mattbasta

They tried making it scarier. They even tried adding a timer so you couldn't just blindly click the install button.

For the same reason Facebook puts a big loud warning in the developer console. People will follow any instructions they're given. "Press ctrl+shift+I and paste this in the box and you'll get a free puppy" "Put this in your address bar and your crush will be revealed" "Go to about:config and double click this thing, and then click this link and we'll show you nearby singles that want to hook up"

Firefox add-ons essentially have full, unrestricted access to your computer. Locking this down good and well is pretty important.

> Mozilla was in the best position to pursue FFOS in the purest possible manner

Well, maybe philosophically, but they didn't have enough influence, money, or manpower to actually make it successful. The first version of FXOS shipped without a calculator app because they couldn't work all of the bugs out. Clipboard support didn't make it until sometime around v2 or 2.5. Apps never got API support for things like front-facing cameras or bluetooth, or even access to which wifi networks were available. One constant complaint was that the Alarm app would sometimes go off at the wrong time, and sometimes not at all.

There's also other components to FXOS that simply weren't free software. The everything.me integration (which was a for-profit service baked in) was truly abhorrent. Hardware vendors refused to provide open drivers in many cases, leading to chunks of FXOS not being open source. Operators and carriers insisted on installing their own crapware on devices and forced the OS to lock them down so they couldn't be uninstalled. At the end of the day, FXOS as it was sold wasn't nearly as free as it was made out to be.

I don't want to pick on Mozilla, but despite having a great vision for FXOS they ultimately were vastly underprepared to build a solid mobile operating system. Even worse, Gary Kovacs bet the farm on FXOS and let Firefox proper rot in a corner.

You really make a tradeoff with FOSS. You can have software that's free in the most pure way possible, but it's ultimately going to be terrible unless the company putting it out is fiscally incentivized to make it great. If Acadine keeps FXOS as open as it is today, that's still a great win for the community and probably most of the users.

Do GG accusations actually matter anymore? Does anyone still care besides the people actually making the accusations?

This was my immediate reaction. A few small plants aren't going to "clean up" a canal.

This is excellent, honestly. We recently moved a few billion requests each month behind CloudFlare and our metrics show that our median user (in terms of load time) had their assets loaded almost 40% faster. It's also worth noting that CloudFlare is the only reputable CDN that currently supports SPDY, and is (purportedly) actively working to turn on HTTP/2. Compare that to a company like Akamai that's still advertising Edge Side Includes like they're new and innovative and the year is 2004.

I think you're forgetting how good the web was ten years ago.

"Immune to viruses in spreadsheet files."

I find this claim dubious.

Nah.

https://twitter.com/robots.txt

They blocked robots on their marketing pages.

I really love this. When I was young, I was really excited to learn to play the piano. The biggest problem I had was being able to read the sheet music. It was incredibly difficult for me to read and understand the notes for both hands at the same time. A big part of this was that when individual notes were off the normal staff (e.g., C is below the staff), you either had to have an innate sense of how far from the staff it was and what note that corresponded to, or you had to stop playing and count to see which note it was. This seems to solve all of those problems.

Alright kids, hug it out

1. They don't want you to talk to other people 2. Good exercise 3. Mastery of efficiency is praised 4. Stable job

Seriously, where does the line start?

Unfortunately, yes. Every mom-and-pop PHP-based website that was done by a teenager in the last 15 years probably still does this at some level. There are also plenty of old web servers out there that look for those headers to decide how to respond (to account for browser bugs).

There's a CSRF token in the form, but deleting it doesn't seem to cause the search to fail.

1. He's complaining about bugs in IE7 that "weren't fixed until IE8" Seriously? It's 2013, the modern web runs on IE9 and up. If you're still building for IE7 support, then you have no idea what the consensus of the web dev community is. Google sites don't even run on IE7. 2. His "hack" is necessary because he doesn't understand how to use CSS layouts properly. Instead of absolutely positioning those folksonomies, he should have been floating them and settings max-widths. You can't blame the web for your own ignorance. 3. CSS3 browser prefixes are largely dead and gone and complaining about them is meaningless and misinformed. If you're still targeting Chrome 10 and below or an IE10 preview release (less than a fraction of a fraction of a percent each), then you're simply an idiot.

My project is waiting for your pull requests! https://github.com/mattbasta/areweequalyet

The only thing that turns me off to a product more than a poor website is poor English in the documentation. If English isn't your primary language, PLEASE get someone that speaks it fluently to either write your docs, translate your docs, or edit what you've written.