Originally posted by caligula
View Post
Announcement
Collapse
No announcement yet.
OpenJDK Java 22 Rolls Into GA With New Features
Collapse
X
-
Originally posted by mSparks View PostBullshit
2001 is 23 years ago
The NIO APIs include the following features:- Buffers for data of primitive types
- Character-set encoders and decoders
- A pattern-matching facility based on Perl-style regular expressions
- Channels, a new primitive I/O abstraction
- A file interface that supports locks and memory mapping
- A multiplexed, non-blocking I/O facility for writing scalable servers
Comment
-
Originally posted by caligula View Post
Ever tried pruning images from local Docker db? I noticed my system had 200 GB of "dangling images" not visible in docker images list. Pruning them took 4 hours. Yes. The performance is abysmal. The system has PCIe 5.0 SSD, 64 gigs of RAM, and 16 cores. Just wiping the Docker directories with rm would have taken milliseconds. Also I've implemented a container runtime system in bash. Yes Docker is more extensive but writing something like that is not rocket science.
Comment
-
Originally posted by bug77 View Posthttp clients came years later.
HttpClient was started in 2001 as a subproject of the Jakarta Commons, based on code developed by the Jakarta Slide project. It was promoted out of the Commons in 2004, graduating to a separate Jakarta project. In 2005, the HttpComponents project at Jakarta was created, with the task of developing a successor to HttpClient 3.x and to maintain the existing codebase until the new one is ready to take over. The Commons project, cradle of HttpClient, left Jakarta in 2007 to become an independent Top Level Project. Later in the same year, the HttpComponents project also left Jakarta to become an independent Top Level Project, taking the responsibility for maintaining HttpClient with it.
Meanwhile, the whole point of his golang post was you can't even set timeouts in GO......
And that's before you get into frameworks like mission control and Jakarta Faces/JSF that date back to 2001, power pretty much every large website and have no Golang equivalents.Last edited by mSparks; 24 March 2024, 07:16 PM.
Comment
-
Originally posted by mSparks View PostStill 20+ year old battle tested jars
HttpClient was started in 2001 as a subproject of the Jakarta Commons, based on code developed by the Jakarta Slide project. It was promoted out of the Commons in 2004, graduating to a separate Jakarta project. In 2005, the HttpComponents project at Jakarta was created, with the task of developing a successor to HttpClient 3.x and to maintain the existing codebase until the new one is ready to take over. The Commons project, cradle of HttpClient, left Jakarta in 2007 to become an independent Top Level Project. Later in the same year, the HttpComponents project also left Jakarta to become an independent Top Level Project, taking the responsibility for maintaining HttpClient with it.
https://jakarta.apache.org/
Originally posted by mSparks View PostMeanwhile, the whole point of his golang post was you can't even set timeouts in GO......
Originally posted by mSparks View PostAnd that's before you get into frameworks like mission control and Jakarta Faces/JSF that date back to 2001, power pretty much every large website and have no Golang equivalents.
That thing has no business in a REST/GraphQL world.
Comment
-
Originally posted by bug77 View PostYes, totally unsupported: https://blog.cloudflare.com/the-comp...-http-timeouts
Originally posted by bug77 View PostWell, just because the project was started 20 years ago, that doesn't mean we get 20yo battle hardened jar.
Originally posted by bug77 View Post
JSF powers what?
Originally posted by bug77 View Post
That thing has no business in a REST/GraphQL world.Last edited by mSparks; 24 March 2024, 09:07 PM.
- Likes 1
Comment
-
Originally posted by caligula View PostI have a 3 year old high end phone and it's starting to slow down.
Originally posted by caligula View PostIt's the same with disk space usage. My Linux installation is now at 25 GB. 20 years ago something like 3 GB was sufficient.
Originally posted by caligula View PostYou can't really avoid that with any language these days.
Comment
-
Originally posted by juarezr View Post
How could It get this big?
even a large java application like say datacamp is only 16.75MB.
Last edited by mSparks; 27 March 2024, 09:26 AM.
Comment
-
Originally posted by juarezr View PostIn my last Java app, the fat JAR has almost 1GB. How could It get this big? It was because each one of the Java libraries included a divergent version of other libraries/jars. So it ended with many versions of the same lib.
Comment
-
Originally posted by juarezr View PostIn my last Java app, the fat JAR has almost 1GB. How could It get this big? It was because each one of the Java libraries included a divergent version of other libraries/jars. So it ended with many versions of the same lib.
Maven or Gradle projects would usually select onlyone version of each dependency.
Comment
Comment