4 ms·

Don't worry, the Typescript ecosystem is fast becoming Java. And that's the exact reason I'm done with it.

• threatofrain 2y ago
  You mean capable of stable firehose throughput, similar to Go? State of the art GC research on state of the art VM? I wouldn't be surprised if Java had more money behind it than JS on the R&D & corporate backing side.
• jjav 2y ago
  > Don't worry, the Typescript ecosystem is fast becoming Java. Typescript is somehow becoming a laguage that supports writing extremely performant high throughput and very scalable server code? That seems unlikely. So no worries, it can't become Java.
  • jappgar 2y ago
    I said the Typescript ecosystem. Java, as a language is fine I guess, but the culture around it sucks.
    • jjav 2y ago
      > Java, as a language is fine I guess, but the culture around it sucks. Culture is what you want it to be. There are indeed some ridiculous subcultures within the world of developers who use Java. Like J2EE-anything or any of the baroque frameworks. It is important to realize none of that is part of Java and none of that is required unless you really want to. You can use Java simply as a memory safe language with reasonably good type safety that can create wicked fast code and has huge library and tooling support. On all those checkboxes, there are few-to-none options that are so good across all those aspects at once. Unfortunately so many people just complain about writing ­Task­Stub­Consumer­Watcher­Visitor­Service­Container­List­Identifier classes, without realizing nobody is forcing you to do that. So don't.