HN user

curtis3389

771 karma
Posts0
Comments187
View on HN
No posts found.

Here's the cosponsors of the bill:

https://www.congress.gov/bill/115th-congress/house-bill/1/co...

I think the purpose of the change was to "increase revenue":

Requiring that certain research or experimental expenditures be amortized over a five-year period or longer, starting in 2023, would increase revenues by $109 billion over the period from 2023 to 2027.

https://www.congress.gov/congressional-report/115th-congress...

The Rust for Linux politics mess should be laid squarely at Linus' feet. He's the BDFL. He approved adding Rust to Linux, and he massively failed at communicating what that even meant. If he wants Rust in the kernel, he needs to kick some maintainers in the ass and get everyone aligned.

“…You need to think of Larry Ellison the way you think of a lawnmower. You don’t anthropomorphize your lawnmower, the lawnmower just mows the lawn, you stick your hand in there and it’ll chop it off, the end. You don’t think ‘oh, the lawnmower hates me’ – lawnmower doesn’t give a shit about you, lawnmower can’t hate you. Don’t anthropomorphize the lawnmower. Don’t fall into that trap about Oracle.” – Bryan Cantrill

https://www.youtube.com/watch?v=-zRN7XLCRhc&t=2308s

Regardless of everything else, most people should not be using bcachefs yet. Kent has even stated that unless you're okay not being able to access your data for chunks of time while bugs are being fixed, you shouldn't be using it. The conventional wisdom would be to wait 10 years after a new filesystem is introduced for it to stabilize before switching, so we're looking at summer next year at the earliest.

I was thinking more of every web app needing one or more "if isIE() {} else {}" blocks somewhere in its codebase. Now we have the wondrous pleasure of doing the same for Apple.

Mobile Safari is the new IE. Random idiosyncrasies that are poorly documented dictated by the whims of a single corporation. Apple has broken stuff multiple times in the past few years.

IIRC, America's weird relationship with sex is rooted in our Puritan history.

Idk about our comfort with depictions of violence. We definitely have a history of "cowboy & indian" films, so it could come from the glorification of our genocidal past (or the genocidal past itself). The Vietnam War on the TV every night for a couple decades is another good option.

We're probably just talking past each other. The reason GNU comes off as religious is because they frame the whole issue in terms of human rights and moral imperatives (it is wrong to hide the source and we have the right to share). OSI prefers to frame it in terms of capabilities and transactional relationships (it's a win-win!).

The OSD is compatible with GNU licenses; I've read it before. That doesn't change the reality that by reframing the issue from rights to abilities, the OSI created the very environment where Winamp can be released as "open-source" while making forking illegal.

If you want a good look at OSI's commitment to the OSD, take a look at their Open Source AI initiative: https://opensource.org/deepdive https://opensource.org/deepdive/drafts/open-source-ai-defini...

They are directly complicit in propagating the lie of open-source AI. If you can't inspect how it was made, including the actual training the data, you don't have the ability to understand how the AI was made. The choice of the lumber is part of how a chair is made.

Without the "I have the right to know what my computer is doing", there is nothing backing point 2 of the OSD. Without "I have the right to share", there is nothing backing point 1.

sigh OSI was established specifically because they just wanted to share code and didn't care about GNU's 4 freedoms, so don't be surprised when the proponents of open source give you projects you can't even fork.