I first learned about em dash reading the GNU Texinfo manual in the 1990s. Now I have to wear a red, slightly long horizontal line on my shirt, and passersby shun me.
I've worked with RMS a good bit over the past few decades, and, in my interactions with him, he has always come across kind, helpful, and professional.
In the age of AI coding, the code itself doesn't matter, much less the code formatting. Just so long as the result functions correctly, we ostensibly never need to see the code again.
Perhaps this is in fact the ultimate code formatting tool -- completely obliterate the need for formatting at all!
I say retroactive not because the law changed, but because the law was never written with AI training in mind. I don't think existing copyright laws fit this situation, and I feel applying this interpretation to works already under copyright, when the creators of those works surely never envisioned this outcome, is an unfair interpretation.
Maybe pointless, but I for one disagree with such rulings. Existing copyright law was formed as a construct between human producers and human consumers. I doubt that any human producers prior to a few years ago had any clue that their work would be fed into proprietary AI systems in order to build machines that generate huge quantities of more such works, and I think it fair to consider that they might have taken a different path had they known this.
To retroactively grant propriety AI training rights on all copyrighted material on the basis that it's no different from humans learning is, I think, misguided.
Ah, I see where you're coming from. I've been hearing a lot of people talk poorly of aerospace as a whole recently, due to some Boeing issues, and I misread your comment as such. Apologies and thanks.
Not involved with this particular matter. What I would want to see is logs of the behavior of the failing subsystem and details of the failing environment. This may be able to to be reproduced in an environmental testing lab, a systems rig lab, or possibly even in a completely virtual avionics test environment. If stimulating the subsystem with the same environmental input results in the error as experienced on the plane, then a fix can be worked from there. And likewise, a rollback to a previous version could be tested against the same environment.
As an aerospace software engineer, I would guess that, if this actually was triggered by some abnormal solar activity, it was probably an edge case that nobody thought of or thought was relevant for the subsystem in question.
Testing is (should be!) extremely robust, but only tested to the required parameters. If this incident put the subsystem in some atmospheric conditions nobody expected and nobody tested for, that does not suggest that the entire QA chain was garbage. It was a missed case -- and one that I expect would be covered going forward.
Aviation systems are not tested to work indefinitely or infinitely -- that's impossible to test, impossible to prove or disprove. You wouldn't claim that some subsystems works (say, for a quick easy example) in all temperature ranges; you would definite a reasonable operational range, and then test to that range. What may have happened here is that something occurred outside of an expected range.
The earlier Peanuts animated specials had marvelous jazz soundtracks by Vince Guaraldi (and later others, after Vince's passing). Not sure if jazz trio is the most obvious music to accompany cartoons, but somehow this music blended exquisitely with the characters.
I think the point remains, if someone armed with Claude Code could whip out a feature complete clone of Microsoft Office over the weekend (and by all accounts, even a novice programmer could do this, because of the magnificent greatness of Claude), then why don't they just go ahead and do it? Maybe do a bunch of them: release one under GPL, one under MIT, one under BSD, and a few more sold as proprietary software. Wow, I mean, this should be trivial.
No doubt! But I was surprised specifically at high end audio production systems that are Windows-only, as that particular industry tends to lean pretty Mac in general.
I am reminded of Dijkstra's remark on Lisp, that it "has assisted a number of our most gifted fellow humans in thinking previously impossible thoughts."
(I imagine that this is not limited to Lisp, though some languages may yield more or less results.)
If we consider programming entirely as a means to and end, with the end being all that matters, we may lose out on insights obtained while doing the work. Whether if those insights are of practical value, or economic value, or of no value at all, is another question, but I feel there is more likely to be something gained by actually doing the programming, compared to actually lighting the street lamps.
(Of course, what you are programming matters too. Many were quick to turn to AI for "boilerplate"; I doubt many insights are found in such code.)
Without going to look up the exact quote, I remember an AI researcher years (decades) ago saying something to the effect of, Biologists look at living creatures and wonder how they can be alive; astronomers look at the cosmos and wonder what else is out there; those of us in artificial intelligence look at computer systems and wonder how they can be made to wonder such things.
Anecdotally, I've seen people do just that. Say, "I've tried it, it either didn't help me at all, or it didn't help me enough to be worth messing with."
But pretty consistently, such claims are met with accusations of not having tried it correctly, or not having tried it with the best/newest AI model, or not having tried it for long enough.
Thus, it seems that if you don't agree with maximum usage of AI, you must be wrong and/or stupid. I can understand that fostering feeling the need to criticize AI rather than just opt out.
Unfortunately, RTX did not respond to our vulnerability report. The account was disabled.
Some sort of acknowledgement of the report certainly would have been good here, but at least they did disable the account. I presume the reported vulnerability no longer exists.
Did the AI company tech workers get summoned into existence in 2023? Would they not have most likely been working somewhere else?
And what about jobs lost (or never created) due to AI itself?
Would not Google/Amazon/Meta have continued on to advance their product lines and make new products, even if not AI? Would not other new non-AI companies have been created?
I'm not convinced that the two options are, "everything as it is right now", or, "the entire economy is collapsed".
I decided to indulge in a Dunkin' pumpkin donut this morning, what with it being late October and the weather actually now fall-like. Apparently they have already discontinued them!
This is in line with my disagreement over the fair use rulings. Most people who published works that have been used to train AI systems, created those works and published them for other people to consume and benefit from, not for proprietary software systems to consume and benefit from. The existing licenses and laws did not account for this; nobody was anticipating it.
On top of which, the most popular systems are proprietary applications running on someone else's machines. After everything GNU showed us for 40 years, I'm surprised programmers are so quick to hand off so much of their process to non-free SaaSS.
I think that programming languages (well, at least some of them, maybe not all) have succeeded in being good ways of expressing programmatic thought. If I know what I want in (say) C, it can be faster for me to write C code than to write English that describes C code.
I was in the grocery store the other day, needed to use the restroom, and saw an AI-generated picture, framed, hanging on the wall in the restroom stall. It was even "signed" by "Meta AI".
I have gone there roughly once a week for years, but almost never get a donut. I feel their best menu item was the turkey sausage flatbread sandwich they discontinued like 10 years ago. Iced tea remains above average for fast food places.