3 ms·

A fundamental feature I look for in frameworks is an easily accessible "off-ramp". Is it possible to wean yourself away from the dependency? While many front-pa

A fundamental feature I look for in frameworks is an easily accessible "off-ramp". Is it possible to wean yourself away from the dependency? While many front-pages of frameworks tout how easy it is to adopt incrementally, my concern is about incrementally escaping. Not because I necessarily will, but because it is a good sign of underlying quality and it is always good to have the option.

divbzero 6y ago
In my judgment, React scores poorly on “off-ramp” potential as there is a particular React way of doing things. Curious if others would agree, and also for assessments on which frameworks score better on “off-ramp” potential.
- runawaybottle 6y ago
  Which is very weird because it was supposed to just be the view layer.
  - oorza 6y ago
    It is just the view layer in well architected applications. The off-ramp for a React application is use your state management, data models, controllers, etc. with a different view layer. Oh, you're making HTTP calls directly in React components? Well, you done goofed and that's not React's fault.
    - runawaybottle 6y ago
      What if you used a bunch of scoped styles in your component? Screwed yourself there again? Would be nice to have a style sheet to just slap onto that whole other framework ...
      - unclebucknasty 6y ago
        I haven't wrapped my mind around scoped styles. You generally want a consistent UI, meaning mostly global CSS. And, you want the option of easily adjusting a global aesthetic/behavior. Scoped styles seem like the framework version of the style attribute.