Re:When to Use TypeScript – A Detailed Guide Through Common ...
by ajxs on Sunday April 07, 2019 @08:36PM
(#19600975)
I've had too many terrible experiences having to maintain and work with buggy and poorly designed Node/Typescript packages. I'm especially thinking of the terrible choice of ORMs available for Node, Typescript in particular. TypeORM seems the de-facto standard and my experiences with it have been horrific. It looks like Hibernate but works like a dumpster fire. There isn't anything as robust as ORMs like EF or Hibernate for Node.
I feel that the shortcomings of the NPM community have been pointed out one too many times, but on too many occasions I've felt that development of a product was made much harder by the choices of poorly developed frameworks as dependencies.
[ Parent
| on HN ]
Re:When to Use TypeScript – A Detailed Guide Through Common ...
by rmrfrmrf on Sunday April 07, 2019 @11:45PM
(#19601840)
FWIW I've helped a team of Java developers transition to Node and the first questions I got were usually about standard library and hibernate. One guy was quite convinced that the NPM world just needed a reimplementation of Apache Commons to see the value in monolithic packages. I also had to do a lot of explanation about strategies for code reuse without inheritance/turning everything into classes.
These are all, at the end of the day, XY-style problems whose suboptimal answers can snowball into unmaintainable code. I do think there is a serious lack of training material in this area, though.
Re:When to Use TypeScript – A Detailed Guide Through Common ...
by slaymaker1907 on Sunday April 07, 2019 @09:47PM
(#19601284)
The ORM was your first mistake. They almost always get in the way and are way more complex than the relatively simple language (SQL) they are intended to abstract over.