> we shouldn’t anthropomorphize

Agree. We should start treating these statistical tools as tools, rather than pretending they are another kind of being.

Exactly. These people really need to get a life.

Java was designed to make manual memory management a non-concern. Yet, ironically, it's the runtime that require more explicit memory tuning than any others.

It absolutely doesn't need any memory tuning whatsoever. People just read 2 decades old blog posts and apply whatever random flag they see.

For 90% of workflows you don't add any command line arguments, for the remaining 10% you may specify a heap size. That's all.

Perhaps you work on simple CRUD applications? In my experience the 90/10 are reversed.

What do you need it for? Which version of the JVM?

Sure, a few examples that happen with modern JVMs (even 25). Essentially anything addressing a large amount of memory (think > 100gb). This can be databases, streaming solutions and so on, where you start tuning the GC just to have a smooth experience. Then there is the case of memory fragmentation of the heap, so you might want to switch out your GC. What else, basically any system that uses a lot of temporary memory is borked, because Java has a nasty habit of not returning unused heap to the OS by default. All in all, my point is, if you are doing anything that actually utilizes the hardware near its limits you will be tuning by quite a bit.

> All in all, my point is, if you are doing anything that actually utilizes the hardware near its limits you will be tuning by quite a bit.

What do you think happens in case of literally any other platform/programming language when you go near the limit? You are just either forced to change code, or.. well just put up your hand in the air, I guess and maybe buy better hardware?

As far as I can tell we are in violent agreement. When you do complicated things you have to tune, when you don't you don't.

This does not match my experience. The amount of manual tuning needed for memory management in C/C++ (which Java was designed to improve upon) was orders of magnitude greater than with Java just to get it correct, let alone efficient in terms of memory usage and performance.

AWS name is really negative.

I trust the person leading DuckDB, nevertheless.

I learn Thinking in C++ from his book for my Master thesis work in 2004

Whoever behind the company communication have done an incredibly terrible job. They start with an extremely unnecessary polished Steve-Jobs-alike debut video when they have zero stuff to offer, while the founder name is already immensely trustworthy. Then follow with a very ugly AI-image-heavy website and blog posts, only to be reverted back to plain website later.

I'd love the language and platform be succesful, nevertheless.

Wonder if this will become common practice from now on ?

  > Pull requests are disabled. Coding agents make it too easy to send a large, 
  > low-context change that costs maintainers more time than it saves. 
  > Thoughtful contributions are welcome; please understand the code, 
  > keep the patch focused, and respect the review time you are asking for.
  > 
  > Send a git format-patch attachment to ...

Could be done by an Openclaw agent named Jarvis.

Funny, the same thing stuck out to me from Cloudflare OS's README (https://github.com/cloudflare/cloudflare-os#contributing):

> At this time, we are not seeking outside contribution.

> AI has made writing code easy. The hard part, today, is not writing the code, but reviewing it, making sure quality stays high, and keeping the product coherent. In that light, unfortunately, external code contributions are "donating" the easy part of the job, while creating more of the hard work.

Feels very weird, but is logically sound: owners know exactly what they want and so they can work with Claude et al to iterate on features faster than with most drive-by contributors.

It reads like an "end of an era" but I imagine the steady state will be somewhere in the middle: high trust, high context contributors will still be able to contribute meaningful work.

time to bring back the dev email distribution list

I wonder if the code was written by AI?

The website surely was, so...

Love this sentence

"The need to conform to digital designs has created an ambient expectation of human subservience. A positive spin on A.I. is that it might spell the end of this torture, if we use it well."

I just learned about Gemma4.pas at the beginning of this week. Now this. This make me wonder how can inference engines could be built that easy. I'm not knowledgeable in this, but I thought it would take very deep Mathematic and system level knowledge, ... and a lot of patience.

If I understand correctly the basic structure hasn't changed since Transformers were invented. It's just gotten bigger and the models have had better training and also some optimizations. I don't think this one has optimizations.

No way! It is a while since I have seen that extension here on HN, I couldn't be mistaken. With AI? Is Pascal still alive?

the math involved is not very hard to understand. it’s linear algebra. the transformer model is brilliant but simple, nobody even really realized the impact it would have until they started training it on massive datasets

I pressed Ctrl-F and search for some programming language names. So amazed by how popular Python, Typescript, and Rust these days. The day of enterprise Java & C# domination have now gone.

Thanks for the false positive looking for c#!

I also don't see general functional programming listed, which was more prevalent a few years ago. Different times.

I think you might want to take some time to understand what a sampling bias is.

Claude has even more occurrences than C#. I feel very old now.

It's a HN bubble :)