3 ms·
This looks really interesting. The possibility to define runtime types basically removes the need to write data object validation blocks, greatly alleviates dat
by stareatgoats 4y ago
This looks really interesting. The possibility to define runtime types basically removes the need to write data object validation blocks, greatly alleviates database sync etc. I'm sure I'm not the only one to have implemented runtime types on top of Typescript for this reason, albeit not at this low level and therefore incurring a certain performance penalty.
So performance would be one reason to chose Deepkit for me. The integrated framework looks interesting too. Something that make me hesitant is the relative small user base and size of the community (mainly one single developer?) considering this would basically be to commit to a new programming language. And if the Typescript team should decide to do anything similar then the project might be dead in the water?
- ConsoleTVs 4y agoI never understood the "single developer" argument. React itself does not even have more than 5 active developers (https://github.com/facebook/react/graphs/contributors https://github.com/facebook/react/graphs/contributors), Vue literally have a single one (https://github.com/vuejs/vue/graphs/contributors https://github.com/vuejs/vue/graphs/contributors). You can apply this to almost any library. I mean, what's that argument for?
- stareatgoats 4y agoIt means that the project depends on the whims or life events of a single person - a single point of failure if you like: critical patches may not be merged, the maintainer might turn malicious etc. More people on the project means more eyeballs on the code. This seems self-evident to me (especially if the project is core in ones tech stack) so I'm really surprised at the "what's the argument for?". Am I missing something? (I don't see how you can cite Vue as an example; Evan is the main contributor to Vue, but he is certainly not the only one.)