<< Firefox OS App Workshop in Wien! | The roads I take... | Preserving Software - Feedback Requested! >>
While we at Mozilla know you can do a lot of good things in JS these days - after all, we're even launching our own phone OS building fully on HTML+JS, and we have been using more and more JS code to power key functionality in our browsers and other products over the years - it's great to see that complex things like editing maps can be done fully in JS and available for all platforms now, while previously it took proprietary and availability-limited technologies like Flash or Java to do the same thing.
Great work, OpenStreetMap guys!
(And yes, as a contributor to OpenStreetMap and even OSMF member, I am biased, but free and open map data on the web fits Mozilla philosophy pretty well anyhow...)
On the mozilla end, this bug (https://bugzilla.mozilla.org/show_bug.cgi?id=837985) will need to be fixed for this great js based osm editor to behave properly
The new iD editor is perfectly usable in Firefox 20.0.1 on my box. I don't run Beta, Aurora, or Nightly like the cool kids. I've been making neighborhood and community edits just fine, even with multiple tabs loaded in the background. To be fair, I have an above-average desktop computer, so I am sure only people with slower processors, less RAM, or older Intel integrated graphics are really hurt.
I wish iD in Firefox was as smooth as Google Chrome; but I get a consistent frame rate, there are no sudden interruptions, and RAM does not spiral out of control.
The performance in Firefox could be much better, but it is not bad enough for anyone to release a "Chrome only" warning. I predict the worst case will be a few people complaining, some loudly.