Tztztz…didn’t he know that a full virus protection is only achieved when you run apps that run ads?

Recursion

"

To me in most cases it’s the opposite. I don’t watch video tutorials to solve a specific problem (sorry, Roal Van de Paar!), but to get into something. And therefore I prefer to see the problem solving in between and the workflow for that activity. If it really tends to waste my time, I just skip forward.

I will do everything I can do to stop this.

I can see that this can be interpreted as a sabotage. If they are dressed like a clown. With a gun and a pack of sandwiches.

I use it as the default shell only in my terminal (with fish completion). You still have to deal with breaking changes and inconsistency. On top of that, you need to wrap a lot of your commonly used commands and tools to take full advantage of it. But personally I consider it worth learning and using. Not only do I hate working with raw text, I also love the visual and interactive data representation. And working with existing tools is honestly not a huge problem. It’s just what you’d usually do regularly. Obviously POSIX-compliant shells in combination with many tools like jq, too are already capable of nushell’s power. But I just like to have it included in the shell language, so I can work with the data more casual.

I couldn’t tell you why you’d use it instead of Powershell. I just never tried Powershell on Linux.

Why should they? Less users are programming anything, but more people have become users of computers in the first place. And we have more users of computers, precisely because the levels of abstraction do not require the ordinary user to program anything. Today’s ordinary user is more “ordinary” than fifty years ago. This development of making a tool or subject more accessible to the layman, by hiding the complexities with abstractions and yet allowing more skilled users to gain advantages by peeling away the abstractions, is present in many different fields throughout the history of mankind.

If you look closely, it is not really surprising. Not even a problem at all. In fact, if you have the simple understanding that maybe somebody doesn’t want to program, not because they are a stupid idiot or a lazy normie consumer, but because they simply don’t give a shit about it, follow other interests and can contribute to the world with other skills, then the observation that most users are not programming anything, is insanely unproblematic.

Me, too, and it works for other Linux distros, but in this case it’s a Windows Sandbox. Unless it’s copy and paste, for this case it wouldn’t be worth it and I assume there can be similar situations in the future for other reasons.

I once started to work on auto-setup scripts for Windows, but the unpredictable nature of it made me give up on that :D

Since fish abbreviations get replaced by the actual abstracted content before the execution, I’m more concise about the tools. And thus I’d remember the ways without my setup better. Then again, it only works for small stuff.

This is cool! It doesn’t fit my current situation. The temporary system I’m dealing with now is a Windows Sandbox for a school project. While it could take a few minutes to install winget and the necessary tools, I’d rather not risk the potential of troubleshooting time, because of the limited amount of time I work on it physically (and because I’m cursed with troubleshooting nightmares on Windows).

But I’ll have a look on xxh. It could definitely improve my comfort with servers that do not maintain nushell packages.

Thank you! That’s exactly what I need, but I probably have a unique case where I as the developer am the cause for the feature creep myself. For work, luckily our product is an ERP software, so in most cases I’m naturally uninterested for more features :D

But I do choose this approach for these problems to not have reusable code on purpose xD I’m not try-harding to rewrite everything for every feature separately, so most of it would be separated and modular, as long as it’s required by the initial purpose of the software. However I avoid writing generic and reusable code that only gets rewarded with functional scalability in mind.

And unit testing is honestly not on my list for these kinds of projects. At best I’d write integration tests to challenge the route handlers. But simply using the software is sufficient to cover the predictably unpredictable usage in these cases.

Thanks for the recommendations. A missing understanding of what needs to be reusable could be a problem. E.g. in my example when I add a DAO-like interface just to implement it for the two entities I have, I invite my future self to add unnecessary features to make more use of that interface and other generic components.

I use mostly Rust. I meant “extending” in terms of features.

It definitely is and I wouldn’t take this approach mid-way for a project with multiple users and contributors. But it works for my little projects that desperately need me to be the user more than the developer. An example would be a REST API with a few endpoints where the database operations are handled directly in the route handlers uniquely for that specific task.

Yes, the better solution is probably not on the programming layer :D I was still interested in a specific term to this approach to look up to what extent somebody can drive this.

Whether it’s 15 seconds, minutes or hours doesn’t matter, because they care about the decision that we make immediately.

If we’re talking about people who simply make video content about software development, then the biggest impact I see is a bigger reach for any tool that needs to be seen in action or simply sounds too strange on paper. In recent years HTMX was probably affected the most.

I see that a lot of people boil it down to tutorials, but there is so much more content about software development.

Being able to find a solution instead of a huge amount of bloat is Linux specific.

Every time I see the example of people used to Twitter complaining about Mastodon’s UX and UI, the experience of using the Twitter app and the constant struggle of figuring out whether the non-sense anomaly you see is a bug or just a feature to keep you locked in is becoming an even more painful memory…