I completely agree with this post. It feels like it's the rage these days to 1) over-engineer everything by 2) using existing "full package solutions" to solve simple problems introducing...
I completely agree with this post. It feels like it's the rage these days to 1) over-engineer everything by 2) using existing "full package solutions" to solve simple problems introducing dependency upon dependency and ending up with slow, bloated products. It's how you end up with things like the Google app, which is basically just a package for Google Web Search, being 350 MB.
Windows 95 was 30Mb. Today we have web pages heavier than that
It's clear modern hardware is capable of much more than computers from a decade ago - yet modern software (how does Slack use 1GB+ of memory) is little more performant because developers opt for the quick or trendy solution rather than considering the impact on performance.
Jonathan Blow has a language he alone develops for his game that can compile 500k lines per second on his laptop. That’s cold compile, no intermediate caching, no incremental builds.
This is pretty impressive and I'd love to see how they managed the speed.
I completely agree with this post. It feels like it's the rage these days to 1) over-engineer everything by 2) using existing "full package solutions" to solve simple problems introducing dependency upon dependency and ending up with slow, bloated products. It's how you end up with things like the Google app, which is basically just a package for Google Web Search, being 350 MB.
It's clear modern hardware is capable of much more than computers from a decade ago - yet modern software (how does Slack use 1GB+ of memory) is little more performant because developers opt for the quick or trendy solution rather than considering the impact on performance.
This is pretty impressive and I'd love to see how they managed the speed.