News for hackers. Stuff that matters.
Re:What Should I Know About Garbage Collection as a Java Dev... by theshrike79 on Tuesday January 10, 2023 @06:14PM (#34332837)
The "slow" here is very relative.

Yes, you can't push Discord -levels of messages with a GC language (like their famous "we moved from Go to Rust" post told us all).

But you're not going to be at those levels any time soon, GC pauses are just fine in a good 99.99% of cases.

This kind of thinking is a type of premature optimization, you skip whole categories of technology (garbage collection) because you "feel" it's slow based on what you read about an edge case. =)

Re:What Should I Know About Garbage Collection as a Java Dev... by lokedhs on Tuesday January 10, 2023 @06:39PM (#34333055)
Except whatsapp at least used to run on Erlang, which definitely was pushing that kind of data.

GC languages can have much better performance than non-GC languages (for many reasons, several of them mentioned here), and the main disadvantage being unpredictability. However, the unpredictability is not going to be problem for a chat application.

Re:What Should I Know About Garbage Collection as a Java Dev... by SirGiggles on Tuesday January 10, 2023 @09:40PM (#34334415)
> Yes, you can't push Discord -levels of messages with a GC language (like their famous "we moved from Go to Rust" post told us all).

You can to a (pretty big) degree, as Discord have publicly stated in engineering blog posts:

- https://discord.com/blog/how-discord-scaled-elixir-to-5-000-...

- https://discord.com/blog/using-rust-to-scale-elixir-for-11-m...

Re:What Should I Know About Garbage Collection as a Java Dev... by keyczar931 on Tuesday January 10, 2023 @09:50PM (#34334486)
99.9% of those posts from startup engineers saying "we migrated from X to Y" is because they wanted to play with technology Y and rationalised their decision.
Re:What Should I Know About Garbage Collection as a Java Dev... by winrid on Tuesday January 10, 2023 @11:58PM (#34335170)
IIRC they fixed a worst case latency of like 300ms in their LRU cache. These were periodic spikes. I doubt users really noticed a change from this. Maybe, it saved them some money...