People are hating on Powershell way too much. I don’t like its syntax really but it has a messy better approach to handling data in the terminal. We have nu and elvish nowadays but MS was really early with the concept and I think they learned from the shortcomings of POSIX compatible shells.

The 4k you find on streaming services can’t really be compared to the 4k you find on Blu-ray. It’s a different league. Turns out bitrate actually matters

Maybe if we curve the TV?

how is feddi formed?

Interesting, I always thought it was the dumbest and unfunniest stuff. But I mean there’s no need to appeal to me.

If they acted differently, they’d probably be liable for illegal activity that they proxy for (this is for example relevant for the DMCA safe harbor).

Anyhow, when on their abuse page, I have an option for “Registrar”, which is used for “DNS abuse”, among others.

So people from low trust score environments like Linux

Linux user here, Cloudflare hasn’t blocked access to a single page for me unless I use a VPN, which then can trigger it.

It’s been this from the very beginning. But they don’t fit the definition of a protection racket as they’re not the ones attacking you if you don’t pay up. So they’re more like a security company that has no competitors due to the needed investment to operate.

I haven’t watched the video, but maybe it wasn’t in bad faith, but the author didn’t know better. bash can be arcane at times, like when I open my old scripts I often have no clue what exactly is going on without comments. Substring removal comes to mind.

I’m not even sure what strucrued data would really mean, so I’m pretty sure it’s not useful to my usecase lol

Probably not, but to give an easy example:

~> ls | where modified >= (date now) - 30day
╭───┬───────────┬──────┬────────┬────────────╮
│ # │   name    │ type │  size  │  modified  │
├───┼───────────┼──────┼────────┼────────────┤
│ 0 │ Downloads │ dir  │ 4,0 kB │ 4 days ago │
│ 1 │ Musik     │ dir  │ 4,0 kB │ a week ago │
╰───┴───────────┴──────┴────────┴────────────╯

Here, ls doesn’t just return a string representing directory content as text, but a table where each file is an entry with attributes that have their own data type (e.g. size is Filesize while modified is Datetime). That’s why I’m able to filter based on one of them; that part isn’t part of ls, but of the shell itself. In a classic shell, this filtering would need to be handled in the originating binary in its own specific way, or you’d need to parse its output, transform it using tools like sed and awk etc. This here is a special case because ls is built into the shell; for non-builtin commands, if they offer it, you can have them output structured data as json or something else and read it into nu, like

~> ip -j a | from json | where {|device| $device.address? != null and $device.addr_info? != [] and $device.link_type =~ "ether"} | get addr_info.0 | select -o local broadcast scope
╭───┬────────────────────────────────────────┬─────────────────┬────────╮
│ # │                 local                  │    broadcast    │ scope  │
├───┼────────────────────────────────────────┼─────────────────┼────────┤
│ 0 │ 192.168.178.72                         │ 192.168.178.255 │ global │
│ 1 │ 2001:9e8:4727:2c00:3071:91ff:fed1:9e26 │                 │ global │
│ 2 │ fdaa:66e:6af0:0:3071:91ff:fed1:9e26    │                 │ global │
│ 3 │ fe80::3071:91ff:fed1:9e26              │                 │ link   │
╰───┴────────────────────────────────────────┴─────────────────┴────────╯

It’s kind of cool, but I don’t need it that often either, so I just play around with it when I feel like it.

I’m glad you mentioned nushell (it sounds like) is a more poweruser thing.

It serves a different niche. nushell is very good for working with structured data. fish on the other hand is a “conventional” shell that’s not POSIX compliant. I guess that’s why they call it “a command line shell for the 90s” because it doesn’t incorporate modern concepts, it’s just more convenient than POSIX shells.

This results in some notable differences: nushell for example has actual data types (https://www.nushell.sh/book/types_of_data.html, though they are dynamically typed by default).

All this doesn’t mean that one is better than the other. I use fish daily and just sometimes dabble in nushell because most of my workflow doesn’t require all the stuff nu offers.

Oh yeah, I never used Python myself and did some very simple (but IMHO too much hassle in bash) Go stuff some time ago. It’s a really good language for that, and if you can’t build on the target, the binary is statically linked anyways.

What’s so bad about string replace World Bash $STRING?

Just don’t microwave it.

Same, but I don’t think it was ever intended differently; I mean the word interactive is literally in the name. If you want portable scripts, use bash. For simple helpers, quickly define a function. If you feel your script becomes too long, use Python.

Stop this slander

The N64 Pokémon games aren’t that bad

Try Ritalin 4, it’s the new hot stuff

Good luck on the journey! What I meant is that over time, you’ll realize that what you did was probably not the most elegant was to do something, at least that’s my experience with my config. Like, I started with a flake with an explicit config for each machine (basically multiple nixosConfigurations) and then turned it into a lib with functions to turn a set of hosts from json into an attribute set (kind of a simple inventory done). My last efforts that are still ongoing (cough) are splitting my NixOS modules off into a separate flake using flake-parts.

I do understand you meant having the stuff that your need work, I just wanted to hint that the language is very powerful and as such, most configurations have room for improvement, as in learning to do things more efficient or do things that weren’t possible before.

Can’t have files if you don’t have a computer to store them tips forehead

None of this stuff for me. I prefer one tool doing one thing, like busybox