4 ms·

Believe it or not? After attempting interface development on all three platforms, as much as I hate it and all of its idiosyncrasies, I fall back to windows on

Believe it or not? After attempting interface development on all three platforms, as much as I hate it and all of its idiosyncrasies, I fall back to windows on the operating system standpoint. Everything I need is there, and in some cases nowhere else (without running a VM). - Visual Studio 2008 Express. has some of the best Javascript support out there. Sorry, but TextMate doesn't have anything to check for stupid syntax errors on the fly - and NetBeans is bulkier, imho. The only thing you're missing is third party add-ins, and I haven't found much use for them yet. If I need to step into some ruby, I'm fine with TextMate. It's not the best tool for JavaScript though. -IE6 and - IE7. Developing for them is an interesting challenge. And a necessary evil. Because you're developing on the same machine you're debugging IEx on, it's a lot easier to use Visual Studio to place breakpoints, watches, and so forth than to use the mostly useless default script debugger. - Safari or Chrome. -Firefox, with Firebug. And YSlow!. And the Web Developer toolbar. - Pandora. (I find I only listen to my music collection when I'm commuting) - Photoshop. - Google Docs - Skype - Pidgin (ugh; it's horrible on all platforms...) So as it happens, Windows unfortunately is the only platform I can run all my tools on. Sucks but there it is (I'd rather be on Ubuntu. I can do stuff like pin a stationary translucent terminal with no decorations to my desktop. And the terminal app for AWN is fairly spiffy for quick one-offs).

jpcx01 18y ago
Textmate has the awesome Javascript Tools extension http://www.456bereastreet.com/archive/200901/javascript_tools_bundle_for_textmate/ http://www.456bereastreet.com/archive/200901/javascript_tool... shift+control+v and it runs it through Doug Crawford's lint engine. It also has the option of running it on every file save. Also, I'd suggest using IE8 instead of IE7. It has way way better dev tools, and built in support for IE7 (using the compatibility mode button). As for IE6, you should do us all a favor and drop support for that ASAP.
- warfangle 18y ago
  No can do. 8% of our userbase still uses it. Not my decision to make, unfortunately. I've used the javascript tool. "1 error, 2 warnings," with no explanations? I'd rather copy/paste the code into jslint and run it manually. It also doesn't find some of the things that the original jslint tool does. Really, it's "awesome," but only if you haven't used something like VS's Javascript support. Sorry, but it's lightyears away. It's kind of like the difference between using nano and using gnome's default text editor...

jpcx01 18y ago

Textmate has the awesome Javascript Tools extension http://www.456bereastreet.com/archive/200901/javascript_tools_bundle_for_textmate/ http://www.456bereastreet.com/archive/200901/javascript_tool... shift+control+v and it runs it through Doug Crawford's lint engine. It also has the option of running it on every file save. Also, I'd suggest using IE8 instead of IE7. It has way way better dev tools, and built in support for IE7 (using the compatibility mode button). As for IE6, you should do us all a favor and drop support for that ASAP.

warfangle 18y ago
No can do. 8% of our userbase still uses it. Not my decision to make, unfortunately. I've used the javascript tool. "1 error, 2 warnings," with no explanations? I'd rather copy/paste the code into jslint and run it manually. It also doesn't find some of the things that the original jslint tool does. Really, it's "awesome," but only if you haven't used something like VS's Javascript support. Sorry, but it's lightyears away. It's kind of like the difference between using nano and using gnome's default text editor...