Why? There's no deployment issues. There's no waiting for my app server to restart, no delay while a change is detected, etc. You edit a file, click refresh.
Flame away.
115 karma · joined September 25, 2010
Why? There's no deployment issues. There's no waiting for my app server to restart, no delay while a change is detected, etc. You edit a file, click refresh.
Flame away.
kill me. Makes me want to kill myself.
WTF is the point of it all?
However, I hate many of the Java APIs, specifically most "JEE" crap, such as EJB, JMS, most third party ORMs (Hibernate), most Java "web frameworks" (too numerous to list).
Java IDEs are bloated, slow, and often unstable with extra plugins (Eclipse)
you might get some nasty letters. yawn.
You'd have the same issues if you developed on Debian and deployed on RedHat Enterprise.
Never learned to touch type the "right" way...
Not sure I'd want to...
I have native code calling into JS code that runs in UIWebView, and JS code calling back into Obj-C, etc.
The big difference is node is event-based...
Twitter. Ugh.
later on, right before the bubble burst, the place was totally over-funded and hired tons of people who didn't know what they were doing at a technical level. many of the people "in charge" (VP level, etc) were complete buffoons.
cronyism, nepotism, and incompetence ran rampant. there were many useless managers, directors, assistant directors, on and on. this was typical of companies of that era. this provided ample opportunity for goofing off.
i could tell you some detailed and hilarious stories, but i'd wind up outing myself.
why not "hot deploy"?
hot deploy doesn't work when you're working with other developers who are violating the JEE spec (mainly by starting their own threads.)
I have yet to have a programming job where more than 4 hours a day of "work" was required.