Death of the Power User

[dbannon]

Here is a blog entry, that while just a touch long certainly rings a bell, for me at least. It relates to the current discussion about AI, newer programmers needing higher level languages and that general feeling that everything should be 'easy' even if at the expense of privacy and functionality.

https://fireborn.mataroa.blog/blog/the-slow-death-of-the-power-user/

I don't think anyone one here will be surprised about any part of it to be honest.

Certainly, my pet hate is the trend on 'devices' that its not the user's business as to where a 'document' is saved, some propriety company will look after that.

Davo

[Thausand]

Good read, thank you dbannon.

[440bx]

The points he makes in that article are so true and, as he points out, it's only going to get worse while everyone will openly agree that the opposite is the right way while accepting, if not celebrating, being manipulated because the result is "easy".

Good read, thank you dbannon.

I agree and thank you Davo.

[VisualLab]

An interesting look at issues of ownership, privacy, and the ability to manage one's life without the oversight of "big brother." Mainly, however, the article relates to matters related to computers, software and data. I agree with 90% of the content.

And what about that remaining 10%? Well, they are completely wrong. The most important thing that is not true is the naive belief that the command line is the path to "IT salvation." In reality, the command line is a relic of very old times. A time when computer hardware and much of the software were provided by a few IT "big brothers," exceptionally nasty corporations, just as powerful and greedy as those of today. And the hardware itself was exceptionally primitive and crude, yet outrageously expensive. Back then, the only way for a person to communicate with a computer was by "typing incantations" — portions of text. Of course, there was no other option back then. But back then, these spells were few, and the hardware had limited capabilities. That's why it was relatively easy to get familiar with it in a relatively short time.

Today, computer peripherals and the capabilities of current hardware abound. And software is incredibly complex and extensive. What's more, today we can use computers in areas that were only in the realm of dreams back then. And I'm not referring to entertainment, but mainly technical, scientific, and utility applications. There's no need to "memorize" various "spells." This is especially true since there are incomparably more of them and they are more complex, so the risk of making a mistake and causing damage to the computer increases. Just look at how this is implemented in Linux. This is a classic desktop anti-pattern (server is a separate issue). Meanwhile, a GUI definitely makes work easier. But there's a catch. Whether a GUI provides the user with enough feedback depends on how the programmer designs it. If he is lazy, lacks knowledge, or wants to deliberately make life difficult for the user, the GUI of his software will be clunky and cumbersome to use. In the case of the command line, even if the programmer is very knowledgeable, hardworking, and not hostile to the user, the software will be cumbersome to use. Because the command line is simply primitive as a concept of human-computer communication. And it will remain that way. Yes, it can be useful sometimes, for example for server administration. But for everyday desktop work, it's ineffective.

The second issue is that the nasty trend of blocking or making it difficult for people to use software is also present in the open source world. Example – 15 years ago you could tinker with Linux as much as you wanted. But around 12-10 years ago, a nasty trend began to emerge of making it harder for users to tinker with the system. A classic example is blocking the root account, especially in the GUI. And I'm not talking about corporations like Red Hat or similar companies. This is done by people focused on "liberty" distributions like Debian. The official narrative is that the GUI is dangerous, that the well-being of the user is important. I have no problem unlocking the root account. But most people can't. This practice contradicts the open source movement's past declarations of freedom to use your own computer. And then there's the lament in the open source media that Linux is unpopular. Another thing is that Linux on the desktop is a mockery of the user. Anecdotal arguments like: "I installed Linux on my grandmother's, mother's, grandfather's, dog's or hamster's computer and they run on the computer without any problems" make no sense. Yes, these people run Linux — using a web browser they barely learned how to use.

But getting back to the point (i.e. 90% of the content I agree with) – part of these pathological trends is also the popularization of Python or JavaScript and pseudo-applications written using monsters such as Electron. These poor, poorly designed scripting languages ​​perfectly fit the narrative described in the article: "there's no need to delve into how something works, because there are so many libraries for Python or JS." And the AI ​​will "write" the rest of the script, so why bother? So now "we have" Python even for microcontrollers (CircuitPython, MicroPython).

This idiotic (and also stultifying) narrative has also been joined by the people who originally popularized the development of electronics and software education "from the inside out." For several years now, the Arduino IDE has been developed as an HTML/CSS/JS based “application”. In the case of the Raspberry Pi Foundation, the situation is worse, because from the very beginning they promoted Python alongside C. So it's hard to be surprised by the results.

[Curt Carpenter]

Reminds me of the old meditations in the ham radio community about the "appliance operators" vs. the guys that built their own equipment from scratch. 

[Jonax]

Interesting reading. Thanks for sharing Davo.

[Thausand]

The points he makes in that article are so true and, as he points out, it's only going to get worse while everyone will openly agree that the opposite is the right way while accepting, if not celebrating, being manipulated because the result is "easy".

Yes, and when have good see then this is happen around for all life category. It have result there many less original idea and thought for result.

@VisualLab
I have basic agree with you write but I think there is good english say (I hope it right): "Those who cannot remember the past are condemned to repeat it".

That is mean that when you not have understand how was make foundation then not have knowledge for how thing is become current. I have agree that is not mean is need for go back but is important for know past (and may be try and have past experience. It is imo help for beter understand why/how thing is work today and not make same mistake (again))

[dbannon]

Well, VisualLab, I will, of course, focus on your 10%

The most important thing that is not true is the naive belief that the command line is the path to "IT salvation." In reality, the command line is a relic of very old times.

If they took my command line away, I'd give up using computers. Seriously, we have arrived at different positions by travelling different routes, whats so surprising ? I drop back to the command line when I find it necessary, I sure can do some things there, quicker and more efficiently. You don't, thats OK.

The second issue is that the nasty trend of blocking or making it difficult for people to use software is also present in the open source world. Example – 15 years ago you could tinker with Linux as much as you wanted. But around 12-10 years ago, a nasty trend began to emerge of making it harder for users to tinker with the system. A classic example is blocking the root account, especially in the GUI.

Two case you quote, 1) an absolute block from root ?  and 2) a block from using the GUI as root ?

First one first, can you name a general purpose Linux distro that blocks access to root ? I cannot.

Second one is much, much deeper and I suggest we would not reach agreement on that one, ever!

Anecdotal arguments like: "I installed Linux on my grandmother's, mother's, grandfather's, dog's or hamster's computer and they run on the computer without any problems" make no sense. Yes, these people run Linux — using a web browser they barely learned how to use.

And that only applies to Linux ?   Lots of people only use their computers for browsing or email. It serves their purpose, thats fine by me.
 

But getting back to the point (i.e. 90% of the content I agree with) – part of these pathological trends is also the popularization of Python or JavaScript and pseudo-applications written using monsters such as Electron.

You forgot Java.  And C++ with cmake ?  Who on earth actually understands whats happening when they run a compile ? Its learn by rote.

For several years now, the Arduino IDE has been developed as an HTML/CSS/JS based “application”.

While I agree with you in principle, I have to say that the Arduino IDE actually works OK. Certainly not in the same class as Lazarus but does work. I use it to programme some ESP32 boards and far, far easier than following Expressif instructions. Using c++ and cmake).

In the case of the Raspberry Pi Foundation, ...

... its quite hard to say something nice.

Davo

[tooknox]

Because the command line is simply primitive as a concept of human-computer communication. And it will remain that way. Yes, it can be useful sometimes, for example for server administration. But for everyday desktop work, it's ineffective.

Well that's the whole point with CLI, it's primitive and it works. I (and others like me) can't actually function without it. The point is a balanced and reasonable coexistence. You don't like it, that's perfectly fine you interact with your computer the way you like. CLI is quicker, effective and way more efficient for the work I do.

@dbannon made the rest of the points so not gonna re-iterate it.

I can always find alternatives and a way out of most situation. I can stay away from JavaScript. Python was/is great, but then they started using it to mow their lawns and in everything they can think of, but that's also fine as long as suitable alternatives exist. The tribalism with programming languages is expected and is mostly harmless unless you hang out with a rust fanboy (/j I love rust).

What really irks me is the whole mobile-tech situation. ARM was supposed to be the salvation, and I was hopeful that one day the mobile hardware will be standardized, and we will have a boot spec just like the PC but post iPhone everything started getting locked (not iPhone's fault just using it as time reference). Now we have locked bootloaders, no way to use my own hardware (securely) post the manufacturer official support. Custom ROMs are getting rarer and Google pushing for dev identification to install apps in my own hardware. The infection has reached laptops too, but I guess that's not as serious as smartphones.

[VisualLab]

@VisualLab
I have basic agree with you write but I think there is good english say (I hope it right): "Those who cannot remember the past are condemned to repeat it".

That is mean that when you not have understand how was make foundation then not have knowledge for how thing is become current. I have agree that is not mean is need for go back but is important for know past (and may be try and have past experience. It is imo help for beter understand why/how thing is work today and not make same mistake (again))

The most important thing that is not true is the naive belief that the command line is the path to "IT salvation." In reality, the command line is a relic of very old times.

If they took my command line away, I'd give up using computers. Seriously, we have arrived at different positions by travelling different routes, whats so surprising ? I drop back to the command line when I find it necessary, I sure can do some things there, quicker and more efficiently. You don't, thats OK.

We didn't understand each other. The paragraph I wrote about the command line didn't suggest its elimination or oblivion. Well, in the article (link attached by dbanon) there was an enigmatic suggestion that it is a remedy for the widespread lack of knowledge about how computers and programs work. And I just gave a quick reminder that this is not the case. Knowing how computers and software work is much more than the command line, and it's different from the command line itself. The command line is only a part of that knowledge (or rather, a small part of it). What I meant was that the user interface depends on the user's needs. For some tasks the command line is suitable, while for more complex tasks the GUI is better. I can't imagine using the command line to show in detail the mechanism of a chemical reaction or analyze a chemical installation. But for supervising the server's operation, the command line is sufficient. "To each according to his needs"

The second issue is that the nasty trend of blocking or making it difficult for people to use software is also present in the open source world. Example – 15 years ago you could tinker with Linux as much as you wanted. But around 12-10 years ago, a nasty trend began to emerge of making it harder for users to tinker with the system. A classic example is blocking the root account, especially in the GUI.

Two case you quote, 1) an absolute block from root ?  and 2) a block from using the GUI as root ?

First one first, can you name a general purpose Linux distro that blocks access to root ? I cannot.

Second one is much, much deeper and I suggest we would not reach agreement on that one, ever!

It's mentioned in my post But I'll repeat: Debian. Some derivative distributions do this too. I would understand if it were a server distribution. But that applies to the desktop.

Anecdotal arguments like: "I installed Linux on my grandmother's, mother's, grandfather's, dog's or hamster's computer and they run on the computer without any problems" make no sense. Yes, these people run Linux — using a web browser they barely learned how to use.

And that only applies to Linux ?   Lots of people only use their computers for browsing or email. It serves their purpose, thats fine by me.

It was ironic. I have been coming across such explanations on various Linux forums for many, many years, so I cited them in my statement. According to people who use such nonsense, Linux has long been ready for the desktop. Meanwhile, serious discussions about the Linux desktop do not concern such cases but more complex work. This is due to the fact that people who point out the shortcomings of the Linux desktop have knowledge about this system (and generally would like to improve the quality of work in it).

But getting back to the point (i.e. 90% of the content I agree with) – part of these pathological trends is also the popularization of Python or JavaScript and pseudo-applications written using monsters such as Electron.

You forgot Java.  And C++ with cmake ?  Who on earth actually understands whats happening when they run a compile ? Its learn by rote.

I didn't so much forget as I only mentioned the most glaring cases of IT pathology. Because they are closely related not only to a lack of knowledge but also to an unwillingness to acquire it. But I agree with what you're writing. Java is an example of "style over substance." In turn, the build system in C and C++ are true relics of the past that should be shown to programming students as anti-patterns: how not to design a build system. They should definitely be phased out, as it has serious consequences, not only for IT but also for the economy. But corporate boards won't allow this. They would have to spend too much, even though it would bring them tangible benefits over time. They prefer short-term profits (thinking along Jack Welch's lines). For these people, knowledge isn't that important.

[VisualLab]

Because the command line is simply primitive as a concept of human-computer communication. And it will remain that way. Yes, it can be useful sometimes, for example for server administration. But for everyday desktop work, it's ineffective.

Well that's the whole point with CLI, it's primitive and it works. I (and others like me) can't actually function without it. The point is a balanced and reasonable coexistence. You don't like it, that's perfectly fine you interact with your computer the way you like. CLI is quicker, effective and way more efficient for the work I do.

We misunderstood each other – I wasn't suggesting eliminating or forgetting the command line. The article (link provided by dbanon) suggests that it is a remedy for the widespread lack of knowledge about how computers and programs work. I merely mentioned that knowing how computers and software work is much more than the command line. The command line is only a small part of this knowledge. Furthermore, what I meant was that the user interface depends on the user's needs. For some tasks, the command line is suitable, while for more complex tasks, a graphical interface is better.

I can always find alternatives and a way out of most situation. I can stay away from JavaScript. Python was/is great, but then they started using it to mow their lawns and in everything they can think of, but that's also fine as long as suitable alternatives exist. The tribalism with programming languages is expected and is mostly harmless unless you hang out with a rust fanboy (/j I love rust).

If someone is developing server-side software, they can (theoretically) use Pascal or Object Pascal. But it will probably be difficult for him to avoid contact with JavaScript. Because, ultimately, the content must be displayed in a web browser. Using JavaScript for any other purpose is barbaric, lazy, ignorant, and sloppy. Everyone knows that JavaScript is not suitable for creating serious software, but there are more lazy and ignorant people than sensible people. And that's why they win "en masse"

As for Python, in my experience it's terrible. It's a classic cheap makeshift solution, the IT equivalent of something made of plywood, tied with string, and taped together. Of course, the aforementioned materials have their uses, but not everywhere. It's similar with Python, simple quick scripts for one-time use - OK. A temporary fix isn't a permanent fix. And unfortunately, Python's popularity (but JS's too) reflects the masses' reluctance to delve deeper, even to see which solution offers better quality.

As for Rust, there is no complete opinion yet. But... I've noticed that its syntax is becoming increasingly confusing, probably more so than C's syntax at the moment. This won't increase its popularity. On the other hand, I've recently begun to wonder if it's technically possible to add borrowing checking to FPC.

What really irks me is the whole mobile-tech situation. ARM was supposed to be the salvation, and I was hopeful that one day the mobile hardware will be standardized, and we will have a boot spec just like the PC but post iPhone everything started getting locked (not iPhone's fault just using it as time reference). Now we have locked bootloaders, no way to use my own hardware (securely) post the manufacturer official support. Custom ROMs are getting rarer and Google pushing for dev identification to install apps in my own hardware. The infection has reached laptops too, but I guess that's not as serious as smartphones.

Android is already "concreted" by "Big Brother", where the user is supposed to be (or maybe already is) a little rat who regularly (and often) buys newer and newer versions of smartphones. And this is without delving into how it works and without the desire to "dig" into the hardware and software. And because corporations (at least for now) can't prohibit this kind of tinkering, they resort to various "obstacles" and scare ordinary users with various threats. When it comes to smartphones, Google is probably even meaner than Microsoft. But the real cause of the problem is that these large corporations have become monopolies in their respective areas of operation.

[dbannon]

It's mentioned in my post But I'll repeat: Debian. Some derivative distributions do this too. I would understand if it were a server distribution. But that applies to the desktop.

I'm writing this now on Debian Bookworm, recently used Debian Forky (ie testing) and don't have any problem becoming root. I typically use sudo and, (maybe what you are talking about,) yes, you have to add yourself to the sudoer group, thats silly but not malicious. It reflects debian's excessive conservatism.

In turn, the build system in C and C++ are true relics of the past that should be shown to programming students as anti-patterns: how not to design a build system.

Actually, cmake is pretty modern, the problem is c++ with its innumerable units and cmake's determination to "protect" you from that. The 'old' make was not that easy to work with but probably did not scale into a c++ world. I was once, long ago, reasonably competent with C, now shudder in fear if I need to touch C++.

Davo

[VisualLab]

It's mentioned in my post But I'll repeat: Debian. Some derivative distributions do this too. I would understand if it were a server distribution. But that applies to the desktop.

I'm writing this now on Debian Bookworm, recently used Debian Forky (ie testing) and don't have any problem becoming root. I typically use sudo and, (maybe what you are talking about,) yes, you have to add yourself to the sudoer group, thats silly but not malicious. It reflects debian's excessive conservatism.

I don't mean sudo. For several years I have been using Linux mainly with SBCs such as Raspberry Pi, Up Squared and recently Orange Pi 5 Plus. I use them for experiments with hardware - various electronic modules (binary, I2C, SPI). I'm not interested in using SBCs as servers, routers, etc. During these experiments, I repeatedly recompile and run various test programs (largely using FPC and even Lazarus). Therefore, I try to simplify my work. That's why I prefer using a GUI, and for that, I need a root account. The less "spell-typing" in the console, the faster and more convenient the work. And Debian and its derivatives are trying to make this so difficult that Microsoft and Google could be proud of them. Of course, I then "dig" in the system. But it's annoying if you have to do it after every system installation, because in each subsequent or newer distribution something works differently.

[creaothceann]

Can't you install copy a portable version of Lazarus onto the system?