PWA’s are slowly becoming better on ios, there was another new release of safari that fixed a lot of bugs. But it’s still very niche, since Add to Home Screen is so hard to find for users
1,794 karma · joined March 18, 2013
https://koenvangilst.nl
PWA’s are slowly becoming better on ios, there was another new release of safari that fixed a lot of bugs. But it’s still very niche, since Add to Home Screen is so hard to find for users
Source code: https://github.com/vnglst/tafels.app
(and also to help me learn svelte ;)
Let me know what you think! Btw. had a very nice chat with the creator of gundb (Mark Nadal) right inside the chat app. That was pretty cool. He also tweeted about it here:
https://twitter.com/marknadal/status/1253446569665257473?s=2...
Source code can be found here: https://github.com/vnglst/svelte-gundb-chat
Let me know what you think!
Btw. had a very nice chat with the creator of gundb (Mark Nadal) right inside the chat app. That was pretty cool. He also tweeted about it here: https://twitter.com/marknadal/status/1253446569665257473
Source code can be found here: https://github.com/vnglst/svelte-gundb-chat
Let me know what you think!
Btw. had a very nice chat with the creator of gundb (Mark Nadal) right inside the chat app. That was pretty cool. He also tweeted about it here: https://twitter.com/marknadal/status/1253446569665257473
Source code can be found here: https://github.com/vnglst/svelte-gundb-chat
Let me know what you think!
Btw. had a very nice chat with the creator of gundb (Mark Nadal) right inside the chat app. That was pretty cool. He also tweeted about it here: https://twitter.com/marknadal/status/1253446569665257473
Thanks for the all the hard work (and the excellent blog post)!
Update: ok, as soon as a proposal reaches stage 4 it's considered finalized and part of the standard. A proposal can reach stage 4 at any time during the year. At that point browser vendors will start implementing those. https://flaviocopes.com/es2019/
This is also what the JavaScript community is moving towards, both for the language specs where new features are "released" once they're ready (see: https://2ality.com/2015/11/tc39-process.html) and their respective implementations in browsers and Node.
As far a I can tell, those release processes (with many millions of users and full backwards compatibility going back to early beginnings of JavaScript) are neither unstable nor unpredictable.
Why not ship any improvements you have immediately to the users?
So accept every opportunity you get to practice.
Person who say it cannot be done should not interrupt person doing it. --Chinese Proverb
- Create React App
- TypeScript
- Mobx State Tree
- react-pose
- Howler for sound fx
Source code is here: https://github.com/vnglst/lumber-jack
Of course it also depends on what you’re building: if it’s simple you could go for old school technologies like jQuery and <script> tags. All those things will still work in 10-15 years time. (generally functionalities are only added to the web, not removed, which means websites from the 90’s should still work on modern day browsers)
I’m personally a React developer and I like that over the last couple of years there have been only a few (and very minor) breaking changes. Upgrading React on any project has not caused me any troubles, which is great.
It’s still a cool project though, since it shows exactly how many problems Netlify solves for us
And maybe also the 'you'?
I tried the PWA/offline mode on Safari/iOS but that's not working right now.