A standard for build output might make sense to me. Maybe just throw cache stuff in .cache and build output to .build (with intermediate artifacts in there as well potentially).
When enabled via flag, dotnet puts stuff into artifacts/obj, artifacts/bin, and artifacts/publish respectively. I like that. So much better than every proj folder having their own.
And there's really no need to make it a dot folder. For the publish you don't want to anyway. And you may want to navigate to bin as well, to run a build or inspect the output.
It depends.
If you can do a static website, don't need user content management, do it. You evade all kinds of trouble and technical complexity.
warning letter? throw them out right away
A bit too broad to give a specific answer from my side.
Overall, I prefer web based over apps, because I can CSS hack and if necessary JS hack them.
Web also means it doesn't litter my PC or mobile phone or tablet. And that it can't fetch more data than it needs or I want it to have access to.
Bad software is bad software, no matter if it's installed or on the web.
The git compatibility is necessary for adoption and connected use.
jj does significantly reduce the work interface, but the git compatibility increases complexity again.
I tried it out a little bit a few days ago, and found it interesting. But given my git knowledge and tooling, I can't reasonably switch. First, I would miss my TortoiseGit Log view (entrypoint to everything). But also, the connection between jj and git seems complex and potentially error prone.
As a fresh and independent tool I can definitely see how it's much easier and better, especially for people not familiar with Git.
from some time ago
It's a fair statement and personal experience, but a question is, does this change with tool changes and user experience? Which makes studies like OP important.
Your >95% garbage claim may very well be an isolated issue due to tech or lib or llm usage patters or whatnot. And it may change over time, with different models or tooling.
It's not a duplicate URL. You posted an image, they posted a link to the study.
I mainly wanted to give the additional context and discussion, more so than say "has already posted".
I assume I must have compared a modified date or sth, dunno. Misled by it being shown further down in my feed.
The JSON Programming Language. Contribute to W1LDN16H7/JPL development by creating an account on GitHub.
Examples from the README
example 1
json [ { "let": { "name": "JSON", "times": 3 } }, { "for": { "var": "i", "from": 1, "to": "times", "do": [ { "print": { "add": ["Hello ", "name"] } } ] } } ]
example 2
json [ { "import": "system.jpl" }, { "print": { "call": { "now": [] } } }, { "print": { "call": { "osName": [] } } }, { "print": { "call": { "cpuCount": [] } } }, { "let": { "a": 9, "b": 4, "name": "JPL" } }, { "print": { "add": ["\"a + b = \"", { "add": ["a", "b"] }] } }, { "print": { "mul": ["a", "b"] } }, { "print": { "div": ["a", "b"] } }, { "print": { "mod": ["a", "b"] } }, { "print": { "&": [6, 3] } }, { "print": { "||": [false, true] } }, { "print": { "gt": ["a", "b"] } }, { "def": { "sq": { "params": ["x"], "body": [{ "return": { "mul": ["x", "x"] } }] } } }, { "print": { "call": { "sq": [5] } } }, { "def": { "greet": { "params": ["who"], "body": [{ "return": { "add": ["\"Hi, \"", "who"] } }] } } }, { "print": { "call": { "greet": ["\"JSON Fan\""] } } }, { "if": { "cond": { "<": ["b", "a"] }, "then": { "print": "\"b < a 👍\"" }, "else": { "print": "\"b >= a 🤔\"" } } }, { "for": { "var": "i", "from": 1, "to": 3, "step": 1, "do": [ { "print": { "call": { "sq": ["i"] } } } ] } }, { "print": "\"All features in one! 🎉\"" } ]
example 3
```json [ // 🚀 Welcome to JPL — JSON Programming Language!
// Import system utilities for fun stuff { "import": "system.jpl" },
// Print system info { "print": { "call": { "now": [] } } }, { "print": { "call": { "osName": [] } } }, { "print": { "call": { "cpuCount": [] } } },
// Define a math function to square a number { "def": { "square": { "params": ["x"], "body": [ { "return": { "mul": ["x", "x"] } } ] } } },
// Greet a user { "def": { "greet": { "params": ["name"], "body": [ { "return": { "add": ["Hello, ", "name"] } } ] } } },
// Declare variables { "let": { "a": 7, "user": "Kapil" } },
// Use greet function and print { "print": { "call": { "greet": ["user"] } } },
// Conditional message { "if": { "cond": { ">": ["a", 5] }, "then": { "print": "a is greater than 5" }, "else": { "print": "a is 5 or less" } } },
// Loop with break and continue { "for": { "var": "i", "from": 1, "to": 10, "step": 1, "do": [ { "if": { "cond": { "eq": ["i", 3] }, "then": { "continue": true } } }, { "if": { "cond": { "gt": ["i", 7] }, "then": { "break": true } } }, { "print": { "call": { "square": ["i"] } } } ] } },
// Fun ending message { "print": "🎉 Done with curly braces and JSON fun!" } ] ```
So many words…
to 
oh god please no
wth is all that coloring [in the design samples]
jank is a Clojure dialect on LLVM with a native runtime and C++ interop.
Stop allowing full unfettered access
There's a decline button. At least privacy settings don't repeatedly come up again (what this post is about).
If you lease you car you have to give it back.
If you license your games for the duration of them being active, then it makes sense.
The biggest issue, miscommunication, and often illegal practice is calling it buying when it is only a limited subscription. IIRC Steam recently (finally had to) change the wording away from "buying". Because it's not buying if you don't own the product afterwards.
They made computers behave like annoying salesmen | exotext
> The population (especially the younger generation, who never seen a different kind of technology at all) is being conditioned by the tech industry to accept that software should behave like an unreliable, manipulative human rather than a precise, predictable machine. They're learning that you can't simply tell a computer "I'm not interested" and expect it to respect that choice. Instead, you must engage in a perpetual dance of "not now, please" - only to face the same prompts again and again.
Steam
- offers services
- takes a 30% cut on products sold on the Steam Store
- offers free Steam keys, within broad limitations, for you to sell on other stores, or distribute in other ways (free review copies, etc)
- requires you to sell the product at the same price even when Steam is not involved (different store, no Steam integration)
- the implication is that this also applies to discounts (I don't know for sure myself, and the post does not give evidence of it, but the "fair to Steam" implies it)
You could sell a product DRM-free on your own website 30% cheaper, and get the same money, while providing a cheaper, DRM-free alternative. Steam currently denies that, restricting your choices. You can still sell it on your website at the same price, of course, and the customer still has a choice.
I think what feels unfair or maybe immoral is that they make demands, even requirements, upon your decisions and distributions that do not involve them at all. They're taking your product hostage. And they can do so because they're so big you can't not publish on their storefront too if you want reach.
We want to move down to the next line (line feed) but also to the beginning of that line (carriage return) after all.
Unless you open it in Excel. In which case bad things will happen no matter what you have in the CSV…
When did you first hear of Godot?*
I don't know man. Required field. No fitting option. Guess I'll leave.
They bought Java (not javascript)
They bought Sun, which "owned" Java and JavaScript.
The trademark was originally issued to Sun Microsystems on 6 May 1997, and was transferred to Oracle when they acquired Sun in 2009.
Tests communicate a lot of information, to readers, other developers, and even our future selves. Well-written tests focus on a single unit of behaviour that can be described in a brief sentence, and we can use that sentence as the name of the test.
Make your .NET MAUI XAML more consistent and easier to read with global and implicit XML namespaces.
> Building UI in .NET MAUI with XAML continues to be the most popular approach. […] One of the downsides is how verbose it can become. […] > > .NET 6 introduced global and implicit usings for C# which greatly reduced the using statements at the head of many C# files. Now in .NET 10 starting with Preview 5 we are introducing the same for XAML so you can declare your namespaces and prefixes in a single file and use them throughout. In fact, you can now omit the use of prefixes altogether!
Looks like an interesting UI framework. I want to try it out.
ooh, that one; I must have blocked them a long time ago, I was like "I don't see any such posts"
Browsers typically ask you to grant permission before sharing sensitive information.
Starts with the basics of how Datamoshing works in video encoding, then explores it in game engine rendering.
OpenAI's o3 just uncovered a remote 0-day in the Linux kernel's SMB code—CVE-2025-37899. A patch has already been rolled out.
Developer experience, concrete examples, contextualized, including flaws/edge of capabilities.
Ideation, Maintenance, Coding, Testing, Debugging, …
Chapters:
- Speaker Introductions
- 00:03:03 - Personal experiences with AI in coding
- 00:14:41 - Updating regular expression engine
- 00:31:39 - AI Assisting in Code Writing and Fixing Mistakes
- 00:34:01 - AI-Driven Regex Capabilities for Uri Templates
- 00:37:59 - Enhancements in Memory Extensions
- 00:44:10 - Discussion about AI handling tasks and upcoming merge
- 00:46:00 - AI creates and handles test cases automatically
- 00:46:57 - AI tackles project tasks, improves efficiency, and handles edge cases
---
A good look into how it is and can currently be used.
cross-posted from: https://programming.dev/post/31210046
Firefox 139.0 released yesterday, with support for the Temporal JavaScript API.
I explored the API, writing down the most relevant interfaces into a reference or cheat sheet.
It's certainly and finally a thorough API for handling temporal information. Working with zoned datetime across time offsets and time zones can get very confusing, though.
I love how you can work with them though, especially with durations.
```javascript console.log(Temporal.PlainDateTime.from('2025-02-05T08:00:00'))
console.log(Temporal.Now.plainDateTimeISO("Europe/Berlin"))
console.log(Temporal.Now.plainDateTimeISO().add('PT2M0.2S').subtract('PT0.5S').since(Temporal.Now.plainDateTimeISO()))
console.log(Temporal.ZonedDateTime.from('2025-02-05T13:57:35.777888[Europe/Berlin]').withTimeZone('Europe/London')) ```
Firefox 139.0 released yesterday, with support for the Temporal JavaScript API.
I explored the API, writing down the most relevant interfaces into a reference or cheat sheet.
It's certainly and finally a thorough API for handling temporal information. Working with zoned datetime across time offsets and time zones can get very confusing, though.
I love how you can work with them though, especially with durations.
```javascript console.log(Temporal.PlainDateTime.from('2025-02-05T08:00:00'))
console.log(Temporal.Now.plainDateTimeISO("Europe/Berlin"))
console.log(Temporal.Now.plainDateTimeISO().add('PT2M0.2S').subtract('PT0.5S').since(Temporal.Now.plainDateTimeISO()))
console.log(Temporal.ZonedDateTime.from('2025-02-05T13:57:35.777888[Europe/Berlin]').withTimeZone('Europe/London')) ```
A little wrapper for hugging face transformers in C# - tonybaloney/TransformersSharp
>A little wrapper for Hugging Face Transformers in C#. This is not a comprehensive 1:1 mapping of the whole HuggingFace transformers package, because the API is enormous. > >If you need a specific feature, toggle or pipeline API clone this repo and make adjustments. > >This project was created using CSnakes and will fetch Python, PyTorch, and Hugging Face Transformers automatically, so you don't need to install them manually.
Embed Python in .NET. Contribute to tonybaloney/CSnakes development by creating an account on GitHub.
> CSnakes is a .NET Source Generator and Runtime that you can use to embed Python code and libraries into your .NET Solution without the need for REST, HTTP, or Microservices.
Run C# files instantly with dotnet run app.cs, no project file needed! Coming to .NET 10, try it out today in Preview 4.
Blog post text follow-up to the build conference video announcement posted here two days ago.
> We are super excited to introduce a new feature that was released as part of .NET 10 Preview 4 that makes getting started with C# easier than ever. You can now run a C# file directly using dotnet run app.cs. This means you no longer need to create a project file or scaffold a whole application to run a quick script, test a snippet, or experiment with an idea. It’s simple, intuitive, and designed to streamline the C# development experience, especially for those just getting started.
> In upcoming .NET 10 previews we’re aiming to improve the experience of working with file-based apps in VS Code, with enhnanced IntelliSense for the new file-based directives, improved performance, and support for debugging. At the command line we’re exploring support for file-based apps with multiple files, and ways to make running file-based apps faster.
Discover what’s new in VisualStudio.Extensibility SDK 17.14, including text classification, enhanced ShowPromptAsync API, and .NET runtime updates for faster, more reliable Visual Studio extensions.
> Our 17.14 release of VisualStudio.Extensibility includes the following features: > >* Text classification support >* Updates to the ShowPromptAsync API > >This release also includes a previously mentioned change regarding .NET runtime management requirements. VisualStudio.Extensibility extensions are executed on a separate .NET runtime host, unlike VSSDK extensions which run in the same process as devenv.exe, using the .NET Framework runtime. Since VisualStudio.Extensibility extensions operate on .NET, we must adhere to the runtime servicing lifetime of .NET. Consequently, the VisualStudio.Extensibility platform will be regularly updated to advance to newer versions of .NET LTS. For more information on how this affects you as an extension developer or consumer, please refer to our documentation here.
Note: VS 17.14 was released 14 days ago. This VS blog post highlights and elaborates on this topic.
How do you experience good and bad reviews and feedback on your games? Are you ecstatic or proud when reading positive reviews? Is it difficult to read reviews listing a lot of negative points?
How does it depend on the proportion of your contributions to the project?
---
I've occasionally wondered about team titles, how individual developers feel when reviews turn out majority or overwhelmingly negative. For very small teams and individual devs, I've often wondered how they feel when receiving "negative" feedback, especially reviews pointing out many flaws.
Today, I posted a Steam review with a long list of things the title is lacking. Personally, I would have never released a title in that state, and for money. I feel bad about pointing out many flaws on indie titles. But I also see no way around it. It's only honest to list what I see and notice. For a review, honesty is key, and allows others to see these things that are not visible from a store page or game trailer.
I'm interested to hear your thoughts and experiences.
I feel like ensuring the presence of a final EOL is something a text editor is supposed to do.
The comment does well in providing context and arguments.
> Lets go back to the closest thing we have for requirements for this editor..Default CLI Editor - Feature Exploration!. This discussion was based on the current state of windows and was not concerned with UNIX.
> Being a simple text editor, it should not hallucinate, it should not add text one did not type, it should not change the text that was typed. If the user typed a tab character, it was because the user wanted a tab character. If you want four spaces then type four spaces.
> edit should by default work like the original namesake and not hallucinate or add characters that were not typed or make assumptions.
Where do you draw the line on "smart" features? Tab should not add indent spaces? Encoding or newline mechanisms? Determining EOF newline?
