๐—™๐—ฟ๐—ฎ๐—บ๐—ฒ๐˜„๐—ผ๐—ฟ๐—ธ๐˜€ ๐—ฅ๐—ผ๐˜. ๐—ง๐—ต๐—ฒ ๐—ฃ๐—น๐—ฎ๐˜๐—ณ๐—ผ๐—ฟ๐—บ ๐——๐—ผ๐—ฒ๐˜€๐—ป'๐˜.

Stop looking at your package.json for answers.

Most developers leave frameworks because of the upgrade treadmill. They hate constant migrations and changing build tools. But there is a deeper reason to move toward the web platform.

Here are four reasons why vanilla JavaScript wins over the long term.

How to switch without the risk:

Do not do a big rewrite. Use the strangler pattern.

  1. Freeze your current framework version to stop the upgrade cycle.
  2. Build all new features as Web Components.
  3. Convert old components one by one when you touch them for features.
  4. Remove the framework shell last.

This approach lets you pause or pivot at any time.

If your app is long-lived and focuses on forms and views, the platform is your best bet. If you are building a real-time collaborative canvas, stick to a framework.

Choose the structure that lowers your long-term costs.

Source: https://dev.to/sebs/frameworks-rot-the-platform-doesnt-58g0