And of course many people self-host which changes a lot of the equation (which you can also do with GitHub, but not for free - and FWIW our self-hosted premium gitlab has about an hour a day downtime, which we've been told by the team responsible is an unavoidable side-effect of backing up gitlab).
I was responsible for administering a self hosted GitLab instance for a medium sized company and our backups never required downtime. The built in backup command doesn't require downtime but also isn't a consistent point in time snapshot (specifically because the instance keeps running while the backup is being taken). If they've decided they need one for some reason, stopping GitLab is certainly the easiest way, but not the only way of accomplishing that goal, but that'll be true of any self-hosted forge, including GitHub.
“Nothing in my training data covers this, but if I had to guess, OpenAI may have released information about GPU support in Mac OS X early, pissing off Steve Jobs.”
Open weights are indeed a commercial risk because there's no shortage of companies that'll make a business out of running MaaS (model as a service), close & resell a fine-tuned or distilled variant (DeepSeeking of Llama / Cursorification of Kimi, for example).
I didn't have a single Apple device in my house until a month ago when I bought a Neo. The last Apple devices I had before that were an iPod Nano and a PowerMac G5 many many years ago.
Apple has pretty good competition in every segment with the exception of maybe the iPad, but I'm not a tablet user.
Some folks like to have a computing environment free of proprietary influences and extremely strong vendor lock-in. I cannot claim to posses any apple devices.
I wasn't thinking of Asahi. Just pointing out that you can run all the standard unix/open source tools and apps on Mac OS (vi, git, qgis, blender, vsc, python, node, etc). With the advantage of higher quality hardware and generally less fiddling.
But if you don't like it, switch. I don't see vendor lock-in.
there a many people who don't own Apple. Why are you so surprised? I certainly don't and never will. What's it got that I can't get on a standard PC + Linux?
Can never predict your future. Enjoy what you will, when you can. I was in a motorcycle accident in 2021, TBI, hospitalized for 3mo, induced coma, and rehab for 9 months after.
I am back on the horse. It is just a zen and still relaxing time, albeit more anxiety while riding, than before. Thankful I can still ride, and I do.
I'm sorry, but from a European perspective, this is the problem, not bikes. If your roads and driving culture encourage driving a tank for safety, that's a bit less than ideal.
I commuted to work for 5 years on a moped. I never used a highway, almost never exceeded 50km/h, and had 2 accidents during that time; both resulted in just a few scratches and bruises.
In another post, you said: "maybe speed was a factor" - actually, it's the only factor. If you never go too fast and never use roads where others may go too fast, you're safe - at least from life-altering tragedies.
If, on the other hand, it's generally impossible to get where you want to without using highways, or the sheer distance forces you to step on it - then yeah, don't buy a motorbike. Just note that it's not the bike's fault!
I lack the commenting impulse control to say this in a politically correct way so my apologies for the outrage that will follow, but to put it crudely there is someone in my extended family who became a retard after falling off their bicycle at roughly walking speed and with a helmet on. It's rare but you can easily die just from walking and slipping on a banana peel.
While you're right about slower generally being safer, you should still treat it like a life-altering tragedy could happen at any time and like you're going 200 kph.
I'm sorry for your relative, and of course you should always do things like driving (diving, cycling, sailing, climbing - or even cooking and cleaning) as if a tiny mistake could cost you everything: that's because it's actually true. These activities will never be risk-free; the best you can do is bring the risk down to a level comparable to that of alternatives (with "just don't do it" included in the set) and hope no unfortunate incidents occur to you.
It's still worth noting the relative probability: death or life-changing injury is basically what happens in every single accident when you're going 200km/h on a highway surrounded by (what could as well be) steel walls moving at the same speed; in my use case, when not exceeding 40-50 km/h and using roads where other users basically stand still most of the time, you need a pretty specific conditions and a lot of bad luck to even have an accident, much less die or become permanently disabled as a result of one. Still, not a zero probability, but the difference between 100% and 0.01% is kind of noticeable.
as someone on the other side who has had to deal with deploys that go from 5PM to 2AM due to bad code changes, and being on call with 40+ pages a day, there's a reason why SREs are just say no when they're the first responders to outages caused by poorly implemented features. I'm not saying just say no is the right mentality but I can see why many develop the cynical anti-change mentality
reply