> My hunch is there are not many globally who want to suffocate while trying to exist for shareholder value.
I hate this kind of hyperbole because it obscures the real dangers. No one is going to suffocate any time soon. Atmospheric CO2 is around 450ppm. The CO2 in a meeting room of a typical office can easily reach 1500ppm or more[1]. Is everyone in meeting rooms "suffocating"?
Setting aside the legal questions, what a nasty thing to do. I would expect to see this kind of move from some big corpo, not an OSS maintainer. This feels like it runs counter to the whole open source ethos and undermines the idea that authorship means anything anymore.
How do you do phase 2 with an LLM when the LLM is likely trained on the original source code? Isn't this equivalent of "rewriting" Harry Potter by describing the plot to an LLM trained on the original books[1]?
Writing in a plan "no GPL/LGPL code" does not actually mean "forget all the GPL/LGPL code that you have ever seen, so that you start from a clean slate".
Agreed, no amount of system/user prompt directives change the fact that the LLM has already been trained on copyrighted code. It's amazing how many people fail to grasp that.
This is the "Don't think of a pink elephant" fallacy all over again.
Legislating that everyone must always be safe regardless of what app they use is a one-way ticket to walled gardens for everything. This kind of safety is the rationale behind things like secure boot, Apple's App Store, and remote attestation.
Also consider what this means for open source. No hobbyist can ship an IM app if they don't go all the way and E2E encrypt (and security audit) the damn thing. The barriers of entry this creates are huge and very beneficial for the already powerful since they can afford to deal with this stuff from day one.
Doesn't have to be a law. Can just be standard engineering practice.
Websockets for example are always encrypted (not e2e). That means anyone who implements a chess game over websockets gets encryption at no extra effort.
We just need e2e to be just as easy. For example maybe imagine a new type of unicode which is encrypted. Your application just deals with 'unicode' strings and the OS handles encryption and decryption for you, including if you send those strings over the network to others.
Scrum is management consulting companies trying to keep their job by turning something that would make them irrelevant (the agile manifesto) into something that requires tons of billable hours and useless qualifications like "scrum master". Seems to be working great for them.
The agile manifesto is about how to run a consulting company. "Customer collaboration over contract negotiation" is not something non-contracting software teams have to worry about, customer collaboration is important but there's no contract negotiation to prioritize it over.
I've worked at three very different companies where at least one member of the software team had to essentially negotiate for their project's budget and scope (and tacitly their jobs in some cases).
This whole debate is cyclical[1]. I expect in a few years everyone will be complaining about not enough daylight in the mornings and DST seasonal changes will come back.
> Permanent daylight saving time was signed into law by President Richard Nixon in January 1974, but there were complaints of children going to school in the dark and working people commuting and starting their work day in pitch darkness during the winter. By October 1974, President Gerald Ford signed a law repealing year-round daylight savings time.
It's a perfect example of "the public" not really knowing what they want or perhaps different factions (unknowingly) wanting different things and not realizing this until the change actually happens. This isn't helped by how these ideas are often oversold as having no downsides instead of being realistic about what the trade-off is.
I know that I want an end to clock changes more than I want the time zone to be optimized. Both spring and fall clock changes cause a spike in car crashes and serious health events, which I suspect of being worse than the problem they're trying to solve.
I don't think there's a way to do this without casting something to connect the pre-fab to the surrounding concrete sidewalk. Like how do you precisely cut out the existing curb so the prefab just fits (including elevation/slope) without excessive gaps or something? And if you're pouring concrete anyway, might as well pour the curb itself.
With prefabs you first dig up both road and sidewalk, set up pre-cut granite curbs (kerbs?) on a mild concrete foundation (negates sinking completely), then repour and repave sidewalk and road. Lasts many years in -20C winters +35C summers climate.
1Password used to be great for personal use and you could sync your vault with Dropbox or Synchings or whatever. I'm sad they stopped selling "forever" licenses and supporting local sync and went the SaaS route.
I hate this kind of hyperbole because it obscures the real dangers. No one is going to suffocate any time soon. Atmospheric CO2 is around 450ppm. The CO2 in a meeting room of a typical office can easily reach 1500ppm or more[1]. Is everyone in meeting rooms "suffocating"?
[1] https://www.popsci.com/conference-carbon-dioxide-tired-offic...
reply