5 ms·
Hey guys, please take a look at the following app: http://editgrid.com/untitled http://editgrid.com/untitled It's the coolest web-based spreadsheets applicatio
by combataircraft 15y ago
Hey guys, please take a look at the following app: http://editgrid.com/untitled http://editgrid.com/untitled
It's the coolest web-based spreadsheets application built 6 years ago using no library, no framework. I'm a fan of it. It was looking just like this current version 6 years ago and was pretty fast at even IE6. And its 6 years old JavaScript code follows the rules of coding good JavaScript code way more than Ember itself.
Here is another story: I was working for a competitor of EditGrid and built a Microsoft Excel clone with dozens of features in 6 months, using no framework, no library, 5 years ago. We were two guys at frontend and two other guys in at backend. And our source code was almost pure object orient, mixable, reusable and relying on MVC, event-driven programming.
I've been shipping rich web apps for more than 6 years and recently had the chance of working with both Backbone and Ember. Here is my feedback:
The size of Ember library is bigger than total source code (including an AI library) of the last multiplayer game I built.
And both of them solve no problem, simplify nothing. They just force beginners to not code crappy code and that's all. Good JavaScript code should benefit of functional programming very well, like some NodeJS apps and libraries. They got no understanding of FP. Especially Ember relies on a horrible idea that increases the cost of development very huge. Very ironically, ember code is not reusable, not mixable with other web apps. It's not even unobtrusive, pollutes Object prototypes. When you finish your app, you got a huge garbage that has not even one piece of reusable code.
To summarize, there is nothing Ember does right. It tries to solve already solved problems in a very absurd way and is very irrelevant with the new problems JavaScript community tries to solve (such as code-reuse with NodeJS apps, it's partly solved)
It's the new, communist North Korea of JavaScript world.
- edwardhotchkiss 15y agoI think that you should check out Angular.js. I have a blog post on it. Basically to write the app "no library no framework" (or even using jquery) - would be a lot more work. I think that you're trolling but I'll bite and link you anyway. http://edwardhotchkiss.com/blog/2012/03/11/jekyll-live-search-with-angular.js/ http://edwardhotchkiss.com/blog/2012/03/11/jekyll-live-searc...
- combataircraft 15y agoI'm very happy and satisfied with my current development kits and methodology. I use no framework and don't write any classes. http://en.wikipedia.org/wiki/Functional_programming http://en.wikipedia.org/wiki/Functional_programming
- LBarret 15y agoPlease write an article about your approach, I am really interested.
- Sivart13 15y agoIt sounds like you're a pretty good JavaScript developer. Great! Not everyone doing JavaScript is as good as you, and frameworks can help guide them toward better solutions. Could you elaborate on the "horrible idea that increases the cost of development"?
- combataircraft 15y agoBetter solutions are already provided by JavaScript itself. Event-driven programming was the idiomatic solution until CPS became the one everybody follows with the grow of NodeJS. See how NodeJS community deal with async programming.
- Sivart13 15y agoThe idiomatic solution to what? Ember.js and other frameworks exist to provide a basic structure for heavy client-side applications. Namely, a way to separate your "models" from your "views", if that's something you think is worth doing in your application. JavaScript is a language, not a framework, and thusly provides none of this structure. "Event-driven programming" and "CPS" are just idioms that can be used within JavaScript. If you don't like the way the Ember framework is structured, that's fine! But you probably have a personal style that you use in your applications that could be distilled into some kind of framework, and there's more to it than "CPS".
- combataircraft 15y ago@silvart19, I was talking about EmberJS' bindings. That's what makes Ember apps crappy. For the mention of MVC, you don't need to use a framework that forces you to live in North Korea.
- mhd 15y ago"They just force beginners to not code crappy code and that's all." That's a pretty huge deal in my book.
- combataircraft 15y agoI prefer teaching beginners the JavaScript way of doing things instead of forcing them to write spaghetti code.
- mhd 15y agoSo it's "not crappy code" but "spaghetti code"? Could you elaborate on that a bit, I don't quite get the argument here.
- sant0sk1 15y agoDo you have any open source projects that I can read through?