abraxas

88 ms·

1021.
by abraxas 7y ago
The slide show is an eye opener for anyone doing performance sensitive work in Java. In particular the amount of overhead introduced by adhering blindly to very common OO idioms will often amount to 80-90% of heap allocation (not including
1022.
Building Memory Efficient Java Applications (2015) [pdf](iro.umontreal.ca)
2 points by abraxas 7y ago|1 comments
1023.
by abraxas 7y ago
Moore’s law will peter out and everyone will be forced to squeeze out more performance out of existing hardware. The tide will turn hard against “the cloud” when companies figure out their cloud spend is many times worse than their own data
1024.
by abraxas 7y ago
If disquss is hailed as an example of good design we’ve fallen so hard...
1025.
by abraxas 7y ago
Yes but hipsters won't be seen dead using it. It's soo not cool. Our industry is much less rational than we think.
1026.
by abraxas 7y ago
It's mostly because most setups will use maven or gradle which do much more than just compile code. They will often pull down dependencies, check for bugs and style inconsistencies, run unit tests etc. If you run plain javac against a
1027.
by abraxas 7y ago
All these great things that Java fossils like myself have been telling Node and Ruby hipsters about. Of course they won't be caught dead writing in a language their parents use.
1028.
by abraxas 7y ago
This is pure hogwash. All that productivity and more has been available for two decades with Java and C#. It's just that hipsters rejected it wholesale because those are their parents' programming languages.
1029.
by abraxas 7y ago
To each their own but YouTube premium is one of the few subscription services where I feel I get my money's worth. YouTube's content library drawfs everyone else's and I use it a ton for education as well as entertainment. So