The case for Nushell, https://www.jntrnr.com/case-for-nushell/.
Relevant article about shells, and how Nushell pushes the boundaries further. I highly recommend reading it.
The case for Nushell, https://www.jntrnr.com/case-for-nushell/.
Relevant article about shells, and how Nushell pushes the boundaries further. I highly recommend reading it.
@hywan @Keltounet Question: "can the state of shells be improved enough to overcome the inertia of sticking to what you know?"
This is the wrong question. It presupposes zero cost of transition, while the cognitive workload of learning a new shell rises exponentially with age (hint: I'm nearly 60, shells are harder to adapt to than a new GUI). Stability and continuity are essential prerequisites to productivity!
@Keltounet @hywan Computing is not my job. It hasn't been my job for over two decades. Time spent learning a new shell or thinking about computers is time *wasted* from the non-compsci point of view.
Thing is, the question about the utility of switching to a new shell has embedded ideological assumptions that implicitly privilege computing over applications. To 99% of the world applications of computing are the priority; the machines and software are just an annoying drag on getting stuff done.
@jyrgenn @jmccyoung @cstross @Keltounet
[edit: oops, I must have applied the 'not' to two clauses and not just the one, apologies! I'm leaving this here to not make the replies look weird, but can remove if you want]
fwiw, all of these have a *time cost*, and most people cannot dedicate a hobby worth of time for the weeks it takes just to get their functionality back
@NireBryce @jyrgenn @jmccyoung @cstross @Keltounet yeah, but this entire conversation opened up with Charlie Stross scoffing about how technocapital looks down on and flattens everything under its gaze because it cannot help but See Like A State, and now people are casually eliding the difference between the accessibility requirements of the GUI and command-line shells as if they're the same thing.
so are we supposed to be discussing this with nuance or are we moving on to "new UX is bad therefore let's make everyone work to death with pickaxes and shovels"? because the last time I heeded people on "just leave old people alone, they can't learn new things" my grandmother never learned my proper name before she died. or do we want to perhaps consider that perhaps someone's hobby project isn't a sinister plot to uninstall bash from your computer?
You probably didn't mean to "waddabout" there but I regret to inform you that's how it came across.
The point under discussion seems more like,
"Is there room for incremental improvement which does not require a whole new way of working with a computer every few years?"
I'm learning 3 human languages in my 40s and regularly pick up new skills related to computing but also, "please stop changing stuff for what feels like change sake".
@cvoid @Keltounet @cstross @hywan
Software in "the cloud" has fully unleashed this form of petty violence and theft of time.
It's astoundingly arrogant, as though somebody grants themselves permission to rearrange others' desks in the dead of night.
@tshepang @Keltounet @hywan UI changes in corporate products seem to happen purely to justify the product manager's request for a pay rise at their annual review! And at Google, old products get killed ruthlessly to make way for new products because that's the only way a manager can earn promotion.
This shit is actively hostile to the users' interests, but it's ubiquitous.
I mean, Canonical think 5 years is "long term stable" for Ubuntu, which is bullshit: should be AT LEAST a decade.
@cstross @tshepang @Keltounet @hywan I mean, on the other hand, 10 years LTS is... really expensive if not impossible. Computers are not some magical thing frozen in time. Maintenance costs rise fast, and not linearly with time, especially with context change.
I totally agree with your point on the UX change ofc, but for example, in terms of shell, as he mentioned in the article... Nushell is not really meant to replace your use of shell. It is built to replace glue scripts. And yes. needed.
@Di4na @tshepang @Keltounet @hywan
"Maintenance costs rise fast"
... which is why IBM mainframes still happily run Series 360 assembly programs from the early 1960s, the hardware is all hot-swappable and fault tolerant, and the main backward compatability issue is finding folks who know what the bottom of the application stack is even supposed to do (the original designers all died of old age).
The inevitability of perpetual churn is a lie. It can be avoided.
@cstross @tshepang @Keltounet @hywan I mean yes, it costs so much to run stuff still on these machines that the estimated cost reduction from moving away from them and paying for the churn is regularly considered order of magnitude cheaper than to keep paying that cost. Ofc the cost of switching is high because it has accumulated over time.
I have seen the accountant doing the maths, I have been in these rooms. It can be avoided, totally. But the costs is rarely one anyone is ready to pay.
@cursedsql @cstross @tshepang @Keltounet @hywan multiple things.
But mostly, because these parts are not the cost. The costs are the design of the board to fit them to our needs. That cost has dropped a bit but not that much. And if you go find an electronic board from 50years ago, you will quickly find out that most of the part are not produced anymore. That it is the wrong voltage for the modern part that replaced them. That the connectors do not fit. Etc.
The parts still exist. Sometimes.
@cursedsql @cstross @tshepang @Keltounet @hywan but combining them together in a way that fit your current needs and the rest of the world they interact with? Not so much.
An example. Most of that IBM 360 emulated stuff mentioned above? Only handle really specific text encoding. Better hope you do not need an apostrophe or an accent in your last name.
@cursedsql @cstross @tshepang @Keltounet @hywan also better hope you don't plan to still use them by 2039. Or that someone was paid to handle the millenium bug.
Even if the parts stay still, the world does not.
@cursedsql @cstross @tshepang @Keltounet @hywan you realise i spent multiple years of my life trying to rebuild electronic cards to keep high speed trains from 50 years ago running?
Also the ibm 360 was less than 1% of the systems at that time. It surviving is an exception showing how hard it is. And costly. And how only a few can do it?
@Di4na @cstross @tshepang @Keltounet @hywan the idea that a stable UI is something “magical” is pretty bizarre.
Required changes in gesture or keystroke should be carefully minimized and the vast majority should be optional.
Backwards compatibility is THE most important feature of any software product upgrade, but somehow that seems to be a forgotten principle. It’s perhaps only a small part of why we have a sense that our devices are losing rather than gaining utility. But it’s part of it.
@mtobis @cstross @tshepang @Keltounet @hywan ah yes, the most important part is to keep the UI that most of humanity cannot use.
Magical indeed.
@Di4na @cstross @tshepang @Keltounet @hywan
Nothing prevents a complete UI upgrade as long as the old one is still the default for existing users. But changing either the existing UI or any existing APIs for existing users is a betrayal. I don’t understand why this isn’t obvious.
@mtobis @cstross @tshepang @Keltounet @hywan and i don't understand how my point is not obvious either.
So maybe we should both realise our arguments are not as strong and evident as it looks.
@Di4na @cstross @tshepang @Keltounet @hywan
Yes perhaps I miss your point.
Mine is that i do fail to see why machines that are two orders of magnitude more powerful than thier predecessors can’t do exactly what their predecessors did in exactly the same way.
Maintaining software shouldn’t be a major expense. If it is, I think it is usually indicates a misdesign at some level of the stack. I can think of exceptions, but usually.
@Di4na @cstross @tshepang @Keltounet @hywan
I guess you're talking software services, while I'm talking local executables. But that's a key part of the enshittification process.
e.g. I just want to run the version of Photoshop I (thought I had) bought. I don't want Photoshop as a "service".
@Di4na @cstross @tshepang @Keltounet @hywan
An interesting example is that I had built an artistic style around pushing a feature of iPhoto to an extreme. Some might call the result buggy.
I did an OS upgrade and my iPhoto was "upgraded" with it. As a consequence the "bug" I had come to enjoy went away, and I stopped producing anything of the sort.
Maybe I was in a very small group. Maybe I was alone. But **I** didn't want the upgrade and should have been given the choice.
@mtobis @cstross @tshepang @Keltounet @hywan because it is not a car. It is the car, the road, the bridge and the pollution regulations. It depends on a ton of code that does not ship with it but with the computer that also change.
Way to talk to a graphic card, memory, way to understand mouse inpute and sounds, way to draw characters on the screen or how to explain which colour is which. Ways to open a file. Code from the 90s does not magically run even if you have the old version.
@tshepang @Di4na @cstross @Keltounet @hywan Someone closer than me to commercial coding should answer but I’d suggest that a satisfied user who can achieve their goals doesn’t need to buy more software.
So the business model needs to set up either subscription models or ways to break what already works and force replacement.
“planned obsolescence”
@Di4na @tshepang @cstross @Keltounet @hywan
It's certainly a real motivation, whether conscious or not.
Like any long-time intensive user, I have lots of stories of things going away for no apparent reason, which was infrequent in the 80s and 90s and 00s. So how is this not a decline in utility in exchange for all your efforts?
@mtobis @tshepang @cstross @Keltounet @hywan and yet i can buy a super cheap pretty resilient and safe toaster for a lower price than in the 80s and that works as well rn.
So it seems... that you are comparing different products and wondering why one has different modalities than the other.
It is because they are not actually the new version of the older. They are a different one.