is there a material difference between taking profits and “getting very nervous”? the reason to “take profits” is that you’re “very nervous” that the price won’t keep going up; that’s the game right?

people have tried.

people predicted the enshittification of GitHub as soon as the acquisition was announced, as you can imagine. now, picture yourself as a dev in that month where a small vocal userbase is reading tea leaves based on Microsoft’s past behavior telling you to move your project, where the best outcome is nothing changes, to a new platform. you have a hundred issues and a dozen PRs in review, and those won’t stop coming in while you are migrating. now you need to mirror your project on GitHub, unless you want to immediately fade into obscurity, because while you’re spending your valuable time making sure everything is setup as it was but now on GitLab (the only realistic alt at the time), issues and PRs are still coming in, and you have to keep your releases updated in GitHub for a while during the migration. you also need to figure out CI/CD on your new platform.

so the ideal—that you can migrate and nothing changes—is a pipe dream. your packaging is now likely totally different; you’re now that snowflake project in the config where i had to figure out how to point to something other than GitHub and waste 30min questioning whether i need your tool at all. you still continue to get PRs and issues through GitHub because of course they didn’t read the README. and there’s tiny friction everywhere. the UI is different, how OAuth is handled is different, the plug and play you got from GitHub Actions is gone, etc etc.

meanwhile for 6 years things are chugging along fine at GitHub: Actions is getting better, Treesitter support, better UI for PRs.

it’s the AI stuff that’s ruining GitHub no doubt. not the AI itself but the culture around it with the “what is our team doing with AI?” nonsense corporate policy. it’s all happened really quickly, and isn’t the “boiled frog” scenario at all really.

Linux was around before GitHub, and wherever we end up as long as we still have our Unix tools like git it’ll be fine.

ideals are great. the perfect is the enemy of the good

“unhackable” is a bit sensationalized here. the Xbox One is actually a security success story not because it is impossible to hack, but because it’s a rare example of a console that wasn’t hacked in its service lifetime. at the risk of giving praise to Microsoft, the architecture is actually really neat and informed the security features of subsequent Windows releases, ie a hypervisor with sandboxed sub containers (this is why they required TPMs).

(also i’m not agreeing with requiring a TPM for general purpose machines; they make sense on a bespoke hardware platform like a game console)

i bet this hack is nuts, but the blue team deserves some level of kudos

https://youtu.be/U7VwtOrwceo

bruh i know people in their 40s making 6 figures that couldn’t read an error message if it would save ten generations of their family.

i don’t think people in this forum would disagree with this move in 2018, as much as sentiments have changed. if you remove the political context and market moves from the equation, it is truly fascinating how these models work. GPT 2 was a crazy leap forward for language modeling, and the idea that a language model would be threatening middle class jobs wasn’t even on the table at that point. the idea that a pile of floating point numbers could write a React app is incredible, if politically fraught.

also, it wasn’t clear back then what OpenAI would become. they were a non-profit, and as clear as our hindsight is today this was before ChatGPT or any customer facing products were coming out of OpenAI.

i can’t be the only nerd in the room that has been fascinated by AI since i was a child only to face a reality where it’s not what i imagined it would be.

two of our offices have 5 day return to office policies. we’ve been told that those coworkers will have less availability and productivity by management. they also are clearly stressed by taking calls in traffic and commuting generally. and not just gas, but vehicle repair, maintenance, and, as a coworker experienced recently, regular replacement means RTO is a pay decrease. i mean, i’m privileged to ride a bike, but i still need to do maintenance and would have to do more if i was in the office every day.

and when i say “two of our offices”, i mean across time zones, so their day as well as mine involves most meetings being over a video call, for which they are more often late or have to be accounted for.

anyone who thinks this is about productivity gains or employee wellbeing has the kind of job where they’re not really expected to produce anything.

this is one of those facts i have to struggle to keep to myself to avoid coming off as an insufferable nerd

oh wow gee thank you for not… [checks notes]… forcing open source developers to write state mandated spyware without compensation

the semantics of C make that virtually impossible. the compiler would have to make some semantics of the language invalid, invalidating patterns that are more than likely highly utilized in existing code, thus we have Rust, which built its semantics around those safety concepts from the beginning. there’s just no way for the compiler to know the lifetime of some variables without some semantic indication

Users who need to run their application in Python 2 should do so on a platform that offers support for it

damn go off

i know people usually are like, “oh cool new features”

but this has a security patch that will literally unblock my pipelines at work lol 🎉

honestly 8 space indents always felt a bit ridiculous to me. i usually use 4 since it’s more conventional in most languages but could also be happy with 2.

weird hill to die on. use default setting unless you have a good reason not to. the argument itself is a waste of time on projects that want to get things done.

i personally have pushed back on every “infinite scrolling” feature request from product designers. first, you think you need it; you don’t. second, you think it’s just so nifty! it isn’t. oh is your content is dynamically generated? what was wrong with Reddit’s pager that launched that site into popularity?

it’s unnecessary complexity that hides information from the user, makes API calls (which are, spoilers, paginated) more complicated, can cause the obvious memory/resource consumption issues, and just generally disempowers the user. which i guess on a social media app is the point. but totally counter to the goals of a fleet management system lol

what else would it be? it’s a pretty common embedded target. dev kits from Qualcomm come with Android and use the Android bootloader and debug protocols at the very least.

nobody is out here running a plain Linux kernel and maintaining a UI stack while AOSP exists. would be a foolish waste of time for companies like Rabbit to use anything else imo.

to say it’s “just an Android device” is both true and a mischaracterization. it’s likely got a lot in common with a smartphone, but they’ve made modifications and aren’t supporting app stores or sideloading. doesn’t mean you can’t do it, just don’t be surprised when it doesn’t work 1-1

most Zionists i’ve met are white Protestants, and most Jews i’ve met aren’t Zionists…

member when all the big cool web 2.0 companies had public facing APIs?

eh Bill doesn’t really pull any levers at MS these days, and Linus already got the moral victory of the Linux kernel running on Windows and basically powering their entire cloud business.

there’s a world of options. this is an LTS distro. use Arch or Nix or whatever if you want the latest packages. i actually switched to NixOS because the CUDA drivers were too new on Arch, and i wanted a better way to pin versions.

or i dunno keep publicly complaining about it until someone does the work for you

where i get into trouble is when i do a bunch of nixos-rebuild —switches between restarts and some state ends up hanging around, so next time i do a reboot that ephemeral state is gone and whoops no internet

i think it’s easy to make comments like this from the peanut gallery, with the benefit of hindsight and a self-selected group of users who will agree. but Apple should be legally obligated to address this. the solution can’t be “this idiot didn’t spend his nights and weekends doing 3-tier backups and high availability infrastructure diversity!”; that’s not scalable. if we just accept that companies can do this, they will continue to. but this has been on the front page of HackerNews. it’ll probably make it to Tim Apple’s desk eventually, so we’ll see what shakes out.