DEV Community

Kalpesh Mange
Kalpesh Mange

Posted on

4

How do you choose between "cutting-edge" and "bleeding-edge"?

At work, we're transforming our website into a very good webapp. Trying.
To qualify as a real install-able progressive webapp, Google Lighthouse requires us to score a 100% on their test.

The only thing we're missing out on is the caching technique. I'm old fashioned. I like sw-precache and sw-toolbox. They're old. They've been around for a while and lot of folks are using it. Google backed.

I'm also very enthusiastic and curious. I like workbox too. It's very new. Google is backing it too.

Now, I remember someone telling me (master Oogway style):

Be a cutting edge developer.
Not a bleeding edge developer.

Can people please shed some light over this? How should we go about it?

All/Any help appreciated. 🙌
#firstPostOnDevTo #finally

AWS Q Developer image

Your AI Code Assistant

Automate your code reviews. Catch bugs before your coworkers. Fix security issues in your code. Built to handle large projects, Amazon Q Developer works alongside you from idea to production code.

Get started free in your IDE

Top comments (0)

Postmark Image

Speedy emails, satisfied customers

Are delayed transactional emails costing you user satisfaction? Postmark delivers your emails almost instantly, keeping your customers happy and connected.

Sign up

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay