A variety of new web frameworks are being cooked up that allow you to write one set of seamless code for the client and server. It's a problem that has haunted the web development community since the dawn of JavaScript and the DOM. One approach is to basically define the database operations on the client. Does that sound like a good idea, or does that sound like a great idea?
Exposes the MongoDB API directly on the client to work on automatically-synced data subsets. What could possibly go wrong? Let's name the project after a flaming ball of rock and find out for sure!
Is client-side MVC too confusing? Is Node.js too immature? Let's combine them and see what happens! (It remains to be seen whether Derby is named after a hipster hat or a county fair event.)
"We have a full security system in the works that will allow you to control read and write access on individual locations in Firebase on a per-user basis. However, it’s not ready for widespread use yet, so right now all data in Firebase is publicly accessible. Please keep this in mind when building apps! Please contact us if you need security or want to be one of the first to try out the new system." *
Despite my scornful tone, I'm actually very optimistic on these technologies and very hopeful that at least one of these will be ultimately successful. I'm also really happy that I'm not going to be the first person trying build an application on this stuff. Given the theme of the project names, it's fair to say that most early adopters will get burned.
* Yes, that's a direct quote.
1 comment:
Thanks for the useful article, wan tot share with you one great web development company from Ukraine http://www.nixsolutions.com/services/web-development-services/ if you're looking for some professional developers for your website or software this is the best solution. Hope you'll like it. Good luck.
Post a Comment