3 ms·

As if type systeme is necessary to build "enterprise-grade" software, "enterprise-grade" sounds to me like bloated Java with terrible framework like hibernate.

• hardwaresofton 5y ago
  If you haven't tried a type system better than what Java used to be, you owe it to yourself to try one of the other options out there. Also, type systems are almost proven at this point to produce better and easier to maintain code in the long term. Startups may not need it while they're iterating super quick, but when they do that rewrite 1-3 years in or whatever, they'll be better served picking a language with a good type system. [EDIT] - Oh also, ORMs are bad, just don't use em unless you really need the velocity. Hooking classes up to objects is just about all I use ORMs for -- write your migrations in SQL and write all queries that aren't braindead-easy (i.e. repository pattern stuff) in SQL/query builder.
  • geodel 5y ago
    > If you haven't tried a type system better than what Java used to be, you owe it to yourself to try one of the other options out there. But those languages are not used for Enterprise Software development.
    • Serow225 5y ago
      F# would disagree :) It's one of the nicest languages for Enterprise software dev
    • hardwaresofton 5y ago
      Well if we followed this rule I think we'd all still be using punchcards? Or FORTRAN? It really depends on what your Enterprise looks like but I do agree that many corporations are going to be better served by more mainstream languages. That said, if you're worried about creating good maintainable software then types are the way to do it -- a lot of the changes that are landing in Java/Python/Ruby/etc came from the niche languages with the good type systems. The renaissance of typing (typescript, mypy, sorbet) is people essentially collectively coming to their senses and realizing that they want to know what their function is expected to be fed, at compile time.