Responsibility, ownership and craft. The folks who are rushing to abandon these things are reckless and wrong, and we’ll all pay the price. Such a shame. We could be positively SOARING as an industry right now and instead we’re relegating the adults in the room to shoveling out the Stygian stables. Bah, I hate being negative Ned but it’s the truth!
I really believed a whole generation of developers, who only know open source from npm and pypi, miss how open source actually used to work.
When Debian or a Linux distribution ships a dependency they take responsibility of it. If there is a security issue and it’s not fixed by the developer upstream, they fix it for their users.
Debian and others basically vendor every thing they distribute. They honor the license and they maintain patches. Most of the stuff that you get from your Linux distribution is basically a (small) fork.
The same is true for Apple, Microsoft and others. The open source software they ship, they carry that responsibility.
That doesn’t mean that security fixes are not upstreamed, but Apple or Debian or anyone else won’t jump in Twitter to shame a developer into compliance with their ways. They are not dependent on the health of a packaging infrastructure. They own their software including all the things it depends on.
I want that thinking back. Because it fundamentally makes people feel more responsibility and it shares the burden of issues. It also does not put so much focus and attention on the one overworked developer who just happened to have too much of the world depend on their library. Remember: they carry a responsibility they never signed up to and they never got compensated for.
each issue of process pamphlets is a project from start to finish
https://t.co/OdtEjB6WOg
love this idea ! reminds me of a talk I give where I walk students through a project from the initial email to finish
I'll admit I joined the pig pile when I first saw the bug report. This is an object lesson. The internet is an outrage amplification machine. Don't give in to the temptation.
@kumxem 45 seconds ago.
X refers to the One True Windowing Protocol of the Elder Gods, X11.
Childe Elon knows this because he made the logo a picture perfect clone of the X11 logo :)
https://t.co/Eg5kjo6Dh5
@badlogicgames Have you considered making the claude-sdk-bridge extension the default Claude provider since logging into the *actual* Claude provider locks you out of using all other models?
Anthropic is acting like the 900lb gorilla they are :(
Rule changes for the SpaceX $SPCX IPO:
Index providers waived the profitability requirement and cut the seasoning window from 90 days to 5.
This forces over $30 trillion in passive 401k and retirement money to buy SpaceX at IPO valuations.
Bloomberg Intelligence estimates S&P 500 funds must absorb 19% of SpaceX's float within 6 months.
Russell 1000 and Nasdaq 100 funds will absorb 24%.
The rules built to protect passive investors:
1. S&P 500 has required 12 months of trading and 4 quarters of GAAP profitability since 2002. Both waived.
2. Nasdaq cut its inclusion window from 90 trading days to 15.
3. FTSE Russell cut its to 5.
All three benchmarks are now structured to buy SpaceX at IPO pricing.
@fleshsimulator It's *your* bat and ball and I celebrate your right to do whatever you want with it but you guys are losing me with this most recent podcast episode.
If you *weren't* looking to shame women for seeking reproductive health care, it certainly sounded like you were, and it's kinda shattering the "Talks like a REALLY erudite mega-troll but actually pretty liberal" impression I have of you.
Still love the videos. Great stuff! Looking forward to the new documentary!
(I agree that no cow is too sacred to avoid tipping when it needs to happen, but I'm not convinced reproductive health care is that cow.)
@aap_twak@badlogicgames Thanks for that. I'm a huge proponent of using AI tools mindfully in service to quality engineering. And if that's what's happening, ESPECIALLY using AI to add more unit tests to a legacy code base like rsync, then this story is rather mis-reporting the facts on the ground.
"Java setup has come such a long way!"
1. Install some packages
2. vim.pack.add{ 'https://t.co/kavF8pbg1K' }
3. Update jdtls config to use java-debug
4. vim.lsp.enable('jdtls')
https://t.co/QR8yj1dGXn
Hate to admit this because I want to support tech journalism, but I paid $60 for a year of @verge and every single time I've read it it's been a waste of my time. Not that the content is BAD. It's not. It's just - way too focused towards other folks that aren't me :)
I suspect I'm too much of a tech nerd for this particular publication :)