The optimizations improved GC performance in general reducing latency, but, the advice in the article is still good. One thing that may seem dated is the concern with Finalization, which is still a valid concern, but nowadays there are very few cases in which one needs to create a finalizer for their types.
Yes, they are all good tips. You will get the best performance if you don't touch memory at all, but that's not practical. There is always a trade-off: don't create large long-living objects mutable split them into smaller ones? But then you have more long lived objects.
Serves me right for not reading the article more carefully. Their proposal is, nevertheless, wrong in its approach to the problem. This can only be solved by putting constraints on the influx and removing constraints on mobility of the people the US does let in. With these two things in place, the rest of the issues will take care of themselves. As proposed $100K isn't much of a deterrent for abuse, seeing that even with $100K+ pay there's a shortage of _entry level_ talent in CA.
