Reminded me of streamlinejs (https://github.com/Sage/streamlinejs) but I guess what makes your library better is that there you don't have the compiler overhead they need, right?
just this month we hit a point, at which we were confident enough to release this and now we're even more confident, so we put it on HackerNews.
If you care about our techstack: the backend is built using rails, em-websocket and postgres, while the Frontend relies on angular with some Backbone leftovers. Messaging is done via vanilla websockets and protobuf.
Every kind of feedback is welcome, however harsh. Thanks!
Thanks :) Atm we're only on FB & G+, but as soon as we figure out how to create a twitter page for non-people, we will do that. Here are our handles:
https://www.facebook.com/solon.rocks
Protip: If 80% of your agument is an analogy, it's probably not a very good argument.
I think the opposite is true, IDEs help you find out what is really going on, by showing you (depending on the language) which module is used where and giving you the option to directly navigate to that source. That in turn confronts the beginner with the code and conventions of other (more experienced) coders. So yeah, IDEs rock. Also debugging...
IDE's aren't the only way to find out which module is used. Why is this such a mystery in the first place? Is it because the programmer doesn't know, because they don't care to know, or is it because the details for how to find out what modules are used in your project are hidden in some sort of arcane manner which precludes their extraction with simpler tools?
IDE's are great if you use them. Editors are, too. But the point is that an over-reliance on IDE's will degrade your skills, generally, and command/control over your project, precisely because it does too much work for you, and your understanding of the subject thus atrophies. If I had a Btc for every new-school "IDE's are the awesome, can't live without them" superstar programmer who nonetheless couldn't navigate his way around the build system, or even directory hierarchy for their very-valuable software system, I wouldn't have to write software for a living. Probably.
It is sage advice, this "don't become addicted to your IDE" statement, because IDE's are also a walled garden, folks. There are reasons the "Developers^3"-mindset was so ironic way back then; if, as a platform vendor, you capture developer mindsets then you safeguard your platform from being undermined by your competition: other developers. Never forget that its turtles, all the way down, folks .. and your average modern IDE is a big, hungry, fat one.
