251–260 of 555 posts
`Executors.newVirtualThreadPerTaskExecutor()`. Java verbosity is alive and well.
Java API stuff hasn't ever been a huge contributor to verbose code. Yeah I guess some of java.io's stuff isn't great, but the worst AbstractFactoryDelegateImplFacadeProviderVisitor gore was always in the application code.
Earlier quoted context omitted.
What is the virtual thread feature in .NET called? I can't find any information about it.
Tasks, simple intro here https://code-maze.com/csharp-tasks-vs-threads/
.NET might indeed have a virtual thread abstraction and if it does you could of course implement the Task abstraction on top of either virtual threads or OS threads, but what you linked to is not a proof that it does.
`Executors.newVirtualThreadPerTaskExecutor()`. Java verbosity is alive and well.
So is Apple/Swift, but Apple always gets a smile instead of a smirk here on HN. func CMMetadataFormatDescriptionCreateWithMetadataFormatDescriptionAndMetadataSpecifications( allocator: CFAllocator?, sourceDescription: CMMetadataFormatDescription, metadataSpecifications: CFArray, formatDescriptionOut: UnsafeMutablePointer ) -> OSStatus
> Virtual threads offer a more efficient alternative to platform threads, allowing developers to handle a large number of tasks with significantly lower overhead. they should have just called them "Tasks" leaving the already overloaded term "virtual" out of the conversation.
[1] https://docs.oracle.com/javase/9/docs/api/index.html?javafx/...
So with this, the last thing Go had going for it over Java is gone, right? Java has an obviously better type system, while Java originated the billion dollar mistake, Java also at this point has much better practices around handling nulls than Go, Java's jars are more portable than go's binaries, Java's GC performs better, Java has a more mature ecosystem and more libraries... Java has better IDE support and comparab…
> Java's jars are more portable than go's binaries Since when?
`Executors.newVirtualThreadPerTaskExecutor()`. Java verbosity is alive and well.
So is Apple/Swift, but Apple always gets a smile instead of a smirk here on HN. func CMMetadataFormatDescriptionCreateWithMetadataFormatDescriptionAndMetadataSpecifications( allocator: CFAllocator?, sourceDescription: CMMetadataFormatDescription, metadataSpecifications: CFArray, formatDescriptionOut: UnsafeMutablePointer ) -> OSStatus
But really, who cares? Who the hell types out the whole method in this day and age? Type the first few chars, up arrow, down arrow, tab. Jump around with vi bindings. I have not written a full line of code in well over a decade.
Although Apple deserves it since their IDE really blows compared to say Idea.
Earlier quoted context omitted.
I have my complaints about Spring, but bad docs is definitely not among them. What do you consider a good docs?
Django's docs are great. For Spring, Google tends to bring up random sites with dubious quality content.
Earlier quoted context omitted.
Irrational Fear of Java is one of the most confusing things among startup stage companies.
Sysadmin here. It's true Java still smells like "corporate" and "slow". And when I say "slow", I don't mean the runtime speed, but the company speed ;) Until not a long time ago I've been maintaining a bunch of Sun|Oracle|J9 Java 6 + JBoss 4.2.3 + AIX|Linux + PPC|x86_64 ... That was not fun, and the task of moving it to more modern platforms was insurmountable to us. No wonder Azul has support for Java 6 until 2027.…
So with this, the last thing Go had going for it over Java is gone, right? Java has an obviously better type system, while Java originated the billion dollar mistake, Java also at this point has much better practices around handling nulls than Go, Java's jars are more portable than go's binaries, Java's GC performs better, Java has a more mature ecosystem and more libraries... Java has better IDE support and comparab…
As a language java's not that bad at this point. But it still has cultural issues. Every java project I encounter tends to be overengineered, has tons of useless boilerplate code and ends up throwing mile-long stack traces as a result. Also, somehow maven manages to be even more unreliable than npm as a package manager. I still frequently encounter situations which seem to only get resolved by throwing away my .m2 fo…
Didn't stop people from using Javascript.
> I still frequently encounter situations which seem to only get resolved by throwing away my .m2 folder
And I frequently encounter issues which seem to only get resolved by throwing away my node_modules folder (and package-lock.json).
Point being every language has its issues but Java gets knocked down constantly regardless.
Earlier quoted context omitted.
Based on your writing, your experience with Java is indeed very limited and not up-to-date at all.
It's simply that the average Java project is out of date and not worth updating, which says a lot.