potch

IMO, LESS's strength is that its implementation is JavaScript. Allowing for real-time compilation during authoring in-browser is great, and coupled with uglifyjs and cleancss (also js) allows for a single dependency during our build stage. This has some very interesting ideas, but maybe I'm just a purist- ignoring the concept of the "cascade" seems counter intuitive to me.

Nothing, actually! It's already in our Nightly builds, and will be appearing in Aurora some time this week. You can grab Nightly at http://nightly.mozilla.org

"Modern Web Development" does not mean "Works in Webkit", and it does a disservice to future/novice developers to reinforce that notion. What's dominant now was not in the not-too-distant past, and may not be in the not-too-distant future.

missed a negative sign- all better!

Took a crack at making a CSS version:

http://potch.me/markdown-mark.html

He's very particular about how this symbol should and shouldn't be displayed. Don't think that's a bad thing, but it's interesting.

The author is either a robot or speaks English as a second language. There are a ton of factual inaccuracies that aren't present in the linked source material.

Glad to see Lyons getting in on the conversation. And by conversation I mean grab for pageviews.

100% agreed. The process has to move faster.

My complaint is not that -webkit CSS extensions are bad. I love how fast the browsers move. It's that people aren't careful to make sure they use all the prefixes when they're available. It's an education problem, but people using CSS preprocessors such as LESS and SASS have no real excuse.

I don't see this as "mean government takes $2B" so much as "Mark Zuckerberg nets $3B"

I interpret this as a call to use innovation and creativity to produce something constructively that will bring Hollywood the fear, and I approve 100%.

That notion could not be more wrong.

I work at Mozilla, and the atmosphere between us and Chrome is not the high-stakes cage match people would have it be. At a fundamental level there's only so much market share, but at an engineer-level, we're insulated from such corporate politics. It's a cooperative atmosphere, and we both succeed with each others' help and knowledge.

The hopeful part of me loves this because I truly believe the web stack is a truly democratizing technology, and has tremendous accessibility.

The cynical side of me also loves this because I like watching PL bikeshedders rage.

Goodwill? Do you think Google's shareholders get warm fuzzies when they see the news of this deal? This arrangement sends Google large amounts of traffic, from which they derive significant financial value. Stop calling this charity, it's a mutually beneficial arrangement.

Edit: I mentioned this before below, but I'll repeat it up here. I work for Mozilla, but was not involved in the inner workings of this deal. I'm stoked to know where my salary is coming from though :)

The open governance of the Mozilla project is not subject to the sort of back-room dealings you imply.

(Disclosure: I work for Mozilla, but have no knowledge of the inner-workings of the new deal.)

wrote a labyrinth demo back in the day to demo the Firefox-prefixed version of the API. I've updated it here: http://potch.me/labyrinth/

I've been working on a less-configurable sort of graphite dashboard for use as an ambient display- https://github.com/potch/statsdash. Looks great on a tablet.

> I don't understand why people get so caught up in something they literally had nothing to do with other than giving their money away to achieve.

They get caught up because they gave away their money. It's a matter of opportunity cost and rationalization at some level. Because these platforms are usually non-cross-compatible, "buying into" a specific platform entails a commitment of irreplaceable capital. When I was a kid, my parents got me a Super NES. Regardless of where you stand on Sega Genesis -vs- SNES, you were sure to defend the system you had, because, well, it's the one you have.

If you've invested years upon years of time and money in a particular pursuit, it seems natural to want to defend it.

Much respect for making it to the 1.0, that shows great dedication on his part. He earned the break, and I look forward to seeing what's next!

"No seriously this time you guys!"

I promise you the fox isn't going anywhere, but add-ons made with the new APIs don't require restart.

Hello! I work for Mozilla. To address the problems with our extension versioning system, we've begun running an automated suite of tests against addons that will automatically make them as compatible with the next version of Firefox. The system performed well for the 4 -> 5 update, and we expect to tune it better. Additionally, if developers use the new set of extension APIs as opposed to the older ones, compatibility is a much simpler affair.

The map was generated using continent-level shapefiles (I believe from here: http://pubs.usgs.gov/of/2006/1187/basemaps/continents/). We stuck with continent-level outlines because adding country boundaries would have needlessly complicated the SVG, and borders can sometimes be disputed and controversial things :)

It would have been nice to have the great lakes and caspian sea, because they're such large features but with a team of two webdevs, some things have to wait until version 2.