561–570 of 605 posts
For us, every .NET upgrade since .NET 5 has gone surprisingly smoothly and reduced CPU/RAM usage by 10–15%. We were even able to downgrade our cloud servers to smaller instances, literally. I wish .NET was more popular among startups, if only C# could get rid of the "enterpisey" stigma.
Earlier quoted context omitted.
Same number of options. Razor is still the "default" and "Razor Pages" has a different brand name, but just means "Razor with more things in the main .razor file and fewer code-behind .razor.cs files and less of an MVC approach". Blazor mostly only matters if you want your frontend to also be Razor. At that point you've got the fork between Blazor using SignalR for HTML pipes from Razor files to the client versus Bla…
.razor is blazor, razor pages is .cshtml
Earlier quoted context omitted.
Yeah, but it's very likely you won't be working like a mule, or creating a bicycle with three wheels. How could oneself be innovative and top talent under such conditions?
It's mostly about pay too. And yeah some people want more exciting jobs and maybe even outlandish stuff like the ones you listed (regardless of the sarcasm!). Yes at the end of the day most software isn't super exciting, but it doesn't make a tech stack or platform where most of your job prospects would approximate to "working on some run of the mill, mega enterprise or SMB software project" any more attractive for d…
Most SV tech stacks are romanticized when in reality they are just are all mostly some flavor of a MEAN stack that is building a CRUD. The allure is the lottery payout and a clean slate tech stack, not that the specific tech itself is used.
Earlier quoted context omitted.
Recommended by whom? I've been doing .NET for 23 years (since the first beta) and I've never paid for a single library in any commercial project I've been part of.
Moq, lots of PDF libraries, Avalonia, Automapper, MediatR, MassTransit,Telerik stuff,etc. I'm not inherently against it, we have a problem with opensource being asymmetrically underfunded and if people going commercial is the cost perhaps we've failed.
I just have PDF micro service where I use puppeteer. But I could swap it to Java micro service easily.
Earlier quoted context omitted.
Security and quality aside, I feel that npm have a larger selection of libraries.
As someone who has written multiple Node and C# backends, Node isn't even close to the ecosystem quality. It's not in the same solar system. Npm has tons of libraries, but they're mostly abandoned. Many barely worked in the first place. And if they're even a little out of date, there's a decent chance they're missing TypeScript types or they won't work with your module system. It's a nightmare. Struggling with missin…
Earlier quoted context omitted.
Moq, lots of PDF libraries, Avalonia, Automapper, MediatR, MassTransit,Telerik stuff,etc. I'm not inherently against it, we have a problem with opensource being asymmetrically underfunded and if people going commercial is the cost perhaps we've failed.
Avalonia is FOSS (MIT licensed). You only need Avalonia XPF if you are migrating legacy stuff. Moq is largely unnecessary today with LLMs being able to easily generate mock classes. I personally prefer to hand-roll my mocks, but if you prefer the Moq-like approach, there's NSubstitute (3-BSD). Automapper and MediatR are both libraries I avoided prior to the license change anyways, because I don't like runtime "magic"…
“team decides” and I was busy with other stuff when they were doing evaluation.
But I would gladly pay the license there is just so much just working out of the box with mass transit you don’t realize until you miss it.
We use it with RabbitMQ.
For us, every .NET upgrade since .NET 5 has gone surprisingly smoothly and reduced CPU/RAM usage by 10–15%. We were even able to downgrade our cloud servers to smaller instances, literally. I wish .NET was more popular among startups, if only C# could get rid of the "enterpisey" stigma.
> I wish .NET was more popular among startups, if only C# could get rid of the "enterpisey" stigma. I tried .NET and liked C# as a language. But even though the language and runtime are now open source, it seemed like a lot of the recommended libraries were still commercially licensed, which was an immediate nope from me. I've never encountered that in any other ecosystem.
What are free PDF generation/handling libraries in Java ecosystem what is their performance are they up to date and which licenses?
Earlier quoted context omitted.
Why is it better than just using a method?
Think of it in terms of semantics. An object has certain properties that are immediately obvious and available: color, height, width and so on. Properties in C# are for such values that are immediately available or at least extremely cheap to retrieve or form. Seeing a property tells me that getting the value is a very small op and has no side effects. A method on the other hand is like asking/telling the object to d…
I’m partly convinced now! I still worry a bit about property authors who don’t follow the “cheap, non-side-effectful, externally cacheable” rules, though. Perhaps there are linters in property-ful languages which would help with that.
Earlier quoted context omitted.
There's more to developer experience than that. Your comment even demonstrates one of the differences: The .NET library compared to a bunch of different Java frameworks.
That is indeed a technical difference. But I don’t see much significance in it. Spring is a de-facto extension of the core java libraries and alternatives like Quarkus follow the same mental model with a better technological foundation.
Earlier quoted context omitted.
I use rider on Mac (and windows to be fair) and i think the experience is better than visual studio on windows. My biggest gripe with dotnet tooling is dotnet format. It’s not quick enough to use on a pre commit hook, so people don’t run it regularly and we get failures for it. It’s such a small nit, dotnet is a great environment to work in
Dotnet format is truly slow and bad. I wish the team focused on improving it, and working on better LSP support