Make a legitimate edit on a controversial article that fails to indulge the bias of an admin and you'll learn all about the ways admins have to ostracize non-admin contributors. Are you aware of this and if so, what has been done recently or what is planned to moderate abuse by admins? How frequently are admin privileges revoked for abuse? I hope this is frequent because I know for fact the abuse is frequent.

Didn't claim you would be able to. I just pointed out that it isn't Microsoft only. The point of the original post was that the HTML5 extensions were "locked into windows," which they are clearly not. It may be locked into all kinds of other crap, but it's not Windows only.

And stop foaming at the mouth.

No claim made to the contrary. It's still lock in, as I said. It's just not specific to Microsoft.

Reading comprehension. Try it sometime.

There may be lock in, but it's not exclusive to Microsoft:

Media Source Extensions (MSE) This specification extends HTMLMediaElement to allow JavaScript to generate media streams for playback. Allowing JavaScript to generate streams facilitates a variety of use cases like adaptive streaming and time shifting live streams.

Encrypted Media Extensions (EME) This proposal extends HTMLMediaElement providing APIs to control playback of protected content.

Web Cryptography API (WebCrypto) This specification describes a JavaScript API for performing basic cryptographic operations in web applications, such as hashing, signature generation and verification, and encryption and decryption.

They're all W3C standards track specifications. The first two have editors from the same three corporations; Google, Microsoft and Netflix. Google, in particular, can't tolerate not being capable of playing Netflix (10% of the population of the US subscribes to this) on its platforms (Android and Chrome OS.) It already works on both and you can take it for granted that Google expects to achieve parity with these specifications.

The last specification is not specific to streaming; it's a general purpose Javascript API to perform common cryptographic operations.

From the SiSoftware link you provided:

Thus, HLE at least can be adopted immediately by operating systems, compilers and runtimes. That actually started over a year ago for GCC. Intel's compiler uses TSX as well. RTM requires a feature test for compatible use, but it can still be utilized, particularly in runtimes (JVM, CLR, v8, etc.)

So seven years is too pessimistic. Haswell users with recent compilers are already using TSX.

Great benchmark link, BTW.

That is going to be an important feature when programmers eventually leverage it. Hardware assisted optimistic locking can make concurrency easier, safer and more efficient as the CPU takes care of coherency problems usually left to the programmer and CAS instructions. Imagine being able to give each of thousands or millions of actors in a simulation their own independent execution context (instruction pointer, stack, etc.,) all safely sharing state and interacting with each other using simple, bug free logic, as opposed to explicit and error prone locking and synchronization. This has been done with software transactional memory but it frequently fails to scale due to lock contention. Hardware based TM can prevent that contention by avoiding lock writes.

It is extremely cool that Intel is implementing this on x86.

That Bloomberg story is about the reactor pressure vessel or RPV, the part the contains the reactor core. These authors write poorly and got it wrong calling it the "containment vessel."

This Slashdot story is about the AP-1000 containment vessel, not the RPV. The vessel is 36 meters wide and 65 meters tall. Nothing on Earth can make a single piece of forged steel that large.

The RPVs specified for the AP-1000 are unusual. RPVs are traditionally welded.

RPVs for other common reactor designs such as CANDU or VVER are welded assemblies. Often forged steel steel rings are stacked and welded. Some RPVs use large forged plates and are axially welded.

Note that although the bottom of the AP-1000 RPV is a single piece it still has a separate head; the top of the RPV is gasketed and bolted to the vessel like every other PWR or BWR. It has to be to (re)fuel the reactor.

I do. I have been looking forward to Mint 15 for a while and so have a lot of others. I appreciate that it was posted on Slashdot and I hope others consider trying Mint as a result. Mint deserves the attention because Mint is an antidote to terrible Linux desktop environments.

The magic ju ju is the ARM business model. There is one trump card ARM holds that precludes Intel from many portable devices; chip makers can build custom SOCs in-house with whatever special circuits they want on the same die. Intel doesn't do that and they don't want to do it; it would mean licencing masks to other manufactures like ARM does. For example, the Apple A5, manufactured by Samsung, includes third party circuits like the Audience EarSmart noise-cancellation processor, among others. It is presently not feasible to imagine Intel handing over masks such that Apple could then contract with some foundry to manufacture custom x86 SOCs. This obviates Intel from many portable use cases.

That feature of the ARM business model might be very useful to large scale computing. One can imagine integrating a custom high-performance crossbar with an ARM core. Cores on separate dies could then communicate with the lowest possible latency. Using a general purpose ARM core to marshal data to and from high-performance SIMD circuits on the same die is another obvious possibility. A custom cryptography circuit might be hosted the same way.

Contemporary supercomputers are great aggregations of near-commodity components. However, supercomputing has a long history of custom circuit design and if the need arises for a highly specialized circuit then a designer may decide that integrating with ARM to do the less exotic leg work computing that is always necessary is a good choice.

People like Zuckerburg use to found colleges and universities in the US. Now they squabble with Congress for cheap imports.

Can't be. Those are the jobs we're keeping here in the US because we all have $75k degrees. The low skill jerbs go to Asia and we keep all the high paying jobs because the Chinese are magically incapable of EE.

Right?

Remember: Education. It's the future.

Shutting down White House tours is the same brand of statist petulance.

BTW, ordinarily around here the Blue Angles and their ilk are just jingoistic manifestations of the US Military Industrial Complex's hegemony over the victims of global capitalism, and stuff. We're supposed to believe you people suddenly give a damn about these airshow cowboys?

LOL

There are a lot of malcontents around here. Not all of us, however.

There is plenty of room for a good systems programming language. No, we probably don't need another managed, exclusively garbage collected, JIT compiled, VM hosted, 'dynamic' application language. And we've certainly collected enough Javascript front-end languages recently. That's not the intent of Rust.

Prosperity. Economic growth. Energy is the ultimate raw material necessary for these things.

Don't assume everyone shares the premise that we need cheap, abundant and clean energy. You could live out your life inside a three mile radius of your yurt nursing a solar panel. Putting you there is an ideal to which many aspire.

To be clear, I am not among them. I've just shed any illusions about whom I'm dealing with. They've either got theirs or they don't want it (the former being the vastly larger group) and job #1 is stopping you.

Investigating, arresting and prosecuting people for violating these kinds of laws is unbelievably difficult and expensive and rarely nets more than wrist-slaps. Cases take years, litigators cost millions and there is and endless supply of replacement spammers to replace the prosecuted. Governments executives and their staffs know this and have better things to do.

Finding the least statist solution is my preferred remedy in any case; make the practice economically infeasible by creating a generic regulatory mechanism (white/black lists based on working caller ID and enforced by the network operator, perhaps) and leave the cops/prosecutors/courts/prisons out of it.

The carriers are a part of this as well. They facilitate spammers by deliberately not making caller ID work end-to-end in all cases like it should, streamlining mass account provisioning, etc. They get revenue from calls, spam or otherwise. Even your legislators are part of it; they exempt themselves from robocall laws and email spam laws creating all sorts of loop holes and special exceptions in the system that carriers can and do use to deflect blame.