Yeah there’s more stuff that runs in the shell. But pretty much all the things you mentioned would work on a VT100 from the 70s. This is about modernising the terminal itself.

Hell, Linux terminal emulators don’t even have a “clear screen & scroll-back” keyboard shortcut like Command-K on Mac. There’s no command output history, there are no auto-complete popups, editing commands is still extremely basic (no multiline input for example). The command prompt doesn’t even have the text editing capabilities of Notepad.

No the point of terminals is not to make people that dislike mice happy. They simply were created before mice were common and haven’t been updated at all. This is an attempt to do that.

Sure, but there are a gazillion forum websites already. I’d just use an existing one. The one D uses is the best I’ve ever used. I think it’s actually written in D, which is a very niche language but way nicer than Ruby.

Riiight

Sounds awesome. Good luck!

Wow, that activated some seriously ancient neurons… I just looked up some of the models it supports and surprisingly they were made within the last decade. For some reason there’s still a market for cheap dedicated MP3 players.

I guess they cost basically nothing to manufacture and some people might need them…

all genders

Uhm what?

Not unreasonable in Germany but it’s a weirdly narrow band. €57-61k?

In Europe, not in cryptobullshit? Find me one.

Ha clever.

I don’t think so. It’s more likely to be a lock-in method. Go to another AI provider and it won’t remember all the useful things you’ve told it.

I guess we’ll see if OpenAI starts an ad network…

Saying “good attempt” is just a nice platitude. It doesn’t actually mean that what you’ve done is good, especially if you follow it up with (effectively) “but you’ve got to do it all again”. I think most people understand that.

Yeah I mean obviously the technical points here are correct (and I wish my colleagues would write more robust code with less Bash and regex all over the place), but I don’t know why he thinks you need an asshole manager to deliver that message.

Over-engineered. Too many moving parts. Refactor.”

That was it. No “nice work.” No “good attempt”. Just a hard stop.

Uhm yeah, would writing “good attempt” have hurt? Obviously not. He could easily have been nice and still deliver the technical information.

Good attempt, but I think this is too over-engineered with too many moving parts. For instance x y z would be simpler to maintain, and a b c isn’t robust to 1 2 3 for example.

It doesn’t take much. Don’t be a dick.

Ha no. SQLite can easily handle tens of GB of data. It’s not even going to notice a few thousand text files.

The initial import process can be sped up using transactions but as it’s a one-time thing and you have such a small dataset it probably doesn’t matter.

Definitely SQLite. Easily accessible from Python, very fast, universally supported, no complicated setup, and everything is stored in a single file.

It even has a number of good GUI frontends. There’s really no reason to look any further for a project like this.

Ok so if I’m understanding correctly Hyperlight lets you sandbox components of your embedded system using hypervisor/VMs. Hyperlight WASM is an alternative sandbox that uses WASM for sandboxing instead.

I guess if you only have WASM there would not be much need for Hyperlight at all, but if you have a mix of WASM and non-WASM code this would be useful.

I’ve definitely seen “this is more correct, but all the other code does it like this so can you change it?”

I can’t say I entirely disagree with it either - usually the “more correct” is not “the existing code doesn’t work at all”, and keeping it consistent makes it easier to fix all of the code later, because you’re only fixing one style instead of two (or more).

So… to store encrypted data that only the user can decrypt you don’t need any fancy zero knowledge algorithms. Just have the user keep the encryption key.

For authentication you could use one of these algorithms. OPAQUE seems to be popular. I’m not an expert but it seems like it has several neat zero-knowledge style properties.

But probably forget about implementing it without a strong background in cryptography.

Don’t tease gossip? Either say “I’m quitting due to personal reasons” or give actual details “I’m quitting because I received ongoing abuse about being trans on X from several users and I’m fed up with it” (or whatever the reason was; I just guessed that).

Seems like one of the areas where Rust is least pressing, but I guess if uutils does become dominant it will be a lot easier to work on the code and add new features & tools.