Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I switch browsers more than I switch underwear, mostly between Safari, uzbl, Firefox, Chrome and TOR Browser (FF fork). When I write extensions I do it for the browser I currently fancy, so I've got a few ones for Safari, Firefox and Chrome. But when I switch I lose the old ones, until I switch back.

Right now I'm in Safari (silky smooth rendering), and can't use this. That sucks. But FF, Chrome and Safari extensions are just JS anyways. Why can't they be automatically ported, or something? What's stopping Mozilla from enabling Firefox to run Chrome and Safari extensions, and vice versa?



Aside from the obvious (API's), the use case you describe see,s incredibly small - likely too small to justifiably target.


Because they interact with different APIs.

Different browsers provide similar APIs in different ways sometimes, and usually web standards support differs between browsers.


Any idea if someone has written an abstraction layer for this yet?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: