Seems WebKit will have a place after Chrome and Opera's split to Blink. (This new Pi browser is Webkit)

"The more items Amazon sells to Prime members, the more money it loses." What bookshops have been saying for a decade is that Amazon is selling books at a loss, which used to be illegal as anti-competitive monopoly activity.

Much better than the opaque NYT article linked is this December article from IBT: "Amazon: Nearly 20 Years In Business And It Still Doesn't Make Money, But Investors Don't Seem To Care" http://www.ibtimes.com/amazon-... It has the quote above, and the historic profit/loss graph I was looking for. Revenues have risen at a 45 degree angle, but profit/loss hovers around zero.

Now all Netflix needs to do is get a FiOS account at their house.

No results found for "will brooker" +scam.

Click "Full Scorecard." It's an interesting mix of D's and R's.

Read the article, they are targeting Firefox, Chrome and Safari as platforms. This is a development tool for some reason put into core.

And the "app" does have to be a web app because this is all about mobile. They will probably integrate submitting the app to the various vendor-approved marketplaces, starting with this one: https://marketplace.firefox.co...

I question all this, because Mozilla has limited resources, mainly from Google searches. But sticking with Desktop only would be risky.

That's long gone. The download (29MB for win32) is now larger than Seamonkey (20MB). At least half the development is focused on mobile and other projects. Thunderbird and Seamonkey have no paid developers. I assume the mobile products do have to be lean and fast though. That's been the big turnaround in browsers, back to small screens, low memory and slow chips!

As for desktop. Still a good browser, needs one process per tab. Still good to have a compliant rendering engine besides Chrome. Still good to have privacy and security policies competing with Chrome.

Not that.

Right now this protocol is useful for Firefox Desktop, Firefox Android, and Firefox OS. But we aren’t stopping there. We’re working on a protocol adapter that will allow clients using the Firefox Remote Debugging Protocol – including the Developer Tools and WebIDE – talk to all mobile browsers, regardless of rendering engine or runtime. Our first targets are Chrome for Android and Safari on iOS.

TB has some architectural problems and the withdrawal of paid developers by Mozilla makes it unlikely they will be fixed. The problem I ran into is that attachments cannot easily be stored separately from messages. That column showing the attachment count is actually just a guess. The db does not have real info on the MIME situation in messages. All that work is done on the fly whenever you open the message. You can detach the attachments from messages and store them separately, but only by clicking on messages one-by-one. There is an extension that attempts to automate detachment through filters, but it will crash if it encounters too many messages with attachments at one time, since the task is asynch. I confirmed all this with the extension developer - not the crashes, but the architecture and the fact that the db only guesses at the attachment count when you view the message list. Of the 12,000 current extensions, I found two or three that attempted to deal with detachment.

BoringSSL is a great name and directly addresses what got OpenSSL into trouble most recently, implementing a new protocol parameter based on a student's idea for a degree thesis. Innovation for innovation's sake, that was. Hurriedly applied for some reason.

And it's not something a website would "use," if you mean a high level protocol akin to "https." It's a library to implement common standards.

Maybe by assigning people to the project who have not chosen security as a career field. On the Mozilla commits I used to follow, the personalities in the security arena were a different kettle of fish from the other developers. They had to maintain FIPS compliance, so were conservative about changes, but it was more than that. Not to mention, there's a possibility of workers with ulterior motives. All the more reason to develop a wider community than just self-selected specialists.

The billion dollar companies can afford it, and should have a long time ago.

They made a whole movie about this one, on the Alabama border. But the franchise was for... sin! The Phenix City Story

Classic Theme Restorer. Cheap, easy, no config.

Cinnamon or Mate?

The big companies probably want more control over the project than LibreSSL will allow them. They've been burned once by relying on old-style Unix community dev. But it's also entirely their own fault for not funding and auditing the open source code they were building their billions on.

Seems to me LibreSSL is the way to go, but I can also see why the corporations would just use it as a side-stream for hints on what to fix. They have enough resources to rewrite openSSL from the inside rather than the the LibreSSL tear-down approach. Having both projects is really a benefit for LibreSSL as longs as it gets sufficient interest and resources.