So my first reaction was like most people, wondering what caused the staccato marks spread. But then I started asking, hey, isn't this stolen data? Sure the security sucked, but what efforts did he take to correct the problem or bring it to the proper attention before he announced to the entire whole world how anyone could steal personal information on hundreds of thousands of students? With detailed instructions.

This is at best unethical. Hopefully it's illegal in his jurisdiction.

The results look to me like some sort of scaling. In fact, if you load up Gimp, take a photo and go into levels and compress the input levels, when you go back and look at the levels again the graph will look almost identical to what these marks graphs look like. It looks to me like the marks spread is being expanded and the algorithm isn't smooth.

First of all I will concede that yes, you are right that weight is properly measured in newtons. I used the common reference of weight most people think of. However it seems I need to explain a little bit about inertia. I'll try to use small words so even NASA engineers can understand:

Curiosity wheel encounters rock. Wheel exerts force to lift itself over rock. To do this, wheel must lift all of Curiosity. Curiosity masses 900kg. Object at rest tends to stay at rest. Curiosity tends to stay at rest. Curiosity wheel has much inertia to overcome to make Curiosity start moving up and then over rock.

NASA test robot masses 342kg. Test robot wheel encounters rock. Test robot exerts force to lift itself over rock. Test robot has much less inertia to overcome to make test robot start moving up and then over rock. Test robot has few dings. NASA engineers cheer.

From the article:

“We have the same wheels on our Scarecrow test rover, which weighs the same on Earth as Curiosity weighs on Mars,” Heverly added. “We have driven Scarecrow about 12 kilometers (7.5 miles) in the Marsyard over rocks and slopes much harsher than we expect for Curiosity. There are some dents and holes in these wheels, but the rover is still performing well.”

This sounds an idea from the same people that brought us the Mars Climate Orbiter crater.

The problem with this is that Curiosity weighs 342kg but masses 900kg. Scarecrow weighs and masses 342kg. Whatever Curiosity weighs, it hitting a rock at 1m/s is still 900 newtons of force. Scarecrow hitting a rock at 1m/s is 342 newtons. The fact it drove 12km and has serviceable wheels does not make me feel better.

I wish I knew what specific optimizations give MSVC its performance gains. What I do know is that it''s not trivial. For encryption and compression libraries, MSVC compiled libraries give me a 20% speed gain over GCC. I really want to supply my projects built with a completely open-source tool chain, but I can't justify taking that kind of performance hit for that.

I suspect MSVC produces better performing code less because of any one particular optimization and more because it is way more tightly coupled with the x86/AMD64 architecture. Most open-source compilers are three stage. Front end (language), a (generic) optimizer, and the back-end machine code emitter. The front end and optimizer stages don't know what sort of code will be emitted, so they can't make any assumptions. Does a particular construct cause cache misses? Does it invoke Intel's replay system? They don't know or care. It's only the emitter at the very last stage that is processor-aware, and by then there is only so much you can do. MSVC, on the other hand, is processor-aware from stem to stern. It can make CPU-specific assumptions at a very early stage and can take far greater advantage of SIMD instructions.

Compilers were much better when each one was for one architecture only. When they didn't mess around with intermediary bytecode, and were intended to one thing only - take language X and turn it into machine code Y.

I'm not so concerned about C++11, or compiling speed - which is what most people tout about LLLVM as its big feature. I'm concerned about the quality of the binaries produced. LLVM produces generally inferior code to GCC, which itself is already quite inferior to MSVC. I just wish there was an open source compiler where binary performance was a primary concern, not an afterthought.

Ya, but the thing is, I'd actually expect something like this from Linus. He really doesn't give much of a wet snap about software freedom - the GPL was a choice he made based on convenience (there's a pre-made license over there, and ooooh.... look how shiny and legal it looks). To make something like this actually funny, it should have been someone like Bruce Perens or Richard Stallman.

And as a follow-up, from the article...

Wow... Monty is not only taking MySQL back from the company who got it after he sold it, but after getting a billion for it he's now looking for other people to foot the bill.

The only thing Oracle is doing wrong is thinking that no one could be bold enough to try and sell the same product twice.

It's a gutsy move. It really is. Sell MySQL to Sun. Claim Sun's purchaser is doing __________ (fill in the blank with whatever evil nasty thing you like) with it. But that's ok, MariaDB will save you from that. Distributions flood to it to get away from the nasty big evil corporation, and suddenly Monty has legally taken back control of what he sold for a cool billion dollars.

The best part about it, is if Oracle says anything about it, then it just looks like they are trying to trash talk the little guy who is just trying to do the right thing for
the community.

And before you think of flaming the idea, remember, Monty is very much the businessman. He almost invented using the GPL as a weapon. He stopped releasing any connector or client licensed as LGPL so he could claim that even using MySQL as a back-end for something else required the entire front-end to be GPLed too - either that or pay him for a commercial license.

The next company to buy something from Monty better get an iron clad agreement never to fork it.

Indeed. For example, the close to thousand years of dominance the Roman legions enjoyed over every other force in the world happened because of the hugely famous Roman Polarmius.

It's simply an equalizer preset that boosts the bass and high end a little.

Funny thing. On the HTC One V phone, a little Beats Audio icon would show up in the status bar when you plugged in headphones. Originally, when you'd drag down your notifications and select Beats Audio, you'd get a dialog where you could select from about 10 different equalizer presets, only one of which was the "Beats Audio" setting. The rest were the typical equalizer presets. Rock, Pop, Bass Boost, Classical, etc. When the first update came out for the, that dialog was replaced with a simple "Enable/Disable" for Beats Audio. I guess they didn't want people realizing this much vaunted "Beats Audio" was just another equalizer preset.

Normally something like this would be the other way around, with the handset or laptop manufacturers licensing some Dolby sound labeling. In this case, the HTC update having deleted all the other equalizer preset settings leads me to suspect that this is a Beats marketing strategy. I'm guessing Beats is going to the handset manufacturers and paying them to advertise "Beats Audio" on their handsets in order to boost name recognition and give them street cred in the audio market. And when HTC dumped Beats Audio in with a bunch of other equalizer presets, I suspect Beats wasn't too happy about that, which caused the change.

I think it's safe to say that most people who have been in the scene from the beginning think the "correct" SI definition of kilo can also fuck off when it comes to computers. As can kebi, mebi and friends. It had been accepted from the beginning that "kilo" meant something just a little different when it came to describing bytes. I accepted that. Everyone accepted that. There was no problem. Even in academic circles, there were no issues.

The problem came with the storage industry and their pious "oh, but that's not what SI says the units mean". If you think that conforming to strict SI is the reason they made their change, then I'd suggest you not accept kool-aid from strangers. Ever. It was marketing greed, nothing more

However, while I think kebi, mebi and friends can fall down a deep dark hole, I actually don't mind using their unit symbols. At least in that way there is no misunderstanding in writing what is meant, and the trickle down effect from intellectual papers where it's vital that it's specified what value is means to more lay writings can occur without changing the unit symbols. But I do not now, nor will I ever, read 500MiB as "five hundred mebibytes".