4 ms·
Whenever I read a project with a marketing pitch of "Some server specifically for some client side framework!" I can't help but feel the author has lost their m
by rubiquity 12y ago
Whenever I read a project with a marketing pitch of "Some server specifically for some client side framework!" I can't help but feel the author has lost their mind.
The browser is just a client, people. All of the frameworks for the browser are just (supposed to be) abstractions for creating dynamic browser applications. If you need to create server frameworks specifically for working with a client framework that should be a sign to stop and think that something might be wrong.
- prottmann 12y agoYep, and the answer of this is https://www.meteor.com/ https://www.meteor.com/
- jonny_eh 12y agoSynth author here. I do realize the idea is crazy. In fact I call it a crazy idea in the video embedded on the page there. I love crazy ideas. Crazier the better! But I will disagree on the point that the browser is just a client. It can be treated like that, if you want, but you can take advantage of the fact that the client code is serveable from the same server that has access to the app's data. And that's what Synth was designed for.
- pessimizer 12y ago>you can take advantage of the fact that the client code is serveable from the same server that has access to the app's data. But you really shouldn't.
- ebiester 12y agoWhy? Consider that on projects where the domain problem is simple yet the user requirements are complex, it may make more sense to optimize speed of development of the client. a webmail client would be a great example of this. The server side is really a small problem, excepting for performance. However, getting the client right is why people still use gmail.