I was surprised recently as I had to fill in a massive form based site for UK NHS mental health survey stuff. The site appeared as a flat background old style early 2000’s sort of thing with bits of comic sans in it. I nearly died when I first saw it expecting a shit show.
But it turned out to be responsive and fast. It worked perfectly from end to end and had little to no JavaScript. It was by far the best thing I’ve used for years. There were over 100 page transitions in total. It wasn’t an SPA but a classic web site with little or no intelligence. Seemed to be backed by python.
I think “Linux supported” is a vague promise that should not be relied on. I had a T495s which is supported officially on Ubuntu 18.04 LTS. And it was quite frankly broken. Closing the lid didn’t work, it drank batteries faster than windows by a mile and plugging in external displays caused the X server to crash.
This is unfortunately every experience I’ve had with Linux on native hardware to some capacity in the last 24 years of using it other than dumb headless servers. So I use windows as the native OS and virtualise anything else.
I totally get that. I did exactly the same. Cost £8 at the time if I remember as well which is a hell of a lot of money for an LED. It was just so different to the yellow, red and green ones. I was buying a bit of the future.
But roll on to today and the things are mostly a nuisance
In my life. I’ve got one shining at me off my monitor now. If I scoot myself up in my chair a bit it doesn’t annoy me as much. I may stick some tape over it.
Still, RIP Mr Akasaki. Your contribution to the world is a net good one. Without it we probably wouldn’t have white leds :)
I remember there was a phase in the late 90s when all of the premium gear had blue LEDs. I remember a Cambridge Audio amp rack and CD player a flat mate had.
Now of course they are used on all of the most tacky direct from China stuff.
That's hard to say upfront. Last time it was systemd-homed randomly blocking ssh access to remote systems where it was not even configured to be used, other than distro sticking its pam module to default pam config. What will be the killer future this time is yet to be seen.
My last systemd mystery was nohup, tmux, etc, not being able to leave a process running. "Working as designed", sure, but it took a while for me to suspect systemd was involved and figure it out.
Is there a document somewhere that shows what the systemd team thinks is a functional boundary? What things they don't plan on replacing?
Why a disabled feature that should just do nothing even if its pam module is loaded, infinitely loops on D-BUS access in its pam module?
Anyway, I reported it and it presumably got fixed. I wouldn't know, because systemd dev handling this didn't say a thing to me at all. Just closed the report after some seemingly not very related commits to what I saw in gdb.
I just dropped the pam module from config anyway, and I'm not willing to lose access to my cluster again just to try.
Not sure how distro fucked up in this case, when it's homed pam module going into infinite loop once in a while unpredictably blocking all processes that use pam naively, unless you mean that they fucked up by using systemd or pam at all.
Edit: lol, I read through systemd release notes and there's no mention of new huge systemd-homed pam module at all. But good I looked, they're moving pam config for systemd to /usr/lib/pam.d and systemd-home pam module is again enabled there. So I'll have to check again all my systems if it's really disabled after upgrade.
I treat my home network as insecure and use an off the shelf ISP provided router (FritzBox). I have saved hours of my life doing this. I was running various unixy things over the years and suddenly something went snap and I decided not to bother.
It’s fine for corporate and medium sized networks but not worth it for home stuff any more. Just costs time, money and eats a lot of power.
one of the most advanced simulator-type games is built in a custom programming language/engine so shoddy that people struggle to maintain it, and yet every single attempt to replicate it in "better" languages/engines has so far failed. This game was originally built by 1 person.
>Wherever tools are used there are tools made of shit.
I find it's super easy to shit on tools. That doesn't mean another tool is better / will have a better outcome. Most of the tool talk is very focused on a few problems that I am not so sure actually point to the outcome of using it.
