• 0 Posts
  • 161 Comments
Joined 1 year ago
cake
Cake day: November 13th, 2023

help-circle
  • Don’t feel stupid. It’s bad enough that all of IT is one giant impostor-syndrome support group. There’s literally too much for any one person to know, and it’s been that way for a very long time. Just give it your all, and memorize how to reliably search and look things up; take notes for the really important stuff. The rest will filter into your memory with practice.

    Also: anyone that holds this kind of thing over your head is attempting to distract from how much they don’t know. Most people in this industry understand and don’t judge.

    As for the ^ thing, I recall seeing that as far back as the 1990’s. I want to say Microsoft actually popularized it, but it could easily be OS2 (IBM) or Apple. In hindsight, it’s kind of wild to have a TUI (terminal user interface) hold your hand like this. Nano (and Pico) are kind of in a special category like that.









  • I agree and disagree.

    The premise is solid: unify config so it’s standardized and machine parse-able for better integrations like an easier-to-build UI/UX. It could even have ramifications for cloud-init and older IaC tech like Puppet.

    The problem is Linux itself. Or rather, the subsystems that are cobbled together to make Linux a viable OS. You’re not going to get all the different projects to pivot to a common config scheme, so this YAML standard would need a backend to convert to/from whatever each little deamon and driver requires. This creates a few secondary problems like community backlash (see systemd), and having multiple places where config data must be actively synchronized.

    I think the current crop of GUI config systems are aleady well down the most pragmatic path: each config panel touches one or more standard config files, wherever they are, and however they are structured. It’s not pretty under the hood, and it’s complicated, but it works. These tools just need a lot more polish on the frontend.








  • Following the path of other regimes around the world, the USA builds their own “great firewall”, segmenting most people here away from the global internet. At around the same time, personal VPNs become explicitly illegal. We might also see the government seize control of at least one certificate registrar, if they don’t fire up their own, thereby “owning” TLS online.

    On the upside, there’s a chance we will see more grass-roots efforts to reboot a lot of institutions that were co-opted by the rich. You’re just never going to hear about that through conventional channels. For instance: local newspapers with real journalism behind them. Or more small businesses with the intent to last, rather than sell. It’s possible that more of those things will be co-ops, union shops, or even Mondragon inspired. Either way, there’s a path forward for more community, real communication, and eventual prosperity, provided folks keep their heads and take things offline where necessary.





  • As someone who just picked through the Zig docs (take this with a mountain of salt), Zig has a few things going for it:

    • spec is simple and closer to C in scope
    • modern language design, toolchain, and overall ergonomics
    • Go-like struct & interface system
    • 1st-class C interoperability

    Go foists co-routines on you and the runtime, and Rust has the borrow checker. Both of these things deeply impact language design, standard libraries, and the overall developer experience. So Zig might actually be a “more modern C” in many ways which makes it a contender. That said, it’s not a 1:1 comparsion since it lacks everything else that C++ does: you’d have to re-envision your software designs as something other than OOP if that’s what you’re used to.