That is the exact passage I found so shocking - if one finds the code in an open source repo, is it really acceptable to pass it through Claude code as some sort of license filter and make it proprietary?
On the other hand, next time OSX/windows/etc is leaked, one could feed it through this very same license filter. What is sauce for the goose is sauce for the gander.
I think, as it is a live BBC page, the title is changing over time? It is now "Planes grounded as mass worldwide IT outage spreads, with airlines, media and banks hit"
I’m really confused about the line of questioning here. Do you think it’s more likely that the submitter has purposely put a random number at the start, or that they’re telling the truth and there’s something that you’re not seeing?
It's a bit like all those people claiming that the new millennium shouldn't have been celebrated until 2001. They didn't stop to think how many years pass between the epoch and the time of interest. You celebrate a baby's first birthday after one year of time has passed. Until that point they are zero (and a bit) years old.
Why did the leave camp stick to the 350 million argument after it had been so firmly skewered. There were many other reasons to vote leave that could have been discussed instead.
It compiles down to JavaScript that you can then run on Node or the browser.
I once wrote a big long rant about the mess that JS and Node have made trying to cope with async code and got tons of comments proposing X or Y library that would "fix" the issue. Not a single person mentioned StratifiedJS. I wonder if there was some history to it that prevented it from getting momentum.[0]
1 - SJS effectively 'solves' the concurrency problem, but it is not a problem that is on the top of most people's mind when they write an application. To a first approximation, the concurrency problem in JS looks "solved" to people already (promises, generators, etc), and it is only when you get down to it and look at it in detail you see that SJS is actually a substantially more complete solution to the problem.
2 - Many people see it as a 'cute' solution that doesn't scale to big applications. To counter that point we've developed a complete SJS client/server framework - https://conductance.io - and are writing big complicated apps on it (such as http://magic-angle.com/ ). It's still rough around the edges, but we're pretty confident that the upcoming release (scheduled for end March) will show
just how powerful the SJS paradigm is. There is a presentation on it here: http://www.infoq.com/presentations/real-time-app-stratified-...
I used to love KDE, but they lost me and all the other users where I worked when they stopped supporting NFS home directories. Kmail was one of KDE's greatest assets, and now we are stuck with thunderbird on XFCE.
KDE claimed to be "Enterprise Ready" once ( http://www.kde.org/announcements/announce-2.2.php ), but silently went back on that when they forced the usage of the terrible akonadi and nepomuk with even the most basic components. I don't know of an enterprise setup that doesn't have NFS home directories by default, so I guess KDE is no longer ready for the enterprise?
Akonadi uses a MySQL db which is kept in your home directory to keep everything - mailbox index, your contacts, calendars etc. MySQL frequently has issues on NFS, and isn't supported to work with that.
Strangely I cannot find any official comment from the KDE or KDE-pim projects about what has happened here, even though the forced adoption of this immature technology has caused a lot if ire withing the community. As a single example I give you http://comments.gmane.org/gmane.comp.kde.devel.pim/33089 but there are thousands more that you will find if you ever try and google a solution to the various and sundry Akonadi/Strigi/Nepomuk issues that people are having.
The perl community have been searching for the best way to overcome the perception that "perl is dead". (The constant bickering that it isn't the case reminds me of the holy grail http://www.imdb.com/title/tt0071853/quotes?qt0470614 )
They need to focus on "Where perl has been" while it has been out of the limelight because, believe me, perl still rocks for productivity and performance.
Moose has revolutionized the object system (a system that was so flexible that it just gave you the parts and said "go build it")
Perl::Critic has created a baseline which all production scripts should be above.
PSGI and plack have changed the way you build and deploy and perl webapps.
In fact, the perl community and the current stars of CPAN have come so far, and have had so much going on that I have difficulty keeping up with the massive strides they are taking, let alone summarize those changes here.
"perl6 is another language in the same family as perl5. It is not meant to replace or succeed perl5. They are incompatible yet complementary."
The success of perl 5 is in no way determined by perl 6. Perl 5 development continues unabated. As jrockway says here, "Think of Perl 6 as Perl 5's Clojure".
Though my personal opinion is that the naming, and the confusion it creates, sucks and makes it really easy to think that perl (5) is dead because perl (6) hasn't been released yet.
On the other hand, next time OSX/windows/etc is leaked, one could feed it through this very same license filter. What is sauce for the goose is sauce for the gander.
reply