He also thought that Rust integrates poorly into project with a deep C++ OOP hierarchy. That is probably still true as well.
Is there any language that can do that? As far as I know there isn't. You can use SWIG or whatever but it's just as awful as any Rust/C++ interop. There's Carbon, but that's a work in progress.
IMO if you need integration with a deep C++ OOP hierarchy your options are a) give up and just use C++, or b) pain, no matter what language you target.
The connection column indicates the connection used. USB FS stands for the usb full speed protocol, which allows up to 1000Hz polling, a feature commonly advertised by high-end keyboards. USB is the usb low speed protocol, which is the protocol most keyboards use.
USB Low Speed allows 1kHz polling too. I don't think you gain anything at all from High Speed. Keyboards probably only use it incidentally because the chip they are using happens to support it anyway.
Huh I was under the impression that you could limit it to specific applications and dbus would tell kwallet the path of the application making the request (which could be done at least vaguely securely). But upon further investigation it just uses the "appid" that the app reports which it can apparently set to anything it wants. It's difficult to find information about this stuff though. D-bus is not very well documented at all.
Interesting how do you do that exactly?
I was thinking you can just start the app that has permission to read the wallet, attach a debugger and then inject code to dump the wallet. It's definitely more complicated than reading a plain text file but not fundamentally less possible.
But really if you have that level of access it's game over anyway and you just MitM sudo and get root access, or use one of the many local privilege escalation vulnerabilities and get root immediately.
They should be keeping them in something like kwallet. But in practice they don't because a) there isn't really a single standard for that on Linux (yeay, I have to support gnome-keyring too!), b) it's a lot more work than using a plain text file, c) the UX is considerably worse, and d) the security benefits are marginal at best (especially if you have full disk encryption).
Plain text is the most sensible option.
Yeah you probably can't do to much more to pwd or yes or whatever (yeah I know about the silly optimisations). I think once you get much beyond that there are always more features you can add. Even for something like cd, people have made fancier versions with fuzzy matching and so on.
Nah it was eternally annoying that it didn't support Unix line endings. Also there are clearly a ton of basic features that people want from lightweight text editors.
A whopping 3% of their workforce.
Right but it's fast(ish) in spite of that. It would still be better with separate types.
Experience has shown that having a map as your only data structure is definitely a mistake. It's much better to support real arrays too. I doubt it would have made the implementation significantly more complex either (maybe even simpler for luajit).
If you think you need this you're doing it wrong. Nobody should be writing bash scripts more than a few lines long. Use a more sane language. Deno is pretty nice for scripting.
I found this one recently which is really good:
https://github.com/sourcegit-scm/sourcegit
Much better than most of the standalone Git GUIs, even the commercial ones.
However I don't actually use it, because I use VSCode and there's a great extensions called
Git Graphthat integrates nicely into it. It is abandoned unfortunately but it still works fine so I still use it.Here's my rating of all the Git GUIs I've tried (that I remember):
I never tried Magit because TUIs are dumb.
Also don't listen to anyone that says "just use the CLI". It's okay once you've learnt how git works, but even then you're still going to want a way to view the commit graph. Learning Git without a GUI is needlessly masochistic. Once you have learnt it you can start mixing it up with the CLI.