11 ms·
A 2024 plea for lean software
- geodel 3y agoLately I have seen developers are nuking the bloat by converting existing applications to hundreds/thousands of ultra slim micro services. I applaud this approach of taking this issue head on at least in server side domains.
- namaria 3y ago> hundreds/thousands of ultra slim micro services Sounds to me like trading one type of bloat for another.
- 7thaccount 3y agoMore macro level complexity for sure, but I guess you eliminate some issues from having all that as a monolith.
- namaria 3y agoAnd create many others by having networking being now part of your architecture. Bloat is bloat, changing how it's distributed isn't getting at the problem.
- 7thaccount 3y agoI agree and don't really work in this area anyway, but work with brilliant developers who didn't go that route just to add something on their resume. There are obviously tradeoffs and it isn't a silver bullet. Trading one kind of complexity for another may make sense depending on the use.
- infogulch 3y agoYes this is a great move, turning code bloat problems into a distributed systems bloat problem is definitely an improvement.
- shrimp_emoji 3y agoWe'll break the elephant apart into a brainiphant, a heartiphant, a liveriphant, two lungiphants, and they'll all agree over a communication protocol with which to exchange matter and energy. It's more a way to enforce API boundaries than reducing complexity. I guess when you have some anxiety about your ability to do so otherwise.
- thfuran 3y agoIf the goal is just to have harder boundaries, it seems like entirely the wrong tool for the job and comes with a ton of unnecessary baggage. Something like java's module system seems like a much better way to try to enforce API boundaries. Of course, there are languages that lack an equivalent but which can be used to write microservices.
- troupe 3y agoAgreed, and if security is an issue, creating network connections between every single piece of your application seems to exponentially increase the attack surface.
- burnished 3y agoAu contraire, an attacker must understand and then navigate the web you have woven which as we all know is impossible. Security could not be more perfect
- meindnoch 3y agoCan't tell if sarcastic or not.
- Sohcahtoa82 3y agoIn a sane world, this would be satire, but I really can't tell these days. Have people taken "Function-as-a-Service" too literally and done the equivalent of moving "is_even" into an AWS Lambda? Or maybe have a dedicated "is_even" nano-service with its own Kubernetes cluster?
- geodel 3y agoYou are thinking in right direction. Ultra small but critical service like "is_even" and combining it with reliability of a kubernetes cluster, that is genius level stuff.
- BobbyTables2 3y agoHow many have even setup a Kubernetes cluster manually? They use a Kubernetes “distribution” that adds another layer of automation on top of that!!! The day is near where “is_even” will be decomposed into multiple containers, with an added caching layer, and extensible authentication layer.
- triggercut 3y agoYou might hate/enjoy this then: https://andreasjhkarlsson.github.io/jekyll/update/2023/12/27/4-billion-if-statements.html https://andreasjhkarlsson.github.io/jekyll/update/2023/12/27...
- mouse_ 3y agoSee OpenVPN (~70k lines of code) being replaced with WireGuard (~4k lines of code), resulting in far less vulnerabilities and performing far better on top of that.
- christophilus 3y ago> We are likely looking at over 50 million active lines of code to open a garage door, running several operating-system images on multiple servers. It is kind of insane when you see it written out that way. It is staggering how much code I'm running right now on my machine as I type this-- code that I never reviewed and that very likely hasn't had much rigorous review at all. :/ Well, back to installing npm dependencies.
- therealdrag0 3y agoAnd yet it works. Reusable layers and abstractions enable the proliferation of computing use-cases we benefit from today.
- MrDresden 3y ago'Do less, but do better' is a mantra that could do with being applied more often.
- surfpel 3y agoDieter Rams mantra is “Less, but better” His 10 principles guide everything I create.
- lifeisstillgood 3y ago>>> Software is now (rightfully) considered so dangerous that we tell everyone not to run it themselves. Instead, you are supposed to leave that to an “X as a service” provider, or perhaps just to “the cloud.” Compare this to a hypothetical situation where cars are so likely to catch fire that the advice is not to drive a car yourself, but to leave that to professionals who are always accompanied by professional firefighters. I’m stealing that line :-)
- bryanlarsen 3y agoIf cars were invented in 2024, there's no way that the general public would be permitted to drive them. We freak out over new products that result in a few deaths, let alone 40,000 per year.
- samtho 3y agoThis is hard to say because an alternate universe where the car didn’t exist would be quite different and may have not led to our contemporary understanding and management of risk in the first place.
- lcnPylGDnU4H9OF 3y agoI'm not so convinced. People talk similarly about the issues that smart phones have caused with the rise of social media but only fringe political groups want their use restricted by law (with exceptions, such as while driving). I'd expect the most popular opinion to be that the convenience outweighs the cost. (Of course, as a sibling comment points out, it's impossible to really know.)
- throwaway598 3y agoLike smoking in the 1960s.
- supertrope 3y agoStatus quo bias is very strong. If you proposed accepting tens of thousands of fatalities per year, bulldozing entire city neighborhoods, kids not being able to cross the street safely, smog, and constant traffic noise people would be horrified. One common justification NIMBYs use is increased traffic aka the burden other drivers impose on a neighborhood by driving through. Ironically instead of identifying the root of the problem (too many cars and the subsidized infrastructure supporting them) they blame one of the solutions (more housing).
- nonrandomstring 3y agoOne more cheer for suckless [0] philosophy. Hoorah! [0 ]https://suckless.org/ https://suckless.org/
- black_13 3y ago[dead]
- Mistletoe 3y agoIs software bloated because that's the only way for everyone to justify promotions and salary increases? It's hard to get a promotion for slimming down your program to a tiny size and it still works perfectly and is exactly what the user wants/needs. But that is exactly how promotions and bonuses should work.
- namaria 3y agoI think the huge influx of money into technology has been akin to pumping energy into a closed system. Entropy went through the roof.
- amelius 3y agoSince Eternal September it hasn't been a closed system.
- namaria 3y agoClosed systems can communicate with other systems/their environment. Closed doesn't mean sealed here, it means well defined boundaries. edit: ok so for thermodynamics analogy purposes, the statement 'closed system' means no matter flows but energy obviously yes... furthermore, 'the tech system' being made of isolated computers and specialized professionals, or networks of computers and specialized professionals is immaterial for the analogy... lots of energy flowing in, in the form of huge amounts of cash, created a lot of entropy, in the form of accidental complexity.
- chasd00 3y agoi know in the consulting world you always want to maximize the number of logos on any given architecture diagram.
- zem 3y agono, it's bloated because that's the path of least resistance. it's easier to write code that builds on frameworks which build on libraries which build on virtual machines etc, and that is arguably even a better use of the programmer's time than doing everything from scratch, but the tooling hasn't kept pace to let us produce a final artefact that strips out all the bloat and collapses the layers into a small binary. (this is theoretically possible with a "sufficiently smart compiler", tree shaking, and a host of related techniques, but is impossibly hard in practice, given the current state of the art)
- nox101 3y agoBloat is most libraries on npm. The authors don't know good design and instead try to make every library do everything. Oh, my library converts strings from one encoding to another, I'll make it load files for you, save files for you, download them over the internet, and give you a command line tool, all in the same repo. The library should just do its one thing. The rest should be left to the user. I get the impression it's no better in rust land. Go try to edit the rust docs. Watch it install ~1000 crates. The issue is not the language, it's that anyone can post a library (not complaining) and anyone does. People who "just want to get stuff done" choose the library with the most features and then beg for even more since they can't be bothered to write the 3 lines of code it would have been to solve it outside the library. "Can you add render to pdf?" I don't know how to solve it. My one idea is to start an "Low Dependency" advocacy group with a badge or something and push to get people to want that badge on their libraries and for people to look for that badge on libraries they choose.
- crooked-v 3y agoOn this note, I wish more npm library authors would emulate sindresorhus's approach of making small packages that each do very specific things in a predictable and well-documented manner.
- whstl 3y agoHell no. This person is probably the worst offender in terms of supply-chain problems and bloat in the NPM ecosystem. A terminal spinner ("ora") with 15 dependencies (including transitive) is not an example of good design. Inflating the numbers of downloads in your own packages is doing no good to the world of software.
- brnt 3y agoWhat you hope for is shallow dependency trees, not too branchy, but probably also not branchless (an indicator of vendoring). Larger projects will have and likely require depper trees through, but the branchiness should be relatively independent. I wonder if this has ever been formalized.
- hgs3 3y ago> A typical app today is built on Electron JS Not enough folks seem to realize but you can use each platforms native web control rather than bundling electron. If you do that your distributed app can be in the kilobytes. This approach also gives you the freedom to use whatever backend programming language / tech stack you want so long as it can communicate with the web view.
- moralestapia 3y agoHow?
- jsheard 3y agoI think Tauri is the most established "like Electron but with the system webview" framework. It supports wiring up native Rust code behind the webview frontend. https://tauri.app https://tauri.app The obvious downside compared to Electron, besides maturity, is you have to test the frontend on multiple browser engines rather than just bundling Chromium everywhere and calling it a day. It uses Microsofts flavor of Chromium on Windows, Apples flavor of WebKit on their platforms, and WebKitGTK on Linux.
- grujicd 3y agoThere's a small problem with Windows, there are no guarantees you'll have Chromium based Edge installed on a system. You'll have to download and install it if not present, and when I looked it was 100+MB. Sure, you don't have to include it in installer, but you have to account for that case.
- jsheard 3y agoI haven't seen it in action but according to the docs their installer will automatically download Chromium Edge if it's not already installed, so the end-user doesn't have to deal with it, and Windows 11 has it out of the box so that case will only trigger on older versions.
- duckmysick 3y ago
- jurschreuder 3y agoThis is what I keep saying about Rust. Maybe you have 70% fewer vulnerabilities per line of code than C++ if really 70% of (old) C++ vulnerabilities are memory related. But if you then pull in hundreds of packages in Rust and have 10x as many lines of code... 30% of 100k lines is more in total than 100% of 10k lines of code.
- tcoff91 3y agomemory related vulnerabilities tend to be the worst kind though, like RCEs and stuff. Remote code execution is so much worse than many other types of vulnerabilities like DOS. How many RCEs have there been in rust programs compared with C++? I bet C++ has far more than 70% more RCE frequency than rust.
- bsdpufferfish 3y agoOnly for software directly connected to the internet. Unix process separation is a thing too.
- lionkor 3y agothe worst kind? probably not. The worst kind is the vulerability that is a logic error, which no language catches for you, which can leave unskilled attackers accidentally breavhing your whole system. RCE takes effort usually, exploiting a logic error not so much. For example, rust happily lets you access a database before checking that the user's auth token is valid - absolutely nothing prevents you from that.
- estebank 3y agoCounting crates and comparing that with number of C++ libraries is making an obtological error. In Rust, a single team usually splits their project in multiple crates. Something like QT would be hundreds of crates on its own if it were written in Rust, but the amount of code and level of risk taken would be exactly the same.
- jsheard 3y ago
- sharas- 3y ago"Writing has been called the process by which you find out you don’t know what you are talking about. Actually doing stuff, meanwhile, is the process by which you find out you also did not know what you were writing about." Why architects code: https://bitslap.it/blog/posts/why-architects-code.html https://bitslap.it/blog/posts/why-architects-code.html
- cptaj 3y agoIn Vernor Vinge's book A Deepness in the Sky, humanity is spread out around the stars with only subluminal technology. Interstellar ships are very old and mix many technologies from different systems and civilizations. They touch on the fact that computer systems have evolved for so long that nobody really knows most of the code anymore. They just use it and build on top of it. One particular character has been traveling and in stasis so long that he is probably one of the oldest humans alive. A systems engineer of old. It turns out to be a big advantage to know the workings and vulnerabilities of his time because he can use them in the future when everyone else is building many layers on top of that and have no way of knowing exactly what he's doing. Vernor had a point, I think.
- peter_l_downs 3y agoVinge definitely got it right. I love the title of "Programmer Archaeologist", it's an extremely good description of what we actually do every day. For more discussion, see http://lambda-the-ultimate.org/node/4424 http://lambda-the-ultimate.org/node/4424
- AlotOfReading 3y agoAs someone who is separately both a programmer and an archeologist, I love the concept and the books. The real skills aren't always as far apart as you'd think either. I once spent a week deconstructing hardware to figure out what assembly language a project was written in. The assembly was only documented in a TRM in a dusty filing cabinet written before I was born. Once I could read the assembly I could read the source code and work my way up the stack to start answering the actual questions I had.
- lloeki 3y agoThe nice thing with software is that everyone gets to be an archaeologist in short order; ~6 months is more than enough... - Howdy! there's a bug! - Okie, lookie! *dig dig dig, stares at line 47* - Oh my, this horsemanure could not have possibly worked, ever! What kind of damaged wetware wrote this?! $ git blame - Oh.
- AdamH12113 3y agoWhat amazes me is how many people (even here) will leap to their feet to defend an exponential increase in complexity to provide a minuscule improvement in convenience from putting their garage door/fridge/front door/etc. on the internet. I really hope the garage door opener bit is a joke (they come with radio remote controls!), but I have a bad feeling it's not. I can almost see how this sort of thing could work -- a secure LAN for the house with appliance controls based on open protocols driven by a local server. Your phone would talk to the server via a LAN (in-house) or a VPN (remotely), decoupling the connectivity from the actual control. Heck, while we're at it, drop IP from the appliances entirely and use some low-bandwidth power line communication system (X10?) -- no need for an OS at all. That would require a lot of industry coordination, though, and in an age of walled gardens and digital surveillance I don't see it happening anytime soon.
- Semaphor 3y agoI don't really see those comments, everyone usually talks about how people are stupid for getting cloud devices instead of going local with something like home assistant
- AdamH12113 3y agoHome Assistant looks like at least 80% of what I was imagining. Glad to see that some serious work is going into this.
- deleted 3y ago[deleted]
- ryandrake 3y agoAlso, a lot of software developers will defend the exponential increase in complexity by pointing to developer comfort and speed. Building on top of these 40 layers of abstraction is easier and faster for the developer, so therefore it's always worth it. Binary/download size, performance, security issues, user experience... so much can get sacrificed at the altar of developer convenience if we let it. It gets defended because "developers are expensive" but nobody thinks of all the person-hours of our users' time lost because they are waiting for the code to execute up and down that class hierarchy...
- givan 3y agoMy approach to avoid bloat with Vvveb CMS was to avoid general purpose frameworks and libraries that do 1 thing I want and 100 more that I don't. Even if it's harder to get started in the end it's less time spent because you know the code better and the code is not adapted around the library and it can better follow the application design. This approach made everything lean and easy to develop and as a bonus everything is rocket fast.
- pcardoso 3y agoCongrats, looks very good.
- givan 3y agoThank you.
- christophilus 3y agoYour GitHub link is broken, fyi. It goes to “.github.com”
- givan 3y agoThanks for letting me know, fixed it.
- galleywest200 3y agoThat Github they linked in the article with 1,600 (!!!) dependencies. Out of all of the programs ever written, this is certainly one of them. I am sorry to the programmer and this is not meant to be a slight on them, but holy moly. https://github.com/SashenJayathilaka/Photo-Sharing-Application/blob/master/package-lock.json https://github.com/SashenJayathilaka/Photo-Sharing-Applicati...
- wahnfrieden 3y agoThat’s not high
- crooked-v 3y agoI think it's fair to note that a huge chunk of those come from react-scripts (and its own dependency Babel), though. I would bet that only a small fraction of all the depedencies are ever actually included in the output of the build.
- whstl 3y agoYes. Out of the 1600 packages, just looking at package names: 227 are related to Jest, 167 are related to Babel, 93 are related to PostCSS, 66 are related to Webpack, 47 are related to Firebase, 43 are related to Webpack, 24 are related to Workbox. There are even more packages that are related to those but whose name doesn't include the main product. These multi-packages, in 90% of cases, are all maintained by the same people and often live in the same GitHub repository.
- kps 3y ago“Have you looked at a modern airplane? Have you followed from year to year the evolution of its lines? Have you ever thought, not only about the airplane but about whatever man builds, that all of man's industrial efforts, all his computations and calculations, all the nights spent over working draughts and blueprints, invariably culminate in the production of a thing whose sole and guiding principle is the ultimate principle of simplicity? “It is as if there were a natural law which ordained that to achieve this end, to refine the curve of a piece of furniture, or a ship's keel, or the fuselage of an airplane, until gradually it partakes of the elementary purity of the curve of a human breast or shoulder, there must be the experimentation of several generations of craftsmen. It seems that perfection is attained not when there is nothing more to add, but when there is nothing more to remove.” — Antoine de Saint Exupéry, Terre des Hommes
- RomanHauksson 3y agoI would have liked to see some statistics cited instead of anecdotes about individual security incidents. Is industry software really less secure than it used to be because of larger attack surfaces, proportional to the size of the software industry?
- Eransbens 3y ago[dead]
- barnabee 3y agoOver time I’m coming to two conclusions: 1. Standard libraries are the new operating systems 2. The only way to design reasonable (lean, secure, responsive, interoperable, reliable, long lasting, etc.) software is for rich and carefully thought out abstractions to be incorporated into operating system and/or standard library APIs. We have to remove complexity by building better operating systems, programming language, and core standards/ abstractions. A great example is web components—they should have destroyed the case for React and its ilk, instead a completely wasted opportunity.
- Ancalagon 3y agoLeave the bloat, that’ll ensure employment for me forever.
- d-lisp 3y agoA few years ago I thought "how smart I am" when I built a smart TV out of a dumb TV, old computer, small server and light apk on my phone to control the newly created dumb-smart-tv, but in fact even this toy project mediately depends on a the linux kernel, drivers, android and a lot of code I cannot even hope to have the possibility to read in my lifetime. The true smart solution would be to have some kind of system on chip that would send via hdmi the proper signal from a source fetched by a sort of curl but with streaming. But then I would expect the source itself to rely on lean software; something like netflix but instead of a web app you would just have some catalog (a printed one?) of the available routes or codes you can send (like a telephone number) to ask for the emission of bytes to your hardware. But then I would ditch software, you would just compose a number on an old analogue phone and plug the video cable in the enclosure to receive your movie, while listening to the audio via the phone speaker.
- akprasad 3y agoI'm reminded of Maciej Cegłowski's "The Website Obesity Crisis" (2015): https://idlewords.com/talks/website_obesity.htm https://idlewords.com/talks/website_obesity.htm
- cylinder714 3y agoThanks for posting this, as MC removed it from his website.
- burkaman 3y agoThat is his website.
- cylinder714 3y agoYou're right. I clarify: he wrote, "So I spent a couple of hours of my own time making a static version of the AMP website." That static version is unfortunately missing: http://idlewords.com/amp_static.html http://idlewords.com/amp_static.html
- TheAceOfHearts 3y agoLean code doesn't get written because there's crazy time constraints and the market generally doesn't reward or care about code quality. Managers want things shipped last month and they want to keep churning new features without long-term planning. But even going beyond that, we're forced to keep building upon tons of old design decisions which don't always match modern software expectations. It doesn't help that modern operating systems have failed to evolve in order to provide a better ecosystem. And that's not even taking into consideration the barriers created by artificial platform segmentation enforced through copyright abuse. In general, platform owners are very resistant to working together. The biggest innovation in the OS space during the past decade which I'm aware of has been the proliferation of containers. We've given up on combating software complexity and decided that the best thing to do is throw everything into a giant opaque ball of software and ship that. Anyway, for all my ranting all this bloat has at least enabled a lot of people to ship code when they probably wouldn't have otherwise shipped anything at all. The choice is rarely between good code and bad code, it's often going to be between nothing and bad code. And a lot of this shitty horrible code is often solving real world problems, even if it's bloated.
- BlueTemplar 3y ago> It doesn't help that modern operating systems have failed to evolve in order to provide a better ecosystem. > The biggest innovation in the OS space during the past decade which I'm aware of has been the proliferation of containers. As someone in the process of installing Guix, I'm not sure I agree...
- ChrisArchitect 3y ago[dupe] Syndication of article from last month: More discussion: https://news.ycombinator.com/item?id=39049956 https://news.ycombinator.com/item?id=39049956
- deathanatos 3y agoI think I kinda disagree? This is hard (and likely the reason it's not happened) but I think we need, in some ways more code. We need the right code. (And there-in is the rub.) For example, today I was trying to … put a link into Slack. And it is very clear, as a user of Slack, that Slack utterly lacks a parser and is almost without a doubt simply tossing some regexes at the problem. A parser might be "more code" … but it would simply work, whereas I often find valid markdown getting mangled by … whatever is attempting to "parse" it, but probably isn't. We have a script that renews certs with certbot. If I get enough free time, I'm going to be replacing it with a Rust program, as certbot is just too difficult to get automated. It wants to prompt users with questions (do you want to upgrade to EC? No, no, I just want to renew) and regularly fails (it attempts to wait for DNS propagation, but it does so too simplistically; this is made doubly hard on its part that Cloudflare will gladly ack a write in their API … but their DNS is apparently not read-your-writes.) Even the Rust replacement, which is in a prototype, has to re-implement part of ACME, as the ACME library doesn't expose the part I need. I'd rather not … but missing code. I want to parse .deb files to walk their dependency tree, but .deb files use an artisanal format. They're old, so I sort of get it, but it's nonetheless annoying. Read-your-writes is the single biggest reason I have to do inane amounts of retry logic around APIs that ack writes and then gaslight me on subsequent requests dependent on that write. I've hacked around Cython failing to accurately transpile Python. I've hacked around Azure APIs just … not doing what they're paid to do. I've written scripts to make Docker API calls that … could have been exposed in a CLI tool, but just weren't, because tough cookies. The WASM people were fighting about whether strings should be forced to be valid, or not. Think about it: every future WASM program might have to deal with SomeNotQuiteAStringType, for the rest of time, all just to make interop with JavaScript "easier". Hopefully, in Rust, we'll get a WasmString with a `.to_string() -> Result<String, Ffs>`, but that's still an fallible path that didn't need to be. People still think CSV is a decent format. left-pad, widely derided as "one of those dependencies that is so simple you don't need it", failed to correctly implement the function! Then when the ragefest about it broke out the broken function was standardized. Go for the longest time didn't have a round function, and the bug report where it was requested got a "it's so simple just implement it yourself" and it took commenters like 6 or 7 attempts to get it right. round()! (Thankfully, Go saw the light and eventually added it to the stdlib.) In many ways, quality engineers who know what they're doing and write good, high quality systems would go a long ways. But SWE companies are, AFAICT, penny wise and pound foolish in that department, and have traded paying devs for quality with devs dealing with low-quality systems for all of eternity.
- ho4 3y agoAs an enterprise web developer by day, I find my salvation in my personal open source projects. It's a topic that has bothered me for about a decade and had actually made me quit programming as a hobby a few times. As someone else had once said, limitation sparks creativity. Without limitations (such as for instance a low number of dependencies, or deliberately simpler code) the activity becomes mundane and overly goal-focused, which ultimately results in poor quality of the outcome. I personally found myself greatly improve the quality of all my activities in life by imposing "challenging" limitations on them. Though surely it's not an approach for everyone.
- flenserboy 3y agoI remember when the stated dream was to have a standard set of system-provided hooks that led to routines everyone would use for interfaces & more (think: Macintosh Toolbox / QuickDraw) while the main job of the developer would be to code the program logic. There was a great deal of talk about making any changes or additions be transparent — system calls would seamlessly fulfill the same task, even if the code behind them changed, & additions would be supersets of what came before, allowing older code to compile &/or run/function without a hitch, while giving newer software more capabilities. This was supposed to make maintenance easier, regularize interfaces, & at the same time keep code lean since it would rely so much on system calls (external libraries were supposed to be avoided, &c., &c.). This dream quickly fell apart (remember DLLs?), & it seems that much package management & packaging has to do with making sure the right libraries are available. It makes sense that it would not have worked as was hoped, as mass software development was still essentially in its infancy. Here's my question: now that there has been a great deal of collective experience in these matters, is it the case that it has been learned that this dream is simply impossible to bring about in a sane fashion (codebases may simply not be moveable to such a system without unaffordable effort), or has there been enough experience with the current messy state of affairs to drive people toward a modern attempt at making this actually work? If we're wanting fast, lean, stable, secure software (& all four may not be possible at once), I'm not sure that the current situation is heading toward those ends.
- crq-yml 3y agoIt's iterative pressure to push features further down the stack. Early Unix did very little! Modern BSDs ship in a very "complete" state. The early Lisps put very little in the language, but Raku shoves every trivial thing that would go into an npm library into the language spec. The C language made you figure out how you wanted to build your code, while every new compiled language comes with some form of build tooling. There are certain things we are doing in this landscape that are pretty effective, but they are done outside of the "you, the machine, and a greenfield project" context that drove Wirth's endeavors. The problem tends to be that they come with certain monumental thresholds of "big dependency" like a database or browser engine, and if you don't like how the big dependency was made you end up unhappy.
- Donaldoben 3y ago[flagged]
- lawgimenez 3y agoSpeaking of bloat software, I just reformat my Mac to cleanse it from all the Electron bullshit.
- jauntywundrkind 3y agoIn 2025 this winge can finally die. Die hard. The size of software is such a rallying point for malcontents & grumblers. Endless belly-aching, back in my day software was all fast and hand coded in assembly, no, binary, by real men/women. Load times can be a bit bad, and yes 400MB app sizes so kind of suck but honestly, it'll swap out fine and if you have an even passible modern SSD, it'll swap right back in fine too in crazy fast speeds. In principle it's unpleasant, in practice, for most people this is not a real impact. But oh how it attracts aggression and disdain. The point about security is interesting because the stakes are so high. And oh my, we do see some epic disasters. What was the npm one with cyrptocoin wallets being drained recently? But you know? In general the number of occurences have been fantastically stunningly low; it's rarely an issue. There's some log4j shit where longstanding legacy unmaintained apps have some horrific vulnerability that no one is around to import the fix for. But generally? Most exploits are dealt with with amazing haste these days, at much shorter intervals than most dev's do uodates, such that most teams likely won't see impact. There's incredibly good tooling available to report dependencies & automatedly offer patches. The stakes are high but our defenses are astoundingly modern capable & fast acting. We are vulnerable, absolutely, but in practice where we are is amazing. The security footing I think is hella legit as a plea for lean software. Far more so than so many other persistent endless grumbles. I'm so weary that so many folks have a common place to get together and bellyache & moan, endlessly, again and again, about how bad software is, and how awful things are, when it's not. Shit is amazing. Our ability to stitch great shit together is amazing and having some extra code or parallel utility functions coded in just isn't really a great offense. Software has plenty of bad architectures underneath the surface, that make it low performance and bad. There's real hard problems about doing minimal amount of work when things change, figuring out what work to do, understanding what data structures and algorithms are helping and hurting. I want software dissenters, I want anger, but it feels like such low grade feed stock complaints that focus on such low & mostly-irrelevant factors that they can easily get together & breed disdain over. So, here we are in 2024, and this security stance seems like a super legit if improbable thing to be terrified about, an actual forcing function to care about the growth of software under layers. If only we had some kind of secure maybe cross-language hopefully capabilities-based sandboxed system for running code that we could use to run libraries safely in... Aoj wait, we do, it's called wasm, and wasi just shipped preview 2 with component-model, so we can make this happen. I'm excited that we can progress past this reason for conservative Fear Uncertainty and Doubt, by encapsulating the problem and containing it, without having to undergo some radical revolution where we completely remake software development in some undefined safe secure mysterious way where everyone starts all using the same code which we all agree is the exactly right code & nothing else is possible. People love to get together & feel smug that they have been in touch with the better halcyon universe where everything is great & only as it should have been, but no one has offered even the remotest suggestiom of how we get there. MS tried with years of .NET but even they had to constantly reinvent what batteries included meant. Who else will do better, make only perfect decisions, such that no one else ever need touch or address the topic again? This longong for some higher authority to make code perfect & simple as can be flies in the face of what should be exciting & compelling & powerful about the coding world to me; it's messiness brings amazing glory & possibility & we thresh towards better slowly & chaotically. What happens is amazing & I'm so tired of the positive of this world having no outlet, no rallying points, while the people who want to trash software can cand together so regularly so easily & so frequently. It's unfair that software conservatism has as much appeal as it does, and wasm stands to cut this reality-bias off at the kneecaps, thank the stars.
- crossroadsguy 3y agoMaybe something like this can help - Product Managers being educated in causes and short and long term side-effects of bloat in depth. PMs and their ever increasing lust for making a piece of software do moreeeee! - Coders should be penalised for frivolous use of libraries (especially in that glorious NPM world). Sometimes I wonder whether they’d just include a library instead of typing the word “include” if they could. - Dependency registries like NPM (actually especially NPM) should have a strict IIEN check before any library is published there (IIEN: Is It Even Needed). Sometimes it’s okay, actually better, to just write your own quick little wheel. - package.json (there’s yarn as well?) should be declared a health hazard especially for anyone who is not directly in the field (they might cause panic attacks) - and that’s just the first level listing.
- liendolucas 3y agoIf I had known 20 years ago that software would be like it is today I would have ever chosen to be a programmer. Everything seems gargantuesque. Hardware and software hand in hand competing in an endless race. And things are not better, nor easier, nor simpler. What a disappointment.
- foobarian 3y agoI wish we could do what Linus did and start a lean walled garden ruled with an iron fist. How nice would everything be if it was written like Apollo mission software but ran on today's hardware! Sigh
- liendolucas 3y agoI was actually thinking about the Apollo computers. We assisted man on landing the moon with a micro fraction of we have today. And flawlessly! It astonishes me so much that achievement when I compare it to where the industry is today that each day I'm more convinced that we have completely lost the skyline.
- atq2119 3y agoNot flawlessly. There was a pretty scary bug with the radar(s?) during the moon landing of Apollo 11.
- inversetelecine 3y agoShowed a young kid (I think the machine was older than him) an old Gateway G6-300 machine from 1999. Pentium 2 300MHz, 128MB SDRAM, 5GB hdd, Win98 FE, with over 3.5 GB free. I'm more a hardware than software person so the main draw for me was the unknown (to me) Chromatic Research Mpact AGP onboard graphics. Anyway, his comment made me chuckle: "Wow, looks like everything runs pretty quick!" And he was right, everything loaded instantly. Even IE6, Netscape Communicator, Adobe Acrobat 5, etc
- omoikane 3y ago
- kazinator 3y agoIf you want leaner software, the first thing you must do is eliminate the vast throngs of users who are generating the demand for the bloated software, such that making that kind of software becomes the economically preferable activity. This issue has analogies elsewhere. Why anything sucks at scale in any way has to do with large numbers of other people. Why can't you find a good quality Widget at any price, only cheap ones? There aren't enough of you who want the better Widgets, so it's not worth it. And when you say any price, you don't actually mean it anyway.
- deleted 3y ago[deleted]
- austin-cheney 3y agoAs a former JavaScript developer the problem is poor training and poor candidate selection. Many people, perhaps most, writing JavaScript professionally cannot do their jobs without advanced considerable assistance, fear (as in phobia) writing original software, and cannot communicate at a professional level. What would happen if things like Angular or React suddenly went away. Would these developers be able to write new applications. Likely not. What if a developer could no longer use jQuery or equivalent helper libraries? Could they continue to deliver work? Almost certainly not. When most of the work force is only interested in their own narcissism the industry has failed on multiple levels. This is experienced when the first, second, and third priorities are only in the developer’s own self interest such as needing things to be easy. That is why software is bloated, because when the self-interest of the developer is all that matters performance and efficiency become absurdly irrelevant. The solution to this problem is to set high standards. Not high compared to other professions but astonishingly high compared to software today. If current developers cannot achieve such lofty professional standards do not hire them as senior developers. It may mean it’s in the best interest for employers to train people off the street who are not yet corrupted by poor habits. Eventually the solution will become economic: what is cheaper for the employer. Will it be cheaper to employ large staffs that deliver bad products slowly in their own self-interest or start anew with well trained teams that deliver excellence rapidly at great training or certification expense. Until the industry figures this out I will never write JavaScript professionally again. Currently, children run the daycare.
- whstl 3y agoYou had been downvoted, but I share the same experience. It has become very difficult to have some discussions with less experienced developers, because they have a problem accepting that there are alternatives they're not familiar about. Just this week I had a discussion with a recent hire that claimed it was impossible to use GraphQL without a dedicated client library. The claim that our team built our current product with just fetch was met with "there must be some security issue, or you had to rebuild from scratch something that is as complex as Apollo".
- lelanthran 3y agoSoftware cannot get leaner, because that takes time, skill and highly paid people, not just people gluing together examples from 12 different tech stacks into a frankensuite. I'm an independent developer, and the person who learned node.js last year, who will throw node.js, containers, random AWS hosted DB services, lambda services, object storage, cloudflare, yaml, react, vite and other dependencies together to produce a cookie cutter, yet still very fragile, webapp together in a day will always bid lower than me. The lean, fast, cheap to run and cheaper to maintain software just can't be written profitably, even if it is cheaper in the long run.
- mrd3v0 3y agoYup, it is not about awareness, it's about how the economy is structured. If people are paid for unsustainable software, they'll do it.
- fuzzfactor 3y ago>The world ships too much code, most of it by third parties, sometimes unintended, most of it uninspected. Because of this, there is a huge attack surface full of mediocre code. And that's just the attack surface when it comes to leanness mediocrity. The "defect & deficiency surface" is much larger than the attack surface, and defects are always doing their deeds while attacks are (hopefully) relatively seldom.
- raid2000 3y agoEven as early as 15 years ago, MIT switched from scheme to python. The reasons are detailed in an interview[1] (see HN discussion[2]): the educators belived the future of programming would be snapping pre-made libraries together instead of engineering from scratch. 1: https://www.wisdomandwonder.com/link/2110/why-mit-switched-from-scheme-to-python https://www.wisdomandwonder.com/link/2110/why-mit-switched-f... 2: https://news.ycombinator.com/item?id=14167453 https://news.ycombinator.com/item?id=14167453
- Timber-6539 3y agoA post on HN almost a week ago delves further on the practicalities of shipping lean software. https://news.ycombinator.com/item?id=39240471 https://news.ycombinator.com/item?id=39240471
- MagicMoonlight 3y agoThe first iPad children are growing up. Wait until the software developers don’t even know what an executable is. It’s going to be interesting when the people who made things like Linux die and there’s nobody to replace them.
- pritambarhate 3y agoBy then AI will know how to write operating systems most probably.
- godzillafarts 3y agoClicked the link. Immediately greeted with a CTA banner, a Google ad, and a cookie banner. Dismissing the cookie banner immediately reveals another Google ad, but this one is sticky and follows me as I scroll. Reading through the article I came across at least three more advertisements. Kind of difficult to take this seriously.
- mcdonje 3y agoThat is ironic, given the topic.
- JoachimSchipper 3y agoThat is on IEEE, not on the author - the article was originally published on the (fast, ad-free, privacy-preserving) author's site at https://berthub.eu/articles/posts/a-2024-plea-for-lean-software/ https://berthub.eu/articles/posts/a-2024-plea-for-lean-softw...
- hilbert42 3y agoIt's now nearly 30 years since this article titled Software's Chronic Crisis by W Wayt Gibbs appeared in the September 1994 issue of Scientific American: https://www.researchgate.net/publication/247573088_Software's_Chronic_Crisis https://www.researchgate.net/publication/247573088_Software'.... What's truly shocking is that the chronic problems with software that were identified in the 1994 SciAm article are still essentially same as those outlined in this current IEEE article. Back then, Wayt Gibbs correctly concluded that software development couldn't be classed as a professional engineering discipline, so why, if anything, has software development sunk even further into the mire over the past 30 years? It is truly incredible that so many have allowed this unmitigated shambles to perpetuate for so long. Why the fuck can't the software industry and computer science finally get their act together?