- What is a “native web app”?
- What about progressive enhancement?
- The performance implications of clientside apps
- Twitter’s move away from clientside back to server-rendered
- The two classes of web apps
- User expectations of modern applications
- Installable web apps
- True offline support for web apps: ServiceWorker
- Isomorphic (dual-rendered) applications
- Picking tools for a rapidly changing environment
We’ll let Luke explain:
That was awesome. Way to go, Luke! If you want updates on more awesome stuff like Ampersand.js, why not sign up for our mailing list? Details below.
While working on a line of business application for a client recently, I was asked to research and implement two different approaches towards improving data updating efficiency and consistency.
The first is JSON Patch. The idea here is to reduce data transfer by only sending the operations needed to make the remote resource identical to the local one. Even though both resources are represented as JSON objects, applying patches means we don’t have to replace the entire entity on every update. This also reduces the risk of accidental changes to data that stays the same.
There’s a bit of a kerfuffle right now in Angular.js land because, lo and behold, the 2.0 release contains drastic differences and there isn’t really an upgrade path.
If you want to upgrade you’ll likely need to completely re-write your app!
The structural updates they’re proposing all sound like good improvements, but if you built a large app on 1.x and want to upgrade it doesn’t really seem like you’ll be able to use much of your code.
Losing your religion
Ok, so what should you do? Pick another framework?
TodoMVC is a neat project with a simple idea: to build the same application with a whole slew of different frameworks so we can compare how they solve the same problems.
There are a few aspects of the implementation that I thought were worth writing up.
First, some highlights
- filesize: Total filesize of all the JS assets required for the app only 24kb(minified/gzipped) which, for comparison, is smaller than jQuery by itself. By comparison the Ember.js version is 165kb and that’s without including compiled templates.
Two of our core values on the &yet team are curiosity and generosity. That’s why you’ll so often find my yeti colleagues at the forefront of various open-source projects, and also sharing their knowledge at technology and design conferences around the world.
As a portion of our elaborate training events I give a short talk about JS frameworks. I’ve shied away from posting many of my opinions about frameworks online because it tends to stir the pot, hurt people’s feelings, and unlike talking face to face, there’s no really great, bi-directional channel for rebuttals.
But, I’ve been told that it was very useful and helped provide a nice, quick overview of some of the most popular JS tools and frameworks for building single page apps. So, I decided to flesh it out and publish it as A Thing™ but please remember that you’re just reading opinions, I’m not telling you what to do and you should do what works for you and your team. Feel free to disagree with me on twitter or even better, write a post explaining your position.
We understand that very few people, both in tech and in the world, have access to the resources needed to level-up in their careers. This is especially true of marginalized groups, who are consistently underrepresented and often even pushed out of our industry without the opportunity to thrive here.
We also understand that there are serious barriers to entry in our industry that keep people who are marginalized by race and/or gender from entering and actively participating in our field.
But we missed the focused simplicity of tiny modules in node-land. We wanted something similar in style and philosophy, but that fully embraced tiny modules, npm, and browserify.
So we made Ampersand.js, a well-defined approach to combining (get it?) a series of intentionally tiny, and loosely coupled modules for building JS apps.
Backbone has been praised for its flexibility and simplicity. The fact that Backbone’s author Jeremy Ashkenas and his fellow maintainers haven’t tried to solve every problem has kept it usable for a broad range of application types. Its effectiveness is evidenced by its incredible popularity.
JS for Teams: It’s ALIIIIVE! is a two-day training adventure happening July 24 & 25 focused on teaching teams how to build advanced single-page apps in a highly maintainable way. Tickets on sale today!
To celebrate, we’re offering $200 off per ticket for the next 5 tickets – use the discount code AMPERSAND at check-out.
The tickets we set aside for our email subscribers already sold out, so don’t miss your chance. Seats are extremely limited.
Page 1 of 3 | Next »