8 ms·
It's the Cycle of Bloat. 1. Develop tool. It's small and fast and minimal! Woo! 2. It's easy to modify because it's so small! Woo! 3. Look, there's
by jerf 11y ago
It's the Cycle of Bloat.
1. Develop tool. It's small and fast and minimal! Woo!
2. It's easy to modify because it's so small! Woo!
3. Look, there's a budding ecosystem of packages! Woo! (Let's
not talk about the fact the packages exist precisely because
the original product wasn't big enough.)
4. Oh dear, some of them conflict, a lot of them suck. Well,
here's some winners, let's pull them into the core. Now the
base system is that much better! Woo!
5. Repeat 3 and 4 a few times.
6. Crap, this tool is all bloated and slow. I'm going to go
create a small, fast, minimalist solution!
Repeat indefinitely.
See also: "minimalist web framework", "minimalist Linux distribution", "minimalist programming language".
- crusso 11y agoThere are projects like Linux Kernel, Mercurial, and Rails that have managed to be very extensible and have had good leadership in knowing what to put into core and what to cut from core as time goes on.
- jerf 11y agoWell, I know for sure I've witnessed people say #6 about the Linux Kernel and Rails multiple times. So for what it's worth, I'm very unconvinced that "bloat" is the automatically-bad thing that whoever is saying #6 says it is. There are things that are just crappy amalgamations of whatever, sure, but there are also a lot of big things that solve hard problems, and part of the implication of the cycle is that every time a #6 pops up and starts a new project, (s)he is inevitably beginning on a journey of discovery in which (s)he will discover why the previous tool got big. Big problems require big solutions. And it turns out that "text editing" looks really simple, and gets really not simple really fast. Same for the other two things. I've literally lost count of the minimalistic text editors with great plugin interfaces that have paraded by me at this point. (And... uh... how can I put this delicately... writing a good web framework is actually a non-trivial exercise. The web is complicated to do it right. If you've got a 250-line web "framework", odds are what you've got is 250 lines that sorta kinda work as long as nobody tries to hack it and nobody cares about actual compliance with all of the implicit and explicit standards embedded in HTTP. It may be suitable for your blog, it may be suitable for a 3-call API, but it's probably not suitable for anywhere near as many things as you'd like. And it's probably brutally insecure somehow.)
- doodpants 11y ago> And it turns out that "text editing" looks really simple, and gets really not simple really fast. Text editing is really simple. The problem is that plain text editors are mostly only used by coders. (Non-coders who want to write text use Word.) And coders want features like syntax coloring, autocompletion, split views, multi-file management, etc. Features that would be of no use to someone writing a quick email or jotting down a cake recipe. Basically, what coders want is a program that looks as simple and feels as lightweight as a plain text editor, but gives them many of the features of a full fledged IDE.
- oblio 11y agoText editing is not simple. Not since Unicode is a thing. And it's not because of Unicode, it's because of us humans and our crazy languages.
- jbenner-radham 11y agoTotally agree with you there. I've been reading over the Unicode spec and some of it makes my head spin. I would have never imagined the required level of complexity beforehand.
- baudehlo 11y agoAnd the language Atom is written in supports Unicode very badly indeed, to keep things relevant to the topic at hand.
- deleted 11y ago[deleted]
- coldtea 11y agoDo people believe that having access to packages and add-ons makes an editor (or whatever else) "bloated and slow"? First, whatever you don't use, it's not even loaded in memory. Second, bloated is all about having tons of options you don't need or use. Not about adding stuff you DO need piecemeal. Third, bloat is mostly a UI thing, not a "number of add-ons" or "too many lines of code" thing. Programs don't get slow because they are "bloated" with extra code (if it doesn't run, then it has 0 effect on their speed). They get slow because they are badly programmed (e.g. loading one big text file all at once in memory instead of having a paging system). The availability of tens of thousands of packages hasn't made Emacs "bloated", much less Vim or ST. Or even installing those packages doesn't make those editors feel bloated. Whereas something like Eclipse was bloated from the start -- because it was a very heavy design with tons of abstractions layers, ton of built-in options and visual clutter etc, created on a GCed language with frequent stops on larger codebases etc. That's even without any third party plugin added, just the Eclipse Java SE core packages.
- duncanawoods 11y agoThe parent did not say that plugins caused bloat, instead that resolving common problems with plugins (stability, quality, conflicts etc.) by pulling them into core is what causes bloat (slowness, complexity etc.) and that trying to resolve the tension between flaky plug-in based systems and bloated monolithic systems is cyclical.
- coldtea 11y agoStill: is anyone complaining of Emacs or Vim or ST3 being slow/complex because they have installed plugins to the core? What's an example in the wild of this "cycle of bloat" in which people complain about it?
- duncanawoods 11y agoI can't speak for the parent but I would say the most commonly seen effect of complexity is stagnation. Change becomes harder, promised features take forever, the developers lose motivation and significant new releases grind to a halt. Atom exists because ST3 was seen to stagnate, ST3 exists because TextMate was seen to stagnate etc. They start as simple but incomplete tools that are moving fast and blah blah - its just the software circle of life.
- matwood 11y agoAtom is cool in that it shows how much time a package adds to startup. It's also so modular that you can remove most of what you don't need or want. For your step 6, it just means disable all packages and add them back only as needed.
- zacharypinter 11y agoSee also: "minimalist web browser" and the history of Firefox :) https://en.wikipedia.org/wiki/Firefox#History https://en.wikipedia.org/wiki/Firefox#History
- jerf 11y agoYup, that one was certainly big for a while! KHTML and its whole menagerie of browsers competing to be more "minimal" than the last. I think the web has stabbed that one dead, though... ship a proper HTML5-compliant browser engine, and, well, you're already looking at a whackload of startup time and tons of functionality. The size of the chrome is hardly an afterthought nowadays. A really "minimal" browser can hardly browse the top-ten sites anymore. (Wikipedia's still looking pretty good in Lynx, though... just checked.)
- TheLoneWolfling 11y agoTry: the web itself. The amount you need to be able to do to just load a basically-plaintext webpage now is absurd.
- knodi123 11y agothat's a really good point. I used to browse http over telnet because my boss couldn't tell I wasn't hard at work. Needless to say, I can no longer do that.
- oblio 11y agohttp://www.jwz.org/doc/easter-eggs.html http://www.jwz.org/doc/easter-eggs.html My all time favorite reply about bloat: "X is big because your needs are big" (in the article X = Mozilla).
- steego 11y agoI disagree with your characterization. Take jQuery for example. 1. Small, fast and minimal. 2. Easy to create plugins. 3. Budding ecosystem and explosion of plugins. 4. Conflicts ensued and some plugins got pulled into the core project. Eventually, the growth of jQuery tapered off as the project stabilized. Not only did the size taper off, it got smaller as well. After nearly 10 years, we're talking about a payload of 30K minified and gzipped. https://mathiasbynens.be/demo/jquery-size https://mathiasbynens.be/demo/jquery-size The cycle of bloat doesn't always take hold if your team is disciplined and dedicated to keeping it small. You simply can't expect to your 3.0 to be as small as your 1.0 because it's very unlikely you're going to know upfront how people are going to use your software.
- steveklabnik 11y agoWhile this is true, and I love JQuery, there's a significant number of JavaScript programmers who do say that JQuery is bloated and slow and old and you shouldn't use it. http://youmightnotneedjquery.com/ http://youmightnotneedjquery.com/ and all that. Even if it's not actually true (as you've said, it literally is not bloated wrt filesize) people still think it's true.
- deleted 11y ago[deleted]
- jerf 11y agoKind of a good example of what I mean about how I don't care much about "bloat" anymore... it is my perception that the vast majority of people who fling the term around are not doing so after any sort of careful examination of the system in question and coming to a considered conclusion... it's mostly just an accusation more than anything else. It's not generally a very nice thing to say about a framework, even if you can somehow objectively prove it, it immediately puts the entire conversation on a very hostile footing.
- thiht 11y agoYour link explicitely says "you MIGHT not need jQuery", there's nothing wrong about that, quite often you actually don't need it at all. It doesn't say "never use jQuery"
- robogimp 11y agoThis. This needs to be a musical number along the lines of the Lion King's "circle of life"
- nchudleigh 11y agoThis is true for some projects, but with atom you can strip away core packages as needed. Just go to settings and disable!
- hawsome 11y agoYou're probably one of those people that pull in jQuery to use just the selector.
- jerf 11y agoI must say, I greatly underestimated the degree to which the word "bloat" triggers all the bad side-taking rationality-bypassing political thinking and socializing mechanisms in programmer's brains. I'd love to promise I'll never do it again, but I'm tempted to try to draw the poison out, too. Bloat ought to be a technical concept, not a political one.
- erikb 11y agoYeah the moment people realise this they tend to start to learn the basics of an old, bloated but still maintained and loved tool like emacs or vim in the case of editors. Nobody wants to relearn the same things over and over again every three years. And you can't really get away from the disadvantages software has (either too small or too bloated). But these old tools will stay. I can't access it, but I bet even my WIFI router, tv and PS4 have a vi somewhere laying around, ready to help with debugging in case a corresponding core developer comes around to take a look.
- macjohnmcc 11y agoI have suffered the same with Visual Studio addin's. My main extension Visual Assist X works great. Once you start adding others the performance gets really poor really quick.
- rndn 11y agoI do this all the time, the number of my installed Emacs packages and Firefox add-ons looks like a sawtooth wave when plotted over time.
- crucialfelix 11y agoTrue story. To mitigate this all of Atom's core are implemented as packages that you can disable or completely replace with other versions. Basic things like https://atom.io/packages/find-and-replace https://atom.io/packages/find-and-replace Facebook's nuclide project replaces a bunch of core features like the tree-view and the quick file opener. > let's pull them into the core That doesn't actually happen. They may adopt a package or publish a more official version of a package, but all major functionality is in packages.
- hollerith 11y agoYour cycle of bloat might describe many other projects, but not Atom because from the start, Atom depended on 10s of millions of lines of code -- a different copy of those 10s of millions of lines than the copy in your web browser.