5 ms·

That is one thing I always admired about .NET from afar: there was generally one fairly polished framework that you could reasonably trust. In Javaland I feel

by Yhippa 8y ago

That is one thing I always admired about .NET from afar: there was generally one fairly polished framework that you could reasonably trust. In Javaland I feel like I sometimes I have to second-guess everything to make sure I'm using the "best" implementation of something. That and C# is an ISO standard which is pretty cool.

jmartrican 8y ago
As a non-apologetic Java-fanboy I can attest to "I have to second-guess everything to make sure I'm using the "best" implementation of something." This is true. The Spring Boot libraries helps to alleviate that a bit.
- dionian 8y ago
  It's a good and a bad thing. It's good beacuse there is a lot of competition.
elboru 8y ago
I'm a C# developer who has been learning React for the past year, and it really is an exhaustive job to look for the right JS library for every case, this is my process: 1. Facing a code task. 2. Asking myself, should I reinvent the wheel or should I look for a library? 3. Google for libraries solving the task, open at least 5 npm/github tabs. 4. For every tab, I should make sure the library is not too big for my needs/popular/still being maintained/not too many open issues. -Closing the tabs that didn't pass this step. 5. Taking a look at documentation/examples to determine if it can solve my problem. -Closing the tabs that didn't pass this step. 6. Testing the library and see if I can make it work. 7. Implement it in my project. It's a really different environment, and it has its advantages, it's just that Microsoft has spoiled me a little with their out of the box implementations.
- growlist 8y ago
  As a dev that's trying to brush up on JS after neglecting it for years, it's really hard to know where to start.
sjellis 8y ago
> That and C# is an ISO standard which is pretty cool. Microsoft publish older versions of C# through ECMA, but that documentation is always behind the implementations (which are all now owned by Microsoft). The latest ECMA document is for version 5.0 of C#.
yarovoy 8y ago
For years it was not really true. You need DI framework? Study all benchmarks and comparisons for 10 most common DI frameworks. Need ORM? Welcome to the NHibernate vs Entity Framework debate. Logging? Here you go with another 10 choices.

by Yhippa 8y ago

jmartrican 8y ago

As a non-apologetic Java-fanboy I can attest to "I have to second-guess everything to make sure I'm using the "best" implementation of something." This is true. The Spring Boot libraries helps to alleviate that a bit.

dionian 8y ago
It's a good and a bad thing. It's good beacuse there is a lot of competition.

elboru 8y ago

I'm a C# developer who has been learning React for the past year, and it really is an exhaustive job to look for the right JS library for every case, this is my process: 1. Facing a code task. 2. Asking myself, should I reinvent the wheel or should I look for a library? 3. Google for libraries solving the task, open at least 5 npm/github tabs. 4. For every tab, I should make sure the library is not too big for my needs/popular/still being maintained/not too many open issues. -Closing the tabs that didn't pass this step. 5. Taking a look at documentation/examples to determine if it can solve my problem. -Closing the tabs that didn't pass this step. 6. Testing the library and see if I can make it work. 7. Implement it in my project. It's a really different environment, and it has its advantages, it's just that Microsoft has spoiled me a little with their out of the box implementations.

growlist 8y ago
As a dev that's trying to brush up on JS after neglecting it for years, it's really hard to know where to start.

sjellis 8y ago

> That and C# is an ISO standard which is pretty cool. Microsoft publish older versions of C# through ECMA, but that documentation is always behind the implementations (which are all now owned by Microsoft). The latest ECMA document is for version 5.0 of C#.

yarovoy 8y ago

For years it was not really true. You need DI framework? Study all benchmarks and comparisons for 10 most common DI frameworks. Need ORM? Welcome to the NHibernate vs Entity Framework debate. Logging? Here you go with another 10 choices.