potch

Correction, getpersonas.com is now decommissioned!

The migration is actively underway! The site will be shut down in a time scale ordering on weeks.

I work for Mozilla, but speak for myself. If you think it was about control, then you don't know how Mozilla works. We fight larger players with one arm tied behind our back because of our commitment to making things open and interoperable. We do it gladly, because we know that sometimes our reference implementation won't be the best implementation, and even if we fail, we want the tech to live on. Every day I have or overhear a discussion about making certain what we build doesn't privilege our own solutions over others. Are we perfect at this? No. Sometimes security of our users trumps a completely level playing field. But every time we have to slightly close a technology, know that it's done extremely begrudgingly.

Sometimes require.js feels a bit heavy for what is mostly a straightforward concept (AMD), so I use a much simplified version of the pattern: https://gist.github.com/potch/4156519

The ability to highlight search terms in a page.

You may disagree that is a better experience for you, but you may not make blanket statements that "there are no such cases, period".

I have some bad news about what constitutes a "normal" website these days.

I'd love a way to see the code that ran to generate the output.

I'm curious what you've decided the purpose of this site is. This seems like a huge issue to discuss around the future of software and the concept of "abandonware", as well as a cautionary tale about DRM, scaling, and failing to plan for success. All sounds about right to me for this site.

If you viewed the above screenshot, you would see that in fact the current Firefox developer tools do the same thing.

I work for Mozilla, but I speak for me.

Supporting a monoculture is trading future potential in the name of short-term convenience. This doesn't just apply to rendering engines, or even just technology. Wishing you could wave a magic wand and make everyone use the same tools, language, conventions, or coding style is something every engineer wishes from time to time, but the world would be worse off without diversity.

Wishing one rendering engine "wins" over the others is a reasonable thing to say, and WebKit is a very fine engine. But the moment we start treating the Web as a zero-sum game and stop collaborating on the vision of a better online experience, nobody wins.

So when a user types '-webkit-', and doesn't type '-ms-,-o-,-moz', when they all work, that's laziness on the vendor's part? Or better yet, when the syntax 'linear-gradient' works and you don't need a prefix at all, and you don't bother because you can't be bothered, that's laziness on the browser vendor's part? The vendors have bent over backwards to be fully compatible on gradients, animations, transition, border radii, box shadows, keyframes, and boat loads more every day. Every vendor makes compromises, the prefixes get removed and the whole web moves forward as one unified. But you'd never know it because hack developers can't be arsed to at least open one other browser to see whether it even worked. But yes, the vendors are lazy.

That this only renders properly in Webkit is a result of pure laziness.

Hello! I work on the Firefox OS app store[1] . There are no officially supported Firefox OS devices yet- but you can experiment with the simulator[2]. Additionally, they will soon be able to run on any Android device with Firefox for Android installed. (certain apps work already in our Beta version[3])

Hope that info helps!

[1] https://marketplace.firefox.com/

[2] https://addons.mozilla.org/en-US/firefox/addon/firefox-os-si...

[3] https://play.google.com/store/apps/details?id=org.mozilla.fi...

If you are guessing that all engineers who understand how to use the command line are well-organized, I can provide you at least one certified example of one who doesn't match your worldview. This is awesome.

I can't reproduce- what version of chrome are you using? I'm re-evaluating all my loops to increase general safety.

I believe I made a huge mistake in my calendar rendering code. Hoping it's fixed now. Sorry for freezing!

Thank you for the bug report!

>6k and a jQuery dependency? Dates aren't as hard as they used to be. I'm working on a pure-JS datepicker for modern browsers that will clock in at under 5k minified, with no dependencies. Take a look at my work so far here: https://github.com/potch/fortnight.js

(Edited to correct that the likely final minified size will be closer to 5k. Hoping to add accessibility features and localizability.)

"The building itself is being evacuated and no remote hands support will be available to assist in any equipment shutdown. Life safety is our number one priority and we are making plans to completely exit the facility."

Uptime that requires people to risk their lives isn't worth asking for.

So I can steal someone's phone, and just have it remind me of all that user's private info by walking around? Nifty.

Edit: I know the above is glib, and I'm not trying to rain on the parade of unbelievable achievements in data-wrangling that are going on here (I'd love to hear how it's done computationally), but I don't like knowing that all the privacy controls something like this deserves will be rolled out hastily in response to someone's life inevitably being ruined by the careless trust of one's life to a device that can fall out of their pocket. It's easy for the savvier of us on this site to say "serves them for not thinking to take precautions", but when we make it so easy to give a third party the reins, even we get complacent.

Nah, the "partial" implementations are all highly compatible with the current spec (which chrome implements), and it's not much more polyfill to achieve solid cross-browser compat.

Thanks!

I added a bookmarklet of the original code to the site- I know you're legit, but I'm always wary of encouraging people to load random external JS via a bookmarklet.

I wrote some JS to add keyboard controls to the map, because clicking and dragging is for suckers. http://www.potch.me/blog/press-and-hold.html

The distinguishing factor in this era of the Web is that now acquisitions are treated with dismay rather than celebration. Web 3.0 is much more cynical toward the big corporations (and in my opinion, rightly so).

Hello- Mozilla employee here, though not a Firefox developer. The good news is it's easy to change how we apply updates from completely silent to "download and choose" to "only check when I tell you". The bad news is, unlike many situations of security theater, we frequently ship security updates due to known existing and actively exploited security vulnerabilities. Staying up to date is the easiest and most practical way of keeping your browser secure. If you want the security updates but find the frequent feature changes jarring, we offer our Extended Support Releases here: http://www.mozilla.org/en-US/firefox/organizations/all.html. I hope you'll adjust your update settings to something that works well for you- we really are trying to keep users in control.

My advice? Take the layers of middle managers who have been there for years, give them their gumball machines or espresso makers, offer to buy out a percentage of their long-underwater options, and make them promise to go work somewhere else.

The inertia is so ingrown there the only way is to cut out the "lifers" who were given their incentives in equity and clog up the system with incompetence or resentment.

I think JS is a good language, but I am probably not in my right mind, so touché.

If the only factor in your market's efficiency is price charged, then this is true. The real market has other factors like satisfaction/willingness to repeat a transaction (for both sides of the party), opportunities for disruption of your market (exacerbated by said dissatisfaction), and (gasp!) goodwill of parties in a transaction. If you're optimizing just the ledger numbers in your industry, you might make a buck, but you're setting yourself up for hatred and being toppled by a newcomer who customers actually like.

I wish people who have written HTML for years would play around with this if for no other reason then to learn what all the new semantics of HTML5 are.

Have you considered not personally flaming the original authors in public?