3 ms·
Not to get into a flamewar about OS'es, but why start out with Safari? If you're looking for a large demographic, which I presume is the case, it would make the
by mixmax 17y ago
Not to get into a flamewar about OS'es, but why start out with Safari? If you're looking for a large demographic, which I presume is the case, it would make the most sense to develop primarily for IE,then Firefox, then Safari.
Is it a question of trying to get opinion leaders (typically mac users) to try it out first, are there technical reasons or is it something else?
Just curious.
- mdg 17y agoI was wondering the same thing. I would like to think they ran analytic s on their traffic and noticed Safari as the browser they get the most visits from.
- johnrob 17y agoIn the early stage, it's more important to get the product right than find the biggest market. I'm guessing the developers use Safari, and they want to 'eat their own dog food'.
- blasdel 17y agoI know I'd feel like a shitheel writing an ActiveX plugin for IE. The last several major versions of Mozilla have inanely required you to fully restart your browser process to install any extensions or NSAPI plugins, and you aren't allowed to have multiple browser processes touching the same profile. It's a fucking conversion killer. A large part of Greasemonkey's existence is due to how poorly architected extensions are -- the full restart, zero sandboxing, etc. Webkit's native plugin API is really goddamn cool but I don't think any shipping software used it before ClickToFlash.