3 ms·
This is enough reason for me to completely forget Deno. They clearly cannot write code or organize it without using classes, which is the core of their current
by austincheney 6y ago
This is enough reason for me to completely forget Deno. They clearly cannot write code or organize it without using classes, which is the core of their current error. The fact that they would choose that stupidity over the organizational benefits of interfaces and static types is not something I can reconcile.
- shirshak55 6y agoremember deno is written by same person who wrote node js so please don't judge immediately.
- HideousKojima 6y agoThat's even more reason to disregard it then
- austincheney 6y agoThe technical problem is a class name in their code conflicting with a same named definition in their index.d.ts file closely related to that class. If they stopped using classes or changed those names to not be in collision this problem would be cured, which indicates it’s an edge case in their code they could easily fix but choose not to. Knowing that and that they blame the TS compiler for their code problem is cause enough to be judgemental. Knowing they are aware they could easily fix this issue themselves but are instead dumping TS is cause for hesitation to invest in the project.
- deleted 6y ago[deleted]