• 0 posts
  • 48 comments
Joined 3 years ago
Cake day: June 21st, 2023
  • I’ve somewhat recently taken TrueNAS to avoid the headache of DKMS for ZFS support.

    While it is nice to know I basically don’t have to worry about that, the rest of it is pretty painful – I can’t even install a package without manually running it in docker.

    We’ve in a CentOS/Rocky shop at work until recently, moving to Debian.

    If I has to redo my NAS, is take Debian or something and call it a day. The hassle of TrueNAS and similar distros do not really seem worth it, if you want more control.

  • I recently had to port a bash script to POSIX because my boss demands we still use at, and wants exec to look like at -f.

    99% of my time is spent in bash, so in conjunction with the POSIX spec documentation, Copilot was useful in finding a solution for >(and ...) redirection (logging related), as my bash solution was not compliant.

    It was helpful, but I still took the time to locate examples in the spec, and validate every single answer I got.

    Outside of this, it has basically never been more productive than doing my own searches, research & testing (sysadmin & “devops”).

  • I both love and hate awk – on the one hand, it provides the same/similar functionality of similar tools (sed, grep, cut, etc); but it is a bit of a bear and can be pretty slow.

    If you need more “complex” tasks done what would be cumbersome with the rest of the standard tooling, and performance is a non-issue, awk/gawk can probably get it done.

    Though, I too am trying to use it as little as possible in scripts. I think multiple subshells/pipes is still better than awk in some cases. Syntax also leaves a lot to be desired…

  • As I added in another comment, I misunderstood the DHH element of the discourse as I, admittedly, don’t know much of anything about him – I’ve heard some references here and there, but that’s about it.

    Taking a stand against things like this causes change for the better in the long run.

    That’s also fine, and I generally agree. My concern basically boils down to killing momentum by sinking a company with (probably?) sane views on right-to-repair & libre as topics.

    If the goal of a boycott is to starve the company until it goes under, because they made a move we don’t like – then that I don’t really like in this context. If the goal is to force their hand towards at least transparency, or maybe force NP to step down; then I’d support that.

  • I’ll admit I’m not up to date on the hyprland/vaxry lore – but I don’t understand the level of outrage based on this article…

    I’m also not sure why the sponsorship of a software project is necessarily being treated as a 100% endorsement of both the maintainers and their alleged views.

    I’m also not sure if infighting and purity testing will help the movement(s) right now. Once it’s the norm, sure, but it’s still a relatively fringe movement within the industry.


    Edit (2025-10-15@20:14): At the time of writing my comment, I was both unaware (and uninformed) on the DHH side of this topic. While I still think the level of outrage is maybe a melodramatic, the push back seems more warranted than it initially seemed to me. I still don’t know much about DHH beyond Rails (and even then, not much); but from what I’ve seen since my comment, the response is more understandable.