News for hackers. Stuff that matters.
Re:Memory in JavaScript – Beyond Leaks (2019) by alkonaut on Monday June 22, 2020 @06:24AM (#23598767)
If compilers could do this even with hours of time to spend, that would be absolutely revolutionary. I program in a high level language (C#) and my whole day is usually moving things to the stack instead of the heap, devirtualizing calls, making SoA/AoS changes etc. I doubt we'll ever be in a position where compilers can make these decisions well enough. Much less jit compilers and dynamic runtimes that need to do it with time constraints.
Re:Memory in JavaScript – Beyond Leaks (2019) by Kiro on Monday June 22, 2020 @06:44AM (#23598882)
What are you building that requires that?
Re:Memory in JavaScript – Beyond Leaks (2019) by alkonaut on Monday June 22, 2020 @08:59AM (#23599651)
A large desktop app (CAD). But the same thing has popped up in other projects: games, audio plugins, statistics, visualization... Basically anything that is CPU/Memory bound (which is most things except for basic web/database apps I find) needs careful thinking around performance.