Inexperienced devs with too little knowledge, using garbage frameworks and libraries, resulting in bloatware on top of bloatware. Devs are getting spoiled. They have these monster CPUs, and terabytes of memory, and believe the purpose is to consume as much as possible - Instead of conserving as much as possible. I made a point out of ensuring Magic can run on "dust" when I implemented its backend parts, and Hyperlambda, optimising it into oblivion, to the point where you can have the thing running on a Raspberry Pi if you wish. The result is that it performs 5x faster than PHP and 10x faster than Python, even though it purely technically should run slower due to its internal architecture ...
I'm 25 y.o. Expert Web/App Design & Development with 7+ years of experience.
Love my π Muffin and banana ice cream. Practice running & yoga in my spare time. πSupport me: https://ko-fi.com/mariamarsh
There is a chain reaction - new software increases the amount of code, the user has to increase the hardware, as a rule, with a surplus from the requirements of the software. New software is developed for surplus - why optimize if there are so many resources? And at some stage the resource is exhausted, the user buys new hardware.
And if user doesnβt buy it and stays on older versions, then questions of compatibility of formats and scripts begin to arise, itβs necessary to install some incomprehensible garbage to view / play the file, which you either canβt put on the old hardware / OS, or eats up the resource like crazy .
In fact, even in 2022, Microsoft itself is selling the type of βmodernβ Surface Go laptops that start with 4 GB of RAM. User puts Slack, Discord and other "masterpieces" there and thatβs it.
And what you wrote about Hyperlambda is very cool.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Inexperienced devs with too little knowledge, using garbage frameworks and libraries, resulting in bloatware on top of bloatware. Devs are getting spoiled. They have these monster CPUs, and terabytes of memory, and believe the purpose is to consume as much as possible - Instead of conserving as much as possible. I made a point out of ensuring Magic can run on "dust" when I implemented its backend parts, and Hyperlambda, optimising it into oblivion, to the point where you can have the thing running on a Raspberry Pi if you wish. The result is that it performs 5x faster than PHP and 10x faster than Python, even though it purely technically should run slower due to its internal architecture ...
The irony ... :/
There is a chain reaction - new software increases the amount of code, the user has to increase the hardware, as a rule, with a surplus from the requirements of the software. New software is developed for surplus - why optimize if there are so many resources? And at some stage the resource is exhausted, the user buys new hardware.
And if user doesnβt buy it and stays on older versions, then questions of compatibility of formats and scripts begin to arise, itβs necessary to install some incomprehensible garbage to view / play the file, which you either canβt put on the old hardware / OS, or eats up the resource like crazy .
In fact, even in 2022, Microsoft itself is selling the type of βmodernβ Surface Go laptops that start with 4 GB of RAM. User puts Slack, Discord and other "masterpieces" there and thatβs it.
And what you wrote about Hyperlambda is very cool.