7 ms·

A lot of software development choices are driven by fashion. Much of the time the decision making is based on thinking like "this is something cool I have heard

A lot of software development choices are driven by fashion. Much of the time the decision making is based on thinking like "this is something cool I have heard of and it will make me feel cool to use it".

irrelative 2y ago
It is, and small teams were often rebelling against incumbents, so rejecting the aesthetics of big companies was a good way to attract talent.
torginus 2y ago
Yeah. My first experience with the cloud was moving a small web server to an ECS docker container. The server used to log into a huge text file, which could be grep'd lightning fast or opened up in a text editor even when it grew to gigabytes of size. When switching to AWS, I got to experience CloudWatch, and my first reaction was WTF is this ****? (and once again when I saw the bills)
neonsunset 2y ago
The problem is the average audience is just not technically sophisticated enough to understand that .NET is a _much_ cooler project with capabilities other languages only try to awkwardly stumble into (like portable SIMD). There has been a lot of largely ignored work, and the way ms markets it to web devs that could also write Python scripts is not helping because the underlying platform serves more technically challenging projects in a much better way. As of 2024, the entirety of Apache stack that is built on Java could massively benefit if a timeline changed and it was using .NET (both C# and F#) instead - none of the Lucene issues with manual memory management would ever happen, it would use less memory and be much faster at its hottest paths. I'm almost regretting picking .NET because you are then forever cursed with "bitch, you live like this?" whenever trying out something different (the short list of issues alternatives suffer from: terrible sdk management, terrible package management or just lack of thereof, poor performance, a lot of unneeded boilerplate, unsound language semantics, poor tooling, poor quality ORMs (the main reason people hate ORMs is they never tried EF Core), few properly supported target platforms, limited languages do not let you express concepts nicely, no low-level primitives to write efficient impl., etc etc.)

irrelative 2y ago

It is, and small teams were often rebelling against incumbents, so rejecting the aesthetics of big companies was a good way to attract talent.

torginus 2y ago

Yeah. My first experience with the cloud was moving a small web server to an ECS docker container. The server used to log into a huge text file, which could be grep'd lightning fast or opened up in a text editor even when it grew to gigabytes of size. When switching to AWS, I got to experience CloudWatch, and my first reaction was WTF is this ****? (and once again when I saw the bills)

neonsunset 2y ago

The problem is the average audience is just not technically sophisticated enough to understand that .NET is a _much_ cooler project with capabilities other languages only try to awkwardly stumble into (like portable SIMD). There has been a lot of largely ignored work, and the way ms markets it to web devs that could also write Python scripts is not helping because the underlying platform serves more technically challenging projects in a much better way. As of 2024, the entirety of Apache stack that is built on Java could massively benefit if a timeline changed and it was using .NET (both C# and F#) instead - none of the Lucene issues with manual memory management would ever happen, it would use less memory and be much faster at its hottest paths. I'm almost regretting picking .NET because you are then forever cursed with "bitch, you live like this?" whenever trying out something different (the short list of issues alternatives suffer from: terrible sdk management, terrible package management or just lack of thereof, poor performance, a lot of unneeded boilerplate, unsound language semantics, poor tooling, poor quality ORMs (the main reason people hate ORMs is they never tried EF Core), few properly supported target platforms, limited languages do not let you express concepts nicely, no low-level primitives to write efficient impl., etc etc.)