In the 2000's (before Oracle), I negotiated a license with MySQL that allowed our company to bundle the software in my commercial app (for ease-of-install, especially demo time) even though someone could have downloaded and installed their own copy of MySQL for free. The OEM license cost something like $150-250/license (kept going up, of course).

The obligitory "Dihydrogen Oxide" reference:
http://www.dhmo.org/research.h... ...applies here.

I don't understand the belly-aching. When I wrote code for Apple II machines, I had to know both BASIC and assembler. PC? Batch scripting, VB, C++, C#, SQL, InstallShield and still a little assembler. Web and mobile? Javascript, Java, Perl, PHP, Ruby, C#, ASP, Objective-C plus a few dozen "platforms", "frameworks" and what-not cobbled together with JSON, XML, CSS and various template and scripting syntaxes.

So, you have to learn three platforms to keep up with a line of devices? Boo hoo. Besides, an "app" should be something you can crap out in a month or two - these generally aren't monolithic platforms like Office - even the context-switching-disabled should be OK.

>> are we seriously blaming google and not NSA who found the bug 4 years ago when the bug was first introduced?

Yes. The NSA is the US gov's lead black hat. Google's an advertising company that depends on people trusting the Internet for information and commerce. I'd expect the NSA to hoard information to assist their black-hatting, and I'd expect Google to quickly share anything they know so security vulnerabilities can be patched and people don't lose faith in the Internet*.

* = (Seriously, when people have asked me what to do about Heartbleed, I've said "don't buy anything you don't need, and try to avoid paying any bills online or doing any online checking for a week or two - then change your password as soon as you sign on.")

>> Google notified OpenSSL about the bug on April 1 in the US – at least 11 days after discovering it.

"OK, maybe it was caught up in legal. Suits at large corporations can take a while."

>> Google would not reveal the exact date it found the bug, but logs show it created a patch on March 21,

"On second thought, if the geeks on the ground had the authority to patch and roll to production, then why the finger to the Open Source community, Google?"

>> The Register has the story as well

Duh - the Register is where most of us read the story so we'll know what to write when the same news appears on SlashDot tomorrow.

>> Advocates of sit-stand desks

Sorry, I read that as "vendors of sit-stand desks"

Seriously, does anyone still work at a tech job crappy enough where they care if you sit, stand or bounce around on a pregnancy ball all day?

can we all pitch in $5 a month and get this bennett guy his own blog? (and punt him the hell off slashdot?)

>> What none of the attendees of the conference knew was that Google was pulling many of the strings behind the event

I doubt/hope that "no one knew." Conference agendas, like news stories, should always be read for brand-name frequency. (The brand name that appears most frequently or in the most positive manner is usually the one that hired the PR agency to plant the story in the first place. Same thing goes for a conference agenda.) What's the number one name on this conference agenda? Google.

So...if the academics attending the conference didn't guess it was Google sponsored...then they're probably not as bright as their titles suggest.

A "responsive image" will load either a small or large version (or multiple versions) depending on the browsers's screen resolution. To do this, it makes an extra request to the server before requesting the appropriate image size.

(The referenced Opera article prattles on and on - Google's faster.)

C'mon, with BUILD just behind us, how did this wall of text make it up here? (It's NOT a slow news day.)

Having lived through the entire lifecycle of "open source," it seems like its place in development communities and businesses is well-established, with a mix of different licensing and deployment models for whatever anyone wants to do.

So...is there really anything interesting left in "open source" to talk about? (Software patents, maybe, but even that's picked up some case law.)

>> Sane people will stay with salting and stretching, ideally with scrypt() to neutralize GPUs.

"Key stretching is orthogonal to PolyPassHash and could be trivially used in conjunction."

Hell, just the bit about bcrypt, etc. using a unique hash per password would have stopped most of these "grab the file then crack the table" hacks; the current focus of developers should probably just be to replace anything still using unsalted (or common salt) MD5/SHA1/SHA256 schemes.

>> some readers may note that with this story we are slowly rolling out one we hope you enjoy -- an audio version of each Slashdot story.

Er...no thanks. There's a reason video tanked on this site too - your readership is too damn busy to wait for the talky-talk. So, we skim (and type) like crazy, and value text-heavy sites like Slashdot and Reddit. (OK, 15 seconds - time up - back to work!)

Early use by a major company of Javascript consuming XML-based web services. Successfully leveraged Google's search engine. Design conflicted with the all-on-one-page "portal" paradigm of the time. Text ads instead of banner ads, and controversial because they were tied to the content of the messages. Original cluster was 300 servers.