Allt has been working really well so far, but now, I want to push it to the next level. Allt is a platform I truly believe in, and I strongly believe that it will upgrade the way people work everyday.
To make sure we are ready for the next decade of the Internet, I want to see which front-end platform would be best to use when moving the front-end code to a completely new codebase.
I’ve listened to almost all the talks that Jeff Atwood spoke about Discourse, and he seems to make a valid point for using Ember.
I went through this blog Robin Ward (Co-founder of Discourse) wrote about choosing Ember for a front-end MVC rather than something that way popular than Ember, like Angular:
1.1 So when you access a front-end MVC like Ember, there’s this huge JS ball (as Jeff likes to call it) rolls out to your browser. And from then on, literally everything that happens is by rotating this JS ball in your browser.
1.2. Whenever there is some change in the UI or data via the backend, it gets pushed right then and there, without having to reload the page.
1.3 Since Allt is a platform that will potentially be open all the time in our browsers, making sure the changes and updates we do in the backend reflects immediately to everyone is crucial. I believe that the can solve the issue; correct me if I am wrong.
- Here’s one more reason why they seem to lean towards client-side MVC.
- Ember is lightweight; its just 47kb when minified. Fair enough.
- Client-side MVC is API-first.
- Simple Documentation
Kick starting these conversations here, so that it is public, with a hope that people would help us arrive at some solution here.