> TVs need to continuously improve to keep selling, as do video game systems, etc.
I think that's true, and it's actually a very interesting topic. Just imagine the prospect that technology has effectively stalled out, and our civilization is stuck perpetuating the perception of forward progress.
Can anybody say what is going to happen? It's not a rhetorical question, and the implied or entailed context might involve a Nash equilibrium of some sort.
Right now the rate of signal is high, and the ratio of noise is proportionally high. But it seems like everyone expects the signal to eventually plateau or sharply decline. Almost as if there is a finite supply of "low hanging fruit" for shallow scanning machines to easily discover, and then there will be some kind of new world that follows where only truly difficult problems emerge.
But eventually the question then becomes why even bother with Rust or any other silly borrow checking ideas if we can use more enjoyable programming languages with LLM side-kicks to catch security vulnerabilities on the front side of the development workflow?
IT seems to me if we exhaust all the extant security vulnerabilities to a calculus that asymptotically goes to infinitesimal zeroness, then... the only trick remaining is to scan code before it becomes vulnerable.
> The FSF wouldn't participate in a lawsuit like this because ...
Because in reality the FSF is a WELFARE program for RMS.
Look, I'm done defending the FSF and the GPL. I worked professionally on open source software for over 20 years, but I'm just another former Red Had employee. But oh boy have I seen some stuff, and have seen how the open source sausage is made. I could probably write a wall of text about how the open source world is populated by a bunch of people with various kinds of pathological personality disorders. I certainly consider some of those crazy people my friends, but we have to recognize the nature of these folks.
RMS has to eat. That's why the FSF will never get involved with any big legal controversy. RMS cannot afford the legal expenditure from the modest stream of donations given to the FSF. But even if lawyers were willing to engage pro bono, they get disenfranchised by RMS and his specific quirky personality disorders.
But whatever. In my humble opinion... I highly doubt these European open source zealots will make much progress. On the one hand they say closed source interoperation with GPL code is a violation of the GPL, and on the other hand they say closed source code must interoperate with GPL code, or else... Something something European this-or-that... I think these are nice people, but clearly crazy. Then again it's not quite clear what these crazy people are chasing after? Maybe they merely want API documents, but probably they want to run GNU Hurd on Apple silicon
Proton is just emulation, and it will happily expose the underlying host system to the running game software. In particular the filesystem and some peripheral devices. However, Valve is moving towards sandboxing in Steam. You can already run the whole thing with a flatpak sandbox, and valve themselves are using ostree. With srvio is possible to run the whole thing in a throwaway windows vm while the graphics card is passed through
The funny thing is even data structure is really an array of memory depending how low down deep one looks. All the people who took an intro computer science course knows, those who had to implement a heap allocator, it's all really just arrays underneath...
Certainly. However, The developer seems to want to avoid the $2,500 per violation by any child who accesses the calculator, and might see a dick pic... because that calculator firmware does indeed allow for image viewing, and application development. It's more powerful than your PC back in the late 1990s.
I'm not sure what you mean by some of the things you write, but the part about Microsoft being "cool guy phase" was hilarious.
I'd say Microsoft buying GitHub was part of a strategy to not lose relevance in the world that moves slowly towards Open Source Software. Or put another way, the world moves in a direction away from Microsoft, and by capturing GitHub they can manipulate the outcomes that would otherwise have been adversarial to Microsoft interests. It's just like when Microsoft forked Java back in the 1990s, and later created .NET. The whole VSCode or Visual Studio thing... it's just Microsoft Word for software engineers, and the whole point is to create an ecosystem that locks people into the ecosystem.
To think in terms of what Microsoft does, you have to step back and look into economic theory, at least a little bit. There is this idea in economics about isolated economies, and integrated economies. For example, Europe or North America relies on cheap manufactured goods from China, and so China's economy is intrinsically linked (integrated) into the economies of Europe or North America. THAT is the idea of what Microsoft does. They start by adding value, a soft-dependency you might say, and then make moves to becoming a hard dependency... to put into terms of a dependency graph. Then they link to dependency graphs together GitHub into VSCode, OpenAI into VSCode, One Drive into GitHub or One Drive into Hotmail...
I'll say for sure, at least Microsoft has a strategy, unlike Google where they seem to have a lot of failed projects.
As ridiculous or absurd as this idea might seem, it's probably the most succinct and likely effective response to this kind of situation. The UK is betting the rest of the world doesn't reciprocate.
The SLS was a good idea, and it's actually a great rocket. However you are correct in saying it turned into a huge program for the old school rocket industrial complex. I think the private sector currently does this better, or it's certainly debatable. However, I think it's a mistake to say only the private sector can do this kind of thing optimally. There is some multiverse in the timelines where government contractors create an industrial rocket production line that quickly and cheaply stamps out heavy lift rockets. Granted, it's easier said than done, but it still doesn't have to be so expensive. Clearly the expensive part should be the R&D with the industrial production parts being jigged, automated, and fully optimized. The SLS obviously went another route by making the rocket production bespoke with non optimal, manual labor, etc... that kind of protection is acceptable for one-off science mission payloads, but not heavy lift....
Anyhoo, NASA letting so many people resign is good if your opinion is such that lowering government expenditure is a good thing. So long as the exit package is comparable to retirement package these government employees would have got otherwise. My guess is the resignation package has great near term performance but low long term (retirement) performance, making it a great option for younger workers able to pivot to new careers.
Hello world is really large, and it's unamusing how so much of the standard library is creamed into the resulting binary, no matter how trivial...
Do you know the current status of dynamic linking? I guess the lack of ABI stability is the big blocker, right? Probably no use in formalizing the linking bits if the goal posts keep moving. So it seems like the big problem is some committee will never complete the task... Because it will never be perfect... Something like that.
This might seems like a rant for some of you, of even heretical to certain shell zealots... But it's about time we move past Posix compliance for shells. Don't get me wrong, it was a fabulous thing back in the 1980s and 1990s with respect to the Unix wars. But in a twist of irony Linux won the Unix wars, and these days Posix compliance, with respect to shells, mostly holds back innovation or modernization by pegging the concept of a terminal to something from 1988. Namely the Korn Shell (which is reference POSIX SHELL implementation back then), or even worse the Bourne shell. Doing get me wrong, I'm glad we're not on something like the C shell, but I'm pretty sure nobody today actually adhears to pure Posix compliance for shells scripting. So let's all just agree to drop the pretence snobbery, and move forward in a brave new world beyond Posix.
I'm sure many of you remember the Monkey selfie from a few years ago... meh!
I'm also sure many of you understand the farther reaching implications of this ruling, especially how it relates to software code written by AI. All that code written by AI cannot be licensed as anything besides public domain. Just think of all the code people have checked into git, that they did not write! Next, please consider the implications towards the open source community if ever there is controversy about Linux kernel code that was AI generated, and then suddenly cannot be covered by the GPL. I think the neck-beard people over at NetBSD can sometimes be eccentric about many things, but this topic was deserved when they loudly banned all AI generated code from their repos.
It's like public photography, it's intrinsically legal, except when it's a Flock camera and then it's suddenly an invasion of privacy.