321–330 of 428 posts
Earlier quoted context omitted.
What do you mean by golang quirks?
No passable debugger, weird typing system, verbose error handling, lack of exceptions, generics, syntactic sugar ... I'm a novice at Golang, and I dislike much of the language, except that it's fast and can produce small binaries.
Earlier quoted context omitted.
Microsoft branding is terrible. My only point of contact with it is Visual Studio Code which is different from Visual Studio which is different from Visual Studio for Mac. There was a brief period of time after I recognized that .NET really works on all platforms without proprietary stuff and before the `dotnet watch` desaster in which I was at least curious about .NET. But even then I never fully figured out how .NE…
Agreed 100%. Even seasoned .NET devs can’t tell what all this stuff means and what the implications are. I wonder if anybody at MS really knows.
> In .NET 6, in-memory single file apps have been enabled for Windows and macOS. In .NET 5, this deployment type was limited to Linux. You can now publish a single-file binary that is both deployed and launched as a single file, for all supported OSes. Single files apps no longer extract any core runtime assemblies to temporary directories. This is a great! Now I can publish statically linked executables and run it e…
Just don't do it.
Earlier quoted context omitted.
IMO they need to realize the common denominator of all these failed and deprecated frameworks is the very thing they've desperately clung onto over all these false starts... and that is XAML. Get rid of it.
XAML is good. It's very easy to build interface by nesting components then styling it if needed, and doing data binding. All the web alternatives are harder to use and came 10-20 years later.
React, Vue, Svelte as well as Flutter & SwiftUI all implement different but vastly more productive reactive dev models.
MAUI will not be resurrecting .NET Desktop Apps which have been on decline since WPF. Blazor Desktop Apps might, anything XAML won’t.
Earlier quoted context omitted.
Perceived cool factor, I think. Both .NET/C# and Java are the core of Dark Matter Development [0]. They're what a huge chunk of developers and enterprise actually use but they're not cool and they don't get blogged about. Obviously the history of EEE and Windows only legacy means there's a lot of hostility to anything .NET specifically amongst a subpopulation of developers. However I don't think it sufficiently expla…
"Dark Matter Development" -- finally I have a name for it! Sometimes you see articles on the Internet where someone basically says something along the lines of "All developers use the Linux bash command-line workflow", and I just look at statements like that and wonder what on earth are they talking about!? I have never seen a developer familiar with the command line. I have never seen a developer willingly use a Lin…
There are a lot of CLI devs out there, even in enterprises! I highly recommend gaining proficiency with the command line, as it will make you a more productive developer in the long run. While most everyday tasks may have a GUI, if you end up working near the cutting edge, you will likely encounter problems that do not have any GUI alternative. And if you end up working on a rare problem, no GUI may ever emerge. Your CLI skills may be the difference between a 10-minute solve and not being able to accomplish the task at all.
I spent > 10 years building on Windows, and this advice definitely applies to the .NET ecosystem as much as others. On Windows, Powershell mastery will set you apart.
Earlier quoted context omitted.
Yeah "publish" is magical, I specifically jumped from .net 4.8 to 5 just for this feature.
msbuild had publish since at least .net 3.5 (when I started to use the platform) it was just a little bit akward to use tough. and of course dotnet publish is 1000x better than msbuild with it's obscure syntax (which got way better in .net5 and 6 with -p: syntax, etc.)
Earlier quoted context omitted.
Into Oracle? Isn't it also expensive?
I mean that Oracle is even more fantastically expensive, and the SQL Server team wants the charge a comparable amount. They're slowly but surely working up to that level...
Earlier quoted context omitted.
No passable debugger, weird typing system, verbose error handling, lack of exceptions, generics, syntactic sugar ... I'm a novice at Golang, and I dislike much of the language, except that it's fast and can produce small binaries.
Sounds like you want nim.
vlang[0] also seems like a nice golang "fork" that I'd be willing to spend time on.
Earlier quoted context omitted.
IMO they need to realize the common denominator of all these failed and deprecated frameworks is the very thing they've desperately clung onto over all these false starts... and that is XAML. Get rid of it.
XAML is good. It's very easy to build interface by nesting components then styling it if needed, and doing data binding. All the web alternatives are harder to use and came 10-20 years later.
Earlier quoted context omitted.
I never run anything else than LTS in production. The in-between versions have basically been beta quality since .NET 1-preview.
Crazy how bing.com seem to not care for "beta" software :D