231–240 of 406 posts
Earlier quoted context omitted.
Real humans don't speak in LinkedIn Standard English
> LinkedIn Standard English We need a dictionary like this :D
Earlier quoted context omitted.
Point? I’m SRE on .Net project, we have been through 6-8-10 and its cost us about 2ish hours of work each time. As long as you don’t get crazy, .Net upgrades is just matter of new SDK and runtime and away you go.
You're talking about .net for server applications right? The discussion above is for client apps being distributed for windows endusers.
Earlier quoted context omitted.
I'm going to need a source for both of those claims.
It sure sounds very Debian-ish, at least. I’m a Fedora user, and Fedora stays veeeery close to upstream. It’s not rolling, but is very vanilla.
Earlier quoted context omitted.
I'm so fucking tired of this
I last developed for windows in the late 90s. I came back around 2017*, expecting the same nice experience I had with VB3 to 6. What a punch in the face it was... I honestly cannot fathom anyone developing natively for windows (or even OSX) at this day and age. Anything will be a webapp or a rust+egui multi-plataform developed on linux, or nothing. It's already enough the amount of self-hate required for android/ios.…
You can do a lot of "native" windows development from modern C#/.NET via win32 interop. Newer C# features like ref returns, structs, spans, et. al., make the overhead undetectable in many cases. https://github.com/prasannavl/WinApi https://github.com/microsoft/CsWin32
Earlier quoted context omitted.
That's not correct. You don't have to give your credit card details or even be logged in but you are still required to have any Visual Studio license. For hobbyists and startups the VS Community license is enough but larger companies need a VS Professional license even for the VS Build Tools. How strict Microsoft is with enforcement of this license is another story.
And a VS license isn't too expensive if you really want to buy one. Stack Social have legit licenses discounted to $15: https://www.stacksocial.com/sales/microsoft-visual-studio-pr...
Earlier quoted context omitted.
.NET versions are faster outdated then .Net Framework 4.8
Point? I’m SRE on .Net project, we have been through 6-8-10 and its cost us about 2ish hours of work each time. As long as you don’t get crazy, .Net upgrades is just matter of new SDK and runtime and away you go.
Why is it ok that you have to invest 2 times number of apps hours just because MS has such a short life cycle for its .NET versions.
> The build.bat above isn’t just a helper script; it’s a declaration of independence from the Visual Studio Installer. I am so fed up with this! Please if you're writing an article using LLMs stop writing like this!
I never understood this sentence structure, it adds zero information, it always goes like: “This isn’t just [what the thing literally is]; it’s [hyperbole on what the thing isn’t].”
Er, sorry. I meant: the purpose isn't just drama—it's a declaration of values, a commitment to the cause of a higher purpose, the first strike in a civilizational war of independence standing strong against commercialism, corporatism, and conformity. What starts with a single sentence in an LLM-rewritten blog post ends with changing the world.
See? And I didn't even need an LLM to write that. My own brain can produce slop with an em dash just as well. :)
Earlier quoted context omitted.
What's exhausting is getting through a ten-paragraph article and realising there was only two paragraphs of actual content, then having to wade back through it to figure out which parts came from the prompt, and which parts were entirely made up by the automated sawdust injector.
That's not an AI problem, it's a a general blog post problem. Humans inject their own sawdust all the time. AI, however, can write concisely if you just tell it to. Perhaps you should call this stuff "slop" without the AI and then it doesn't matter who/what wrote it because it's still slop regardless. I completely agree with your parent that it's tedious seeing this "fake and gay" problem everywhere and wonder what a…
Exactly!
Earlier quoted context omitted.
https://github.com/dotnet/core/blob/main/release-notes/10.0/... .NET 10 supports a Windows 10 build from 10 years ago.
Yes and in the wild believe it or not you'll find windows 7 and windows 8. We had just deprecated support for XP in 2020 - this was for a relatively large app publisher ~10M daily active users on windows. The installer was a c++ stub which checked the system's installed .NET versions and manually wrote the app.config before starting the .net wrapper (or tried to install portable .NET framework installer if it wasn't…
I feel for those who have to support an OS no longer supported by the vendor. That's a tough position to be in, not only if a customer comes across a bug that is due to the OS, but it keeps you from advancing your desktop application forward.