larard

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 have a ruler. What number does the first centimeter start at?

The "e-bike" in that is clocked as hitting a max of 60km/hr during the test. That's not an e-bike to my mind.

Well, arseholes spelling wise, but wankers would be my chosen vernacular in this situation. Agree completely otherwise.

The quality of discourse was terrible.

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.

Just create the VM and clone it before you login for the first time, and use the clone. Never expires that way.

Looks like exactly what this article is talking about. I have no idea why noone else has commented on it....

How does stratifiedjs work under the hood? Does it switch out the stack?

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.

http://web.archiveorange.com/archive/v/6W82CWtdN8xPKbyel7HO#...

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.

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?

"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.

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.

I remember it clearly. It was the first evening of the Northeast Blackout of 2003 [http://en.wikipedia.org/wiki/Northeast_Blackout_of_2003] and I was working in NYC.

My wife had gone to her parents, and I wanted to phone her to say that all was well. All the cellphone towers were either without power, or overloaded. But the good old payphones just kept working.

It really is useful that telcos maintained their own power network. I wonder if this is still the case?