From what I've gathered this is a fairly accurate summation of the pattern that many (if not most) large JS applications have fallen into. In the last few months I've headed moving Estately's old and organicly grown JS onto a system very similar to what's described here. http://github.com/aconber...
- Anders Conbere
Agreed (at large scales), but that's not politically correct ;) I guess the only option is to let people figure that out by themselves ;)
- Julien
I mean it strikes me as a solution that results from folks with entrenched interests in HTTP, which is fine, cause well... that's most of the world really (pets his web browser kindly).
- Anders Conbere
from email
I can't be the only one that thinks these ladies, covered in grease and working up a sweat (or... covered in grease for a photo shoot, either way) are smokin hot.
- Anders Conbere
I'm not sure about his methodologies. But I know in my experience this certainly rings true. And certainly my question is a one of supply.
- Anders Conbere
I couldn't agree more. OSCON this year was fantastic in Portland it would be sad to see it move to San Jose which is simple not as charismatic a city.
- Anders Conbere
I think this is a 100% useful post for any erlang developer to read, I'm just not sure that the problems he's trying to solve crop up seriously in anyone's code who is familiar with functional style and erlang in general. That being said, the idea of building a python/erlang like language that has concurrency built it is just fantastic :)
- Anders Conbere
This software developer does not have a detailed list of all "the things he needs to do. Which means, despite adamantly claiming that he is 99 percent done -- he has no idea how long development will take!" This is such a telling statement. It's not that the software developer thinks he's 99% done really. That statement derives from the developer knowing that they've "solved the problem". There's however a disconnect between what the manager and the developer perceive as "the problem"
- Anders Conbere