DEV Community

Discussion on: Odi - server-side framework

Collapse
 
dantsk profile image
Dan T.

Hi! Thanks for your question. Loopback got a design like Nestjs, Ts.Ed, Routing-controllers. Shortly, differences between Odi and Nestjs are similar to differences between Odi and Loopback :)

Contributing will fail, as design goals of loopback is not completable with Odi goals.

Collapse
 
gregra81 profile image
Greg Rashkevitch • Edited

Well, from taking a closer at Odi and at Loopback 4, I see only advantages in Loopback 4.

  • Regarding routing - it works very similar with decorators (Odi has decorators in the controller)
  • Regarding DI - Loopback does it explicitly, like any other framework I know (like Spring), Odi does too much magic - harder to debug (and test?)
  • Regarding all the future features you plan to develop - these exist today in Loopback 4
  • Also, Loopback has an LTS support and it's backed by IBM with people that are getting paid just to maintain and support the framework

In summary - I do not see any reason to take risks and go for a new framework that has only disadvantages over Loopback 4
Take my word for it and consider moving to Loopback 4 and contributing (or any other NodeJS framework)

Thread Thread
 
dantsk profile image
Dan T.

It’s defenitily good arguments. But we have interesting things to show in the future that will differentiate odi from loopback. Anyway, it’s great to have a choice between technologies.