3 ms·
Have worked with .NET for several years and I'm happy to say is an insanely good option, and it's miles ahead of competition when it comes to serving a specifc
by EliMdoza 2y ago
Have worked with .NET for several years and I'm happy to say is an insanely good option, and it's miles ahead of competition when it comes to serving a specifc profile of programmer. UX, APIs, docs, tooling are generally of very high quality. If as a programmer you do not ever want to get involved (good luck getting a change landed), and don't care to understand much of what's under the hood just want to read good docs and get back to your usecase, if you like automation as long as it's written by someone else (how many .NET devs can build a project without VS or even care to know?), if you're happy to confine your dev skills to the inside of a box defined by MSFT, there is no close second option.
- rjbwork 2y agohttps://use.expensify.com/blog/ceo-friday-why-we-dont-hire-net-programmers https://use.expensify.com/blog/ceo-friday-why-we-dont-hire-n... this article again, but in HN comment form this time. yawn
- devmor 2y agoI always find this article very funny. I do not really use .Net myself, only when I need to make a contribution to a project that is already written in it, but the few developers I know personally that use it are using it for incredibly nonstandard work. I know of an entire framework written in .Net that exists to hook into a proprietary, developer-hostile program and inject a full plugin ecosystem that exposes the protected memory and processing hooks of the program as a user-friendly API.
- lupire 2y agoThat article was a bad HN comment in blog form. The author even put a disclaimer apology on it.
- spyke112 2y agoWow, had not read that before. It seems really offensive to ordinary programmers that just want to get stuff done. I also find my peak productivity when using the .NET ecosystem, which after all is good for business.
- spyke112 2y agoBuilding without VS is actually really easy with the dotnet cli, and msbuild was also doable. But now a days you get a long way just doing a: dotnet build