![]() This really does not exist in any sufficient way. Now if phones have better and better cpu, why are newer phones in 2017 still feel as sluggish as the ones in 2007? Again, it's because the phones have better cpu now, mobile OS and software developers put more and more features in their code and make use of all that extra cpu resources.īut for the current state of CRUD application frameworks that do not do this, it implies some enforcement at the data layer and probably some hint at this at the ORM level. Battery tech is getting better and better, why do phones in 2017 still only last < 24 hours, instead of 3 days? It's because battery got better, all the phone manufacturers (Apple, etc.) made use of that extra power and put better cpu/memory in their phones. It is very similar to mobile phones cpu/memory and battery. Notifications didn't appear at the lower left in addition to the notif dropdown. Even if it was, it definitely did not have video chat and voice call straight from that. Your inbox chat might be on a separate page (can't remember if they had the bottom chat bar in 2012 yet). and now utilize them fully to build many more features on top of it.ĥ years ago, your notification bubble would often go out of sync. ![]() I totally hear you re: everything being built in React nowadays and SPAs are annoying both as a user and a developer, I definitely feel like that sometimes.īut the answer to your question, why isn't Facebook significantly better than it was 5 years ago, is exactly because they've invested a huge amount of time in React etc. Step back and build some pieces of your site with tools that can look at your database and spit out some sensible defaults for CRUD screens, shamefully pre-rendered on the server as they may be, for the pieces where it makes sense to do so. Because that's what The Trend has told you to do. And you use none of that power on your page, but you have it there in reserve, just in case. And you have all the power that made sense for the engineers at Facebook to use on their newsfeed, where things would regularly change behind the scenes and the page needed to re-render and re-flow itself several times a minute without the user noticing, for which a brief 3 second "flash of empty container" was a reasonable trade-off. So you find yourself dragging in a few megabytes of javascript just to render your static blog page. Even when it makes no sense whatsoever to do so. Everybody wants to build Single Page Apps today. I imagine the answer (to my question, and thus yours) is that fashion changed. Rails is the obvious one to point to, but there are dozens of others built in the late 00's that all tried to recreate that "20 minute DB-Backed Blog" demo. I suppose a better question is "Why aren't you using a framework that automates 90% of your CRUD?"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |