Because moving from one proprietary language/library ecosystem to another proprietary language/library ecosystem is somehow an improvement.

Fuck them both. We have truly open ecosystems like C++, and I would encourage any sensible developer going forward to move away from the likes of Java and the .NET ecosystems, now that the Supreme Court has essentially turned them into perpetual litigation machines.

But cleanroom implementations are meaningless if copyright can be asserted over the API. Clean room implementations only work because it has been generally understood that an API itself is essentially a directory listing, like a phone book, that in and of itself does not constitute some sort of creative work. Before the Oracle case, it was assumed that it was the code itself that constituted the intellectual property. But that is now apparently no longer true, and thus the Win32 API has gained the same level of protection as the source code.

If this stands, and is not corrected either by a lower court or by Congress, no one will every try a clean room implementation of any non-free library again, because there's a real likelihood that you would find yourself sued into oblivion for breach of copyright.

Wine may be safe because MS is being constrained by future potential anti-competitive suits, and of course Samba is protected because of a deal cut with the EU. But from this day foreward, clean room implementation of proprietary APIs, and I assume any other software spec (document format, communications protocol, etc.) will have absolutely no protection under the law.

Would you contribute to a future project like Samba or Wine now?

It certainly is looking that way, but there is the whole notion that what amount to call tables can be copyrighted. What the supreme Court has done here is basically unravel the common understanding of the difference between spec and implementation, and if Java is the most obviously vulnerable, in a very real way it means any number of APIs that have been re-implemented (like the standard *nix set of system calls) could suddenly be plunged into a purgatory-like nether world. I made vulgar jokes about using stdio.h in C programs, but that's the real question. Considering that in many cases header files and libraries whose origins go back decades in many different languages and on many different architectures could become low-hanging fruit, and since copyrights are in most industrialized countries are essentially perpetual now, big software houses now have a far better club to beat competitors with than patents.

Do you think another Samba or Wine project could happen if the lower courts rule for Oracle? Who would be crazy enough to even try?

Fucking hell, I guess I'm utterly fucked, because pretty much every C program I've ever written includes #include <stdio>. Here I thought I was invoking a free and open set of library functions passed on down since the 1970s, and now it turns out I've been stealing someone's hard work in creating a standard set of functional calls. I'm dirty fucking thief.

If specifications alone can be copyrighted, then the software industry is in for a world of hurt.

A function name and parameter spec is now "someone's shit"? Oracle's position is about as sensible as SCO's was.

All the early games I played were very "crunchy"; D&D, AD&D, Palladium, Twilight 2000 and Traveler 2300. The inelegance of such systems really began to drive me nuts, and I ended up going with Fudge and its variants like Fate. I never really played Gurps very much, but as I recall it was the middle ground between the kind of ultra-loose systems like Fudge and the very complex systems like AD&D. Now, I run a couple of PBeMs; a Palladium Rifts one and a home-brew heavily narrative game in the Harn universe, and dice are rarely used in the Palladium game, and not even part of the Harn game

It all depends on what you want to do with your matrices. Various operations have various costs in different sparse matrix formats. The standard ones are COO or coordinate format: a list of triples (i, j, val); DOK or dictionary of keys format: the hashmap you are thinking of; LIL or list of lists format: a list for each row and a list if pairs (j, val) in each list entry; CSR/CSC or compact sparse row/column: an array of indices where each row starts, an array of column indices and an array of values.

COO and DOK are great for changing sparsity structure; LIL is very useful if you have a lot of row-wise (or column-wise) operations, or need to manipulate rows regularly. CSR is great for matrix operations such as multiplication, addition etc. You use what suits your usecase, or change between formats (relatively cheap) as needed.

What would exiting the Euro actually accomplish? Greek banks have been fundamentally reliant on the Emergency Liquidity Assistance funding since February this year, when the ECB stopped accepting bonds guaranteed by the Greek government as collateral for loans, following the direction that the general financial markets have been taking for some months previous to that. So the Bank of Greece would still need to borrow money from somewhere, and exiting the Euro doesn't make borrowing suddenly easier....

How is a jump from $250 per unit to between $610 and $1250 (an increase of between 244% and 500% against the dollar) any more stable than either the Euro (~15% fall over the Dollar during the past year or so), the GBP (~10% rise over the dollar during the past year or so).

Something doesn't make sense.

Because the value of gold and silver is somehow less arbitrary than electronic bank balances.

So my collection of clown porn is still safely undetectable?

Does your book have dinosaurs and hot android sex? I don't just read anything, you know. I have my standards.

Or more aptly, those who apply and are the best fit for the job - there is no point in berating a company for woeful diversity hiring figures when all they did was concentrate on hiring the best candidate.

When it can be shown that Facebook turned down a better qualified minority candidate in order to hire a more poorly qualified white candidate, then there is an issue in hiring standards - if minority candidates are being failed by the education and social support systems to the point where we have a noticeable disparity in hireable candidates, well thats something we all need to fix properly rather than just tut at companies who would rather hire the better candidate regardless of race, colour or sex.