All my apps going forward will be progressive web apps. Progressive web apps are web applications which are designed to work even more seamlessly on mobile devices than native mobile apps. What do I mean by “more seamlessly?” I mean that most web traffic comes from mobile devices, and that users install between 0–3 new apps per month, on average. That means that people aren’t spending a lot of time looking for new apps to try out in the app store, but they are spending lots of time on the web, where they might discover and use your app.
Progressive web applications start out just like any other web app, but when a user returns to the app and demonstrates through usage that they’re interested in using the app more regularly, browsers will invite the user to install the app to their home screens. This is where it gets interesting. This has been a long time coming. Some History In the early days of the iPhone, there was no app store. Retiring Python as a Teaching Language. For the last ten years, my standard advice to someone looking for a programming language to teach beginners has been start with Python.
When I was more active in the frontend community, the changes seemed minor. We’d occasionally make switches in packaging (RequireJS → Browserify), or frameworks (Backbone → Components). And sometimes we’d take advantage of new Node/v8 features. Scaling On The Cheap — Startups, Wanderlust, and Life Hacking. Scaling On The Cheap “Planning is bringing the future into the present so you can do something about it now” — Alan Lakein I’m going to take a break from my Tech Hiring and Team Building series to write a more technical article.
Why I’m not staking my future on MeteorJS. Why I’m not staking my future on MeteorJS.
TLDR: After about 3 weeks of using Meteor seriously (8 hours a day), I decided that, despite its benefits, it would be shortsighted, and perhaps lethal, for my organization to use Meteor. jQuery considered harmful. Heh, I always wanted to do one of those “X considered harmful” posts*.
Presumably most people still do this but they're the same people who aren't reading this blog post so we can pretend they don't exist unless we end up consulting at their companies and oh god oh god please no not that. The great/awesome/amazing thing about JS is that nobody wanted to go near it and in enterprise organisations they just wanted to stay in their safe little world of well organised layers of abstraction ordered by factory and XML super injection frameworks. That was great for people like me who wanted to get paid enterprise rates but didn't want to have to put up with layers of awful "best practises" and performance problems that came from the irrational fear of letting anybody who wasn't a DBA touch the database. We've hit peak JS You ruined it Angular.js: service vs provider vs factory? Why you should not use AngularJs.
Why you should not use AngularJS Much time has passed since AngularJS birth (given the fact how fast front-technologies evolve).
Obviously, this post has big red ‘opinion’ stickers over it. But hear me out.