DEV Community

Cover image for What's wrong with code in 2022? πŸ€·πŸ»β€β™€οΈ
Maria 🍦 Marshmallow
Maria 🍦 Marshmallow

Posted on

What's wrong with code in 2022? πŸ€·πŸ»β€β™€οΈ

I use one service from time to time: I need to upload some files there (the name of the service does not matter, because, frankly, they are all the same). Basically, I just point to a folder on my hard disk, after which its contents are copied to a remote server, which is probably doing something related to databases – these files are given names, and checks are made on who downloads them.

The service is owned by a large company, so its processes are large-scale. It is likely to be hacked a lot, so some protection is required, as is checking that no one has modified the files in the interval between uploading from my PC and receiving it on the server. I understand all this.

... but in essence, we are talking about the fact that you need to register several files, read them, upload, and then close the connection and write to the log file whether everything went well. And if not, what exactly happened. There is nothing complicated about this, and I wrote similar code from scratch using the Wininet API and PHP on a server connected to my MySQL database. Perhaps my system was not as reliable as enterprise-level systems, but it supported hundreds of thousands of uploaded files, their verification, downloading, and logging. That's a job for one coder for two or three weeks, isn't it?

The special file upload tool I use today has a total of 230 MB of client files and uses 2,700 files to manage this process.

You might think that this is a typo, but there is no mistake: two thousand seven hundred files and 237 MB of executable and supporting files to copy several files from the client to the server. This is no longer bloatware or overengineering, but absolute, obvious, visual madness.

The problem is that, most likely, this uploader is no different from any similar modern software created by any other large company. And by the way, it gives error messages and does not work at the moment.

I have seen coders doing this. I know how it goes. This is not only because coders don't write low-level efficient code to achieve their goal: they've just never seen low-level efficient, well-written code. How can we expect them to create something better if they don't even realize it's possible?

You can write a program that uploads files securely, quickly, and securely to a server, and it takes a twelfth of that amount of code. It could be just one file, a single small .exe. It doesn't need hundreds of DLLs. Not only is it possible, but it's easy, and it's more reliable, efficient, and convenient to debug, and it actually works.

You might think that old programmers in their fifties (like my father) complain about bloated code because they are obsolete and grouchy. And I realize it. But the obsolete and grouchy complain about code that is 50% slower than it should be, or code that is 50% larger than it should be. However, the situation has gone far beyond this. We've reached a point where I sincerely believe that 99.9% of the code in the files on our PCs is completely useless and never gets executed. The code is just in a package of 65 DLLs, simply because the coder wanted to do something trivial like store a bitmap and had no idea how easy it could be, so he imported a whole bunch of bloatware to solve the problem.

Like I said, I really shouldn't get mad at young programmers for this. That is how they were taught. They have no idea what high performance or development with constraints is. It may seem strange that a girl of 25 is talking about this, but I had enough wise mentors to show me really beautiful code. My father told me that the first Elite in 1984 had a huge galaxy, 3D space combat, a career progression system, trading, and thousands of planets to explore, and at the same time the game was 64 KB. Modern programmers may hear this, but they don't realize the gulf between it and what we have today.

Image description

Why is this important to me?

This worries me for a lot of reasons, not least because if you need two thousand times more code to complete a task, then at least it should work. But more importantly, I realize that 99.9% of the CPU time on my huge, powerful PC is completely useless. Today, computers are so fast that, 10 years ago, they would have been regarded as absolute magic. Anything you can imagine should happen in 1/60th of a second. However, when I press the Microsoft Surface laptop's volume icon, I see a delay: the machine gradually creates a new user interface element, figures out which icons to draw, and then they appear and become interactive. This takes time. It seems to be about half a second, which is close to a billion years on a processor’s time scale.

If right now (conservatively) 99% of our PC's resources are wasted, we're wasting 99% of the computer's energy. This is absolutely criminal. And what are these expenses for? If you look in the task manager, you'll notice a bloated software nonsense that does god knows what. I'm just typing this blog post. Windows has 102 background processes running. My NVIDIA graphics card currently owns six of them, and some of them have subtasks. To do what? I'm not playing a game; I'm using almost the same set of video card driver functions that my father did twenty years ago, but for some reason six processes are required.

Web View Microsoft Edge also needs 6 processes, just like Microsoft Edge itself. And I don't even use Microsoft Edge. It seems like I was opening an SVG file yesterday, and here you go - 12 useless pieces of code are wasting memory and probably also polling the CPU.

This is absolute madness. This is the reason why nothing works, everything is slow, you have to buy a new smartphone every year and a new TV to download these bloated streaming apps that also hide equally bad code.

Personally, I think it's only going to get worse because big tech companies like Facebook, Twitter, Reddit, etc. are the worst examples of this trend. Soon, each of the thousands of "programmers" working for these companies will be using machine learning to copy-paste bloated, buggy, sprawling Github stuff into their code. Just to add two numbers, they’ll need 32 DLLs, 16 Windows Services, and a billion lines of code.

Twitter has 2,000 developers. More precisely, it was until Elon Musk came along. Tweetdeck sometimes refuses to load the user column. This has been going on for 4 years now. I'm sure none of the coders have any idea why this is happening. And the code at its core, as my dad says, is just a bunch of bloated, copy-pasted ****.

When suggesting the topic title from a link, Reddit can't handle the ampersand, semicolon, and pound symbol. Outside, the year is 2022. The company probably also has 2,000 developers. Obviously, none of them is able to get the text parser to work correctly. What are all these people doing?

Image description

Once upon a time, there was a β€œgolden age” of programming when there were limits on memory and CPU. Today, we live in an ultra-wasteful pit of inefficiency. This is very sad.

Thanks for reading! I hope you have found my reflections interesting and that you now have some questions to consider. Feel free to leave any comments and write if you agree with my opinion.

Latest comments (104)

Collapse
 
chasm profile image
Charles F. Munat

I use a Mac. It's better, but not as much as it should be.

The problem is that most developers are mediocre. This is not a dis on devs. Most people are mediocre at most things -- when they are not entirely incompetent.

This is unavoidable. Intelligence, talent, etc. are distributed on a bell curve. Most people are in the middle, hence mediocre, which means average.

So most devs copy and paste code, which isn't a problem unless you don't really understand what you're copying and pasting. Most devs turn to libraries, frameworks, and other dependencies as a first resort. They only code it themselves as a last resort. And then badly because using dependencies and copying and pasting doesn't teach you to code well.

Because most devs (like everyone else) are mediocre and, frankly, infantile (need supervision, essentially), there is an enormous overhead of process (and people to monitor that process).

Because we all (infants all) really just look out for ourselves, personal gain takes precedence over the group's ostensible goals. Most employees are working against the system, and those who try to do good work are generally frustrated and exhausted or driven out.

But the real question that no one asks is this: Do we really need all this garbage? What if we only made what we actually need, and then shared everything so that everyone was fed, housed, kept healthy, entertained, etc.?

Nope! Nose to the grindstone slaves! We must crank out another million lines of tech debt this week! Extinction is right around the corner. MUST. WRITE. MORE. USELESS. CODE.

Collapse
 
mariamarsh profile image
Maria 🍦 Marshmallow

You definitely need to write books haha πŸ˜„
I really like your comments 😍

Collapse
 
nubuck profile image
Barry Buck

Image description

Collapse
 
mariamarsh profile image
Maria 🍦 Marshmallow

Haha nice πŸ˜‚πŸ˜‚πŸ˜‚
This is exactly what I'm talking about πŸ€ͺ

Collapse
 
cubiclesocial profile image
cubiclesocial

You might find it interesting that writing small, fast code is not as dead as it might seem:

js1k.com/

Plus there is this:

icpc.global/

ICPC requires quickly writing code to correctly solve complex problems. Submissions get something like 30 seconds of CPU wall clock time and a certain amount of RAM to solve a problem. Code that takes too long to execute will get ejected. Most of the problems are designed with sneaky edge cases that will burn CPU cycles. Each failed submission causes the team to take a penalty.

Also, Assembly, C, C++, Rust, and Go communities are still pretty focused on writing really fast code. It's only within the interpreted language space (e.g. Javascript, Python, PHP) and compiled languages that come with massive libraries (e.g. C#, Java) where significant laziness starts creeping in. That's because the hardware has been abstracted away from the developer to such a degree that the developer has no idea what it takes to allocate a chunk of RAM or how data structures are stored or how instructions are executed by the CPU.

At this point, it's really only a matter of time until someone drafts a law that takes note of the inefficiencies in computer software and wasteful use of today's computer hardware. Such a law would require developers to write efficient software within certain specifications. The larger the organization, the more efficient the software would have to be written plus a scaled fine schedule up to 10% of annual revenues for any violation. Wasting CPU cycles = more electricity usage and also more heat. More electricity/heat = more global warming. Wasting RAM = more hardware. More hardware = more landfill e-waste. That law might not see the light of day in the U.S., but it might find purchase somewhere more receptive such as Sweden or Denmark. All it would take is one country somewhere to pass such a law and companies writing and releasing inefficient, wasteful software would find their bank accounts drained shortly afterward. Everyone else would realize "they're next" and optimize their own software. Software development is currently a largely unregulated industry but the bloated software being produced today makes it more and more likely to turn it into a regulated industry.

Collapse
 
mariamarsh profile image
Maria 🍦 Marshmallow

It is a pity that js1k.com has not been held since 2019, it was a very cool competition.
And what about ICPC, where did you find such requirements? I looked through their documentation and didn't find any similar info πŸ€”

You have a rather interesting idea about the regulation of development, I think it makes sense with the right approach, and maybe someday we will get to that. The main thing is not to create an even worse problem, as is usually the case.

Collapse
 
wadecodez profile image
Wade Zimmerman

Software is bloated because we no longer feel the pressure from hardware constraints. It's so much easier to pull in an existing library and write adapters to force solutions.

Code gets bloated because developers only optimize their code, and never think about optimizing 3rd party libraries.

Another problem is a lot of devs ship code with dependencies, source code, or a whole directory of config files.

Also if you think web is bad, let me remind you that Call of Duty and other AAA games are over 200gb!

Collapse
 
mariamarsh profile image
Maria 🍦 Marshmallow

This is true, we have already discussed this in other threads.

Collapse
 
alessioferrine profile image
alessioferrine

I would like to correct the author - the first Elite occupied not 64, but 48 kilobytes, where the first 16 KB - it was a computer ROM with some analogue of the operating system.
And yes, in 2004 we had a Pentium-3 533 MHz at work, and one browser game on Flash worked perfectly on it. This flash player had a bad habit of being updated a couple of times a month, and after each update it worked slower and slower. After 5 years this game was already barely running on the 1700th Celeron.

Collapse
 
frederickprice profile image
Frederick Price

To be even more precise, the original Elite version took only 22KB. But its version for the ZX Spectrum has almost doubled in weight - up to 40KB. But on the other hand, many different enemy starships were added.

Collapse
 
mariamarsh profile image
Maria 🍦 Marshmallow

How is that even possible? I just can't believe 🀯

Collapse
 
mariamarsh profile image
Maria 🍦 Marshmallow

Thank you for this remark. This makes it even sadder πŸ˜”

Collapse
 
igibsonconor profile image
Conor Gibson

I propose to call this problem the "Problem of the French Scribes". There is a legend explaining why in French words there are many more letters in writing than they are pronounced (sometimes only one sound is pronounced out of 5 letters) - in ancient times, when there were very few literate people, and paper documents were already in circulation, scribes took bribes from clients for each letter. So they cheated quite good amounts for writing simple texts. Smart-ass puffed-up turkeys πŸ˜„ This is only speculation of course, but it is quite logical.

Collapse
 
mariamarsh profile image
Maria 🍦 Marshmallow

By the way, as far as I remember, when writing The Three Musketeers, Dumas was paid for the number of lines (like some programmers). Therefore, he specifically came up with monosyllabic characters with a bunch of stingy dialogues, for example, Grimaud Athos's servant.
In the end, the writer was told that lines that took up less than half a column would not be paid. Then he even thought about removing Grimaud from the story.
But ten years later, the writer was paid for the number of words - and Grimaud became more talkative. So the French trace is confirmed, and this problem can also be called "Dumas syndrome" 😲

Collapse
 
igibsonconor profile image
Conor Gibson

This is a curious fact 🧐
This name sounds interesting and mysterious heh πŸ€–

Collapse
 
dagnelies profile image
Arnaud Dagnelies

Cost of Dev Time > Cost of CPU/Ram/Disk. I think that summarizes it.

Back in the old days, hardware was expensive, hence optimization was crucial. Now that hardware is dirt cheap, what is "optimized" is the developer's time. Bloat is a "natural" side effect of that.

Another source is certainly scope creep, by adding feature after feature, that slowly and silently eat up the resources and grows the codebase.

Collapse
 
mariamarsh profile image
Maria 🍦 Marshmallow

I think that relatively cheap hardware is really one of the reasons.
But what about the features: not all software has significant improvements with each new version. We've already looked at the calculator and websites here, and there are many more examples. In most cases, "new" features do not justify such a large increase in code.

Collapse
 
veronika2406 profile image
Veronika2406

I think that games on Nokia and Samsung phones have less weight than now in the "play market" or "up store", even if the quality of new games has improved, there are still too many megabytes, in my opinion.

Collapse
 
cyberdog37 profile image
cyberjopa

it's ok i think

Collapse
 
mariamarsh profile image
Maria 🍦 Marshmallow

πŸ’‹

Collapse
 
slidenerd profile image
slidenerd
  • I might get a lot of hate for this but i ll write anyways. I understand the business implications of what I am writing below is why it needs to be done gradually or in a blue-green deployment phase
  • Do you know what we do when things dont work my friend? We RESTART

  • In the first step, lets scrap all frameworks, angular, react, vue and a 1000 of their friends, scrap that webpack stuff, scrap vite and go back to plain html + css + js days

  • In the second step, scrap windows 10 with its shitty search, 1000s of bloatware programs running in the background and jump back to windows 7

  • In the third step, we setup a committee under every programming language to evaluate and approve libraries. If a library does not solve a genuine problem, no approval. This committee can be a centralized body or a decentralized institution thanks to blockchain

  • In the fourth step, we completely revamp the mobile OS, nobody needs 1 TB of HDD and 64GB RAM on a phone. Most of the apps are full of bloatware. The way you remove this is by making everything backwards incompatible and building the OS from the ground up again. This way the main OS removes all the bloat

Collapse
 
mariamarsh profile image
Maria 🍦 Marshmallow

This is a very bold idea, I think that with proper implementation, it has the right to life.πŸ€”
Using the decentralization charms of blockchain technology, you can fix many things in this world. But, unfortunately, even among crypto projects there are only a few Dex/DeFi with the correct execution, so it is not worth thinking about normal use in real life in the next 5 years. πŸš€πŸ•πŸ˜

Collapse
 
brense profile image
Rense Bakker • Edited

Yes, we've come a long way from the days when thousands of developers around the world would reinvent ten thousand wheels every day and every single one of them was convinced their wheel was the best wheel. Today we have embraced the concept of open source, where code libraries are reviewed and commented on and improved by thousands of developers, who see the value in contributing to the development of the best wheel that we can build with our collective knowledge. Sure there are inexperienced devs who chose (often for bad reasons) to use code libraries that are not well maintained. The other reason why software has more files and bytes now, is because the capabilities they can make use of, have increased dramatically. For example, web browsers can render 3d animations now. No computer could render anything in 3d in 1970s.

Collapse
 
mariamarsh profile image
Maria 🍦 Marshmallow • Edited

Yes, you are right, this is the problem with libraries, where everyone is trying to add something of their own. And when business requires a ready-made solution here and now, of course it is easier for a developer to connect such a ready-made library, from which he needs one feature out of 5000 πŸ€ͺ
Here we can smoothly switch to browsers: the problem is not in new features, because most sites do not use 3d, and in fact surfing ordinary text pages has gone not very far from the 2000s. The problem is that the sites are almost entirely composed of crappy code, which is why one page eats up hundreds megabytes.
Web browsers themselves are no better - they, like many applications, grow over time until they turn into monsters that contain another operating system of their own (sometimes two or more). It seems that in the end they must die under tons of their own unsupported code. But for some reason they never die. 😡

Collapse
 
dragodima profile image
dragodima

Cool

Collapse
 
mariamarsh profile image
Maria 🍦 Marshmallow

Thanks! Have a great day!😊

Collapse
 
kvetoslavnovak profile image
kvetoslavnovak

Just in a process of rewriting one of my web applications to get rid of the most npm libraries as possible. Because when I examined them in detail they were bloated and chain dependent as hell.

I also decided to go with Sveltekit because its usage of native web features (forms, http requests, progressive enhancement ) seem really appealing to me Using the default in-build technologies and as less of JS in browsers seems like a way to go forward or rather to go back to roots.

Collapse
 
mariamarsh profile image
Maria 🍦 Marshmallow

You are one of the few who are on the Light side πŸ’šπŸ’™πŸ’œ

Collapse
 
sleibrock profile image
Steven L • Edited

Modern computers can absolutely waste a ton of CPU and memory, but at the highest levels, the organizations would not care about solving these minor issues. Why does my laptop need 15 gigabytes of RAM to have a spreadsheet, Microsoft Teams and one Chrome tab open? Couldn't tell you. I absolutely hate Windows for how useless it feels. Can't even open Outlook without it spinning up to 100% CPU usage.

But, things aren't always so obvious; software is objectively a challenging problem that requires a lot of well-thought out plans.

For instance: how do you write one project and compile it to work on other people's computers? If you were still writing C, you would have to write a C codebase and use a compiler to support a given architecture and hope the operating system can run your code. Then you have to test it and all that other fun stuff.

But then suddenly, you need to target an entirely different platform that you've never seen before with a different compiler. Suddenly your C code doesn't work, because the platform is different; compiler types are of different sizes, the endianness is a different direction, certain standard library functions don't exist or take different parameters, and now you're stuck writing C preprocessor macros hoping that your pains go away.

This was what coding was like in the awful days, and it can still exist too if you write C/C++. No compiler will make you happy. Everyone either acknowledged C/C++ was awful and moved onto other things during this time period, or simply stuck behind and said "this isn't so bad guys" as they wrote high performance software dealing with the issues that C/C++ brings. Java won a lot of fans because it was very portable with it's "write once, run anywhere" mantra, while C++ is still hated to this day by many.

With Java came other languages that offered more dynamic and flexible programming, like Python and Ruby, which most people scoffed at when thinking about building full-fledged software in. The performance metrics of these two languages aren't great, but sometimes people write Python/Ruby code that can interop with C-world and get decent performance. Fast forward one or two decades and now we have insane machine learning libraries that you can use with Python and are used at Fortune 500 companies.

The web is popular, but golly does it suck to write things for it. HTML pages aren't dynamic, so you need a language to be able to create dynamic pages that can retrieve information from database, so in comes PHP, which sells itself as a solution to a problem web devs were having with FastCGI and Perl. PHP proved itself as an okay solution, and somehow companies around the world threw their million-dollar industries at it and it got us decently far. But the browser was the real pain in the butt, so in came JavaScript, and JavaScript took off to the moon.

Where am I getting with all this? I'm mostly stating that things that alleviate headaches from the programmers are far more popular than things that don't. Writing and maintaining separate language codebases with different purposes is not necessarily better to some people who would prefer to have a "monolithic" repository of code that can do everything and not make things complex. JavaScript can now control the front end, the back end, it can be used to design games, GUI applications, and so much more without ever having to leave the comfort of the JavaScript language itself.

Facebook, Google, Apple and all the other tech companies are the foremost "leaders" of the technical world, and when Facebook publishes a library called "React" where the goal is to make the web easier to develop, what happens? Everyone's going to write React. Google makes Go and uses Go? Go devs will pop up in random places. Increasing your surface vector of being a potential hire at a Fortune 500 is a very promising idea for many aspiring programmers.

But this doesn't mean everything will appear pretty at the bottom of the totem pole. Organizationally, no one gets promoted for fixing memory leaks. Sometimes I have to close my Discord because it leaks memory after several hours and gets slow. Is anyone going to fix it at Discord? No, because it's an Electron problem (probably), and Discord isn't there to fix Electron problems, they're around to fix Discord problems.

YouTube, a site owned and ran by Google, has to polyfill in a ton of extra JavaScript for non-Chrome browsers, making the performance of YouTube on non-Chrome browsers not all that great. Google runs and upgrades Chrome with non-standard libraries so they can move fast, and in turn, makes other browsers perform worse on their sites. I can admit that sometimes other browsers are very slow at upgrading their features (Firefox), but it's not likely that Google will care about the non-Google browsers, as Chrome is included in every single Android device, and is renowned for being the most popular browser on the internet. Why? Probably because it's a Google browser lol, remember that part about everyone using React?

So in summation, we live in a society where poorly-built software is so common-place that people have to upgrade computers to go on Facebook of all things. The lowest common denominators of computer hardware are not the targets of big business, and probably never will be all that important. Our ten-year old laptops are deemed unimportant, and everyone is expected to upgrade their smartphone every two years. Why? Probably because nobody wants to write fast software made with slow phones in mind!

/rant

Collapse
 
flkdnt profile image
Dante Foulke

@sleibrock This is valuable insight, you really show how complicated and ugly things get and fast... and it's true, our world of software and technology is a mess and you really bring clarity to a messy topic

But to talk to @mariamarsh real quick, there's a couple things I want to point out:

  1. I assume you wrote this in reference to Windows computers. Windows is my background and it's honestly a frustrating and messy OS, for many reasons I won't get into. It's not Linux, and Definitely not the prime pick to run containers in. But, it is an extremely complicated software platform where I've touched things I didn't even know existed that affect things I didn't even know X component could. However, since windows 7, they've much improved their act and it's a much more reliable platform.

  2. Where are you getting your 99.9% figure from? How do you calculate resource waste? Is this in regards to software that runs on windows, or you talking about the OS itself? Or both?

  3. I don't think, necessarily, file-size is the End-All, Be-All indicator of resource-usage/waste. For example, compare the file size between the exact same .csv and .xlsx(Excel) file, which one is smaller? File compression, and other factors play into this.

  4. Libraries. Yes, There are built-in libraries in the OS, but that's not the end of the story. What about different Versions of the same library/software? I think it was Windows xp where you had to download different versions of .Net and .Net components for every piece of software. But the same thing applies to every language and dependency version.

Version mismatch and Dependency Hell are very real things that cause issues, from personal to corporate environments to this day. All software is built on software before it, and once you dive deep into what dependencies everything is built on, you'll never reach the bottom. Do you remember how one developer removed left-pad from NPM and broke the internet? That's the situation we are in with all of our software on any operating system. This is a joke tweet, but also, so very true:

"the most consequential figures in the tech world are half guys like steve jobs and bill gates and half some guy named ronald who maintains a unix tool called 'runk' which stands for Ronald's Universal Number Kounter and handles all math for every machine on earth" - twitter.com/6thgrade4ever/status/1...

  1. The last thing is, if you are upset with windows, try linux if you can(There's some software that cannot be ported easily or doesn't have an equivalent counter-part). There's never been a better time to run linux on desktop, or headless, or on ARM devices. It definitely outperforms Windows In regard to Resource-Management.
Collapse
 
mariamarsh profile image
Maria 🍦 Marshmallow

This is a big problem with any modern operating system, whether it's Linux or Windows.
XUbuntu eats up 500-800 MB just after startup, and it needs 1.5-2 GB for some significant work. Win2K startuped and ran with128MB, WinXP with 256. Well, that's not entirely fair, because they were 32-bit: just to CALL to the full address, we need a 64-bit address, but XUbuntu has a difference even with WinXP by 8 times. In fairness, a workstation on Linux still doesn’t eat up more than the conventional 1-2 GB after startup, but Win10 / 11 can easily eats 2-3.

On Linux, all problems manifest themselves in exactly the same way, just try to build any open source project, it will immediately pull billions of the same open source libraries to itself. And many of them are needed only for the sake of one or two functions.
If it were not for the SSD, the available RAM, and the hardware instructions in the processors and their multithreading, the operation of computers running any modern OS would be a sad sight.

The main resources are eaten not by a bare machine, but by applications on it. Websites are almost entirely crap code, and one page "weighs" a hundred megabytes. This needs to be optimized on the server side, otherwise nothing. IDEA, VSCode and a bunch of other applications eat about the same (a lot) almost regardless of the OS. Another example for you is Jetbrains Toolbox, a little application for downloading and updating the IDE. It eats up 200-500 MB of RAM. What? How? Why?

Dependency hell can also exist in linux, I would not put 2 different versions of openssl, or libjpeg without "dances with tambourines". Look at the NPM and Composer dependencies of any site. Previously, jQuery was enough of all JS, but what about now? NPM folder can easily reach several gigabytes, and then from too many files the collector will fail and fall, great!

What about 99.9%, maybe I'm exaggerating, but the absolutely irrational loss of resources applies to both software and OS.

Thank you for your questions πŸ€—
I also advise you to read the comments of other users, there are a lot of interesting thoughts and opinions 🌈

Thread Thread
 
flkdnt profile image
Dante Foulke

"If it were not for the SSD, the available RAM, and the hardware instructions in the processors and their multi-threading, the operation of computers running any modern OS would be a sad sight." Well, yes, things are written for the current hardware standards of the day. People(developers, commuters, pedestrians) will "fill the space" of where they are. People naturally use the tools at their fingertips.

Nothing you've described is particularly new to me, but it feels like you are just describing the state of software in 2022. So, since I'm not sure what you are comparing everything to, I have to ask:

  1. What do you think the state of software should look like?
  2. What does good resource management look like to you, both from an OS perspective and a software perspective?
  3. What do you think are reasonable specs for computers(cpu, ram, HDD space, etc)?

P.S. - Linux Dependency hell is particularly frustrating because if you try to update your packages, and one of those packages was installed by pip / is dependent on something installed by pip, the package manager could fail to update anything.

Thread Thread
 
mariamarsh profile image
Maria 🍦 Marshmallow • Edited

It feels like you are a very curious young man 😏
$500 and we'll face you in a 1v1 Discord battle to see who wins, the Dark Side or the Light Side πŸ”΄βš”οΈπŸ’šYou will be in the role of Darth Vader πŸ‘Ύ
But I have a condition: I will take my father Chewbacca with me 🀣

Thread Thread
 
sleibrock profile image
Steven L

Some of these conversations can be tagged under the "static linking versus dynamic linking" category and others probably file under "software bloat". What do you think your approach to application development is with respect to static/dynamic linking? Ship with deps, or ship targeting deps on a host environment?

Collapse
 
mariamarsh profile image
Maria 🍦 Marshmallow

We can assemble a separate blog on this topic from the comments under my post haha 🀣
With each new comment some new information is added and it's really cool πŸ‘
Thanks for sharing your thoughts 🀩

Collapse
 
sophie_966dd4e profile image
Sophie Gru

πŸ‘πŸ»

Collapse
 
mariamarsh profile image
Maria 🍦 Marshmallow

πŸ€—