Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)F
Posts
3
Comments
1744
Joined
2 yr. ago

  • 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.

  • This has been the norm for literally decades. Doxygen was doing it in 1997 and I'm sure it wasn't the first.

  • Uhm, ship both. Most type systems are not expressive enough to 100% explain the correct use of an API.

  • In my experience unless you are pretty much immediately popping the stash it's much better just to make a branch and do a normal commit. I would recommend avoiding git stash in general.

  • To be fair they are definitely improving. It feels pretty incremental at this point though. I think we need one or two fundamental breakthroughs before we're going to see programmers actually out of jobs. E.g. if they find a way to do real on-line learning, or a way to stop the hallucinations.

  • Why? MATLAB is pretty dense normally, and most MATLAB code is hacky scripts that wouldn't bother with "boilerplate" anyway.

  • Oh that reminds me. I wouldn't recommend PIC in the 21st century but there's a really cool project called BIO that is an open source alternative to Raspberry's PIO (programmable IO). It's RV32-E with custom x16-31 registers that control the pins directly. Very neat idea.

    It's by Bunnies Huang and he talks about it in this talk about Xous.

    The hardware is (or will be) here: https://www.crowdsupply.com/baochip

    May be a bit hardcore for a beginner though.

  • Sounds like you know plenty to learn Rust.

  • Yes it has definitely changed. Before AI, writing code strongly indicated that the author had thought about the problem and put effort into solving it. Of course they could have still done it wrong but a) the chances are much higher with AI, and b) they're using up your time without spending any of theirs which breaks the social contract.

  • Yeah I think just counting fully unique lines is going to really capture the repetitiveness of a language. I think you'd get more accurate results just asking people using pairwise ranking.

  • They wanted me to make some changes and with the normal workflow that's just git commit and git push. With git send-email I have no fucking idea and it got beyond the point where I had enough cared enough to fight the process.

  • For bare metal definitely get a microcontroller and do some fun electronics project.

    Easiest to get into is Arduino, but don't stick with that because its only redeeming feature is that it's easy to get into. The IDE sucks, the build system sucks, the APIs really suck, and the code quality is very low (probably because it's easy to get into so you get a lot of inexperienced people doing stuff).

    After Arduino I would recommend either going to the Nordic nRF5x series - you can do some cool Bluetooth stuff, or even make you your own radio protocol since the radio peripheral is fully documented... Or ESP32 with Rust and Embassy is probably the most modern and slick way to do microcontrollers.

    It does require learning Rust but Rust is really really good so you should do that anyway.

    There are some extremely good videos on YouTube about that: https://youtube.com/@therustybits

    I would probably still start with Arduino though since you know C. Just don't stay there for too long.

  • Linux @programming.dev

    Best rootless remote X solution?

  • Programming @programming.dev

    How to see a graph of open/closed issues & PRs on GitHub?

  • Rust @programming.dev

    Dart Macros