• 1 Post
  • 19 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle


  • If we can simply help Americans understand small-s socialism from small-c communism, we’d be in much better shape.

    Because yes, my healthcare is already paid in advance by me and everyone else from our taxes; and my buddy’s emergency Sunday morning quintuple stent install after the widowmaker heart attack and two ambulances and a bed in one hospital before transfer (a third bus) to the regional trauma/cardiac center for the operation and 2 weeks of aftercare was free to him that day – and his only concern was not dying. And that’s not just normal but that’s the general expectation. No monthly subscription, no premium cost, no user fee, just paid-parking and vendor-machine food for visitors not coming in via the train.

    Our upcoming election will gut that, though. Being bankrupt, losing retirement savings and mortgaged to the hilt at 61 is the American dream mr Polievre has for all Canadian plebes.







  • didn’t find answers [:] they’re buried in general discussions about why compiling may be better than pre-built. The reasons I found were control of flags and features, and optimizations for specific chips (like Intel AVX or ARM Neon), but to what degree do those apply today?

    You won’t build and install directly from source in any proper enterprise environment, simply because validation breaks and (provably) consistency goes with it; and that takes out reliability.

    Even accounting for the gains when you’re tuning stuff, or even when it’s a home build, or even when it’s a kernel build and you’re removing or adding drivers or tunable defaults, ultimately you will be building a package as a portable artefact to be submitted for testing or pulled out of backups for easy re-install. Especially when kernel builds take a long time, and even when you’re using makefiles for much of it, you’re STILL going to be building a package, only so you have the process encoded and repeatable and so you don’t have to re-make if it all works (more an issue when building a kernel package took 25 hours, but you get the idea).

    So. In short, if someone’s telling you to compile into production from source, it’s still a security risk and it’s also inefficient past the N=1 stage. Irresponsible for TWO reasons, then.

    Edit. I coordinated with Support while I was doing Security work in ~2005. You wanna know how to piss off your support worker and fast-track a ticket to ‘no repro’ death? “I compiled it on the machine from source …” and that goes for paid support or gitlab project volunteer support.










  • And here, last night, I was stressing over an issue with distributing the version of an app that I knew would solve the problem caused by this other app being only a facsimile of the one it replaced, and is there for missing some important compatibility.

    But new is shiny so fuck ‘usable’.

    So I was grabbing this other app to do the thing I knew it could, but this app was first built 18 years ago, and last major update - security not feature - was 9-10 years ago. The app is feature-complete and it’s not fucking systemd so it can stop at being perfect for its primary use.

    But then its python interpreter has left it behind, like “fuck you this can’t even run”, because they fucked wit the api without thinking. And now this app is just abandonware.

    I think that’s two sides of the same coin: you have inept answers from people practicing robotic responses, and my thing was killed by eager-beaver devs who cut off features they don’t understand or value, just like a civil war surgeon treating athletes foot. Similar, my shit won’t ever run again either.

    (No I don’t know python yet. Too busy working to learn it; and also indentation disco sucks)