4 ms·

If you're going enterprise, go C#. If you're going open source, you should have went python or node.

by skrowl 13y ago

d0 13y ago
No - go Java. ORMs, document generation, reporting, integration, architecture, deployment, tooling, devops stuff. Literally everything is ready to roll out of the box for $0. And it all works. C# - half of this is available for a fee and the rest is available for a larger fee. And none of it works particularly well. And if anything breaks it's $200 a go to get it fixed.
- blahbl4hblahtoo 13y ago
  None of it works particularly well? That's just not true.
- Xdes 13y ago
  I would go Java if the syntax weren't so stale. C# has continued to improve over the years. The BCL and compiler teams are not afraid of breaking changes between major versions. Stability is good (which is why non-nullable reference types won't make the cut), but stagnation kills the ecosystem and drives new contributors away.
  - d0 13y ago
    Java syntax is usually pretty irrelevant when it comes to actually solving problems. C# is a minefield for issues. Linq memory ballooning, null refs, O(WTF) LINQ expressions, tri-state logic caused by nullables, spinlocks from hell (ReaderWriterLockSlim), missing symbols and more sourceless black boxes than anything. Oh and three different subtly broken XML APIs. More language features don't make it better.
rbanffy 13y ago
Actualy I would think Java is a better technology to bet on if enterprise and neckties are your cup of tea. While things like AD, SQL Server and Windows are ubiquitous, there are lots and lots of companies that prefer Java over C#.
- d0 13y ago
  Not only that, Java talks to AD via LDAP and SQL Server via Microsoft JDBC driver. The same is not true the other way round for a lot of things though which means you are stuck in the Microsoft ecosystem the moment you put one foot in it.
blt 13y ago
Yeah, Node should have been the obvious choice in 2001.

If you're going enterprise, go C#. If you're going open source, you should have went python or node.

by skrowl 13y ago

If you're going enterprise, go C#. If you're going open source, you should have went python or node.

d0 13y ago

No - go Java. ORMs, document generation, reporting, integration, architecture, deployment, tooling, devops stuff. Literally everything is ready to roll out of the box for $0. And it all works. C# - half of this is available for a fee and the rest is available for a larger fee. And none of it works particularly well. And if anything breaks it's $200 a go to get it fixed.

blahbl4hblahtoo 13y ago
None of it works particularly well? That's just not true.
Xdes 13y ago
I would go Java if the syntax weren't so stale. C# has continued to improve over the years. The BCL and compiler teams are not afraid of breaking changes between major versions. Stability is good (which is why non-nullable reference types won't make the cut), but stagnation kills the ecosystem and drives new contributors away.
- d0 13y ago
  Java syntax is usually pretty irrelevant when it comes to actually solving problems. C# is a minefield for issues. Linq memory ballooning, null refs, O(WTF) LINQ expressions, tri-state logic caused by nullables, spinlocks from hell (ReaderWriterLockSlim), missing symbols and more sourceless black boxes than anything. Oh and three different subtly broken XML APIs. More language features don't make it better.

rbanffy 13y ago

Actualy I would think Java is a better technology to bet on if enterprise and neckties are your cup of tea. While things like AD, SQL Server and Windows are ubiquitous, there are lots and lots of companies that prefer Java over C#.

d0 13y ago
Not only that, Java talks to AD via LDAP and SQL Server via Microsoft JDBC driver. The same is not true the other way round for a lot of things though which means you are stuck in the Microsoft ecosystem the moment you put one foot in it.

blt 13y ago

Yeah, Node should have been the obvious choice in 2001.