Deno will stop using TypeScript
This is gonna be an unpopular opinion but as someone who learned to program in loosely typed languages, I have never seen the TS appeal.<p>TS feels like something that was created to lure programmers who couldn’t wrap their heads around JS loose nature. Almost like it was created to convince Java and C# developers to use JS.<p>It have never felt about it like something that would make my code better or more organized. It definitely slows me down with very little benefits in return. (Again, can’t stress enough that this is a personal opinion based on personal use cases)<p>I appreciate that it forces me to be more intentional about organizing my code but I also get that when I use frameworks.<p>Of course I also appreciate when I can identify that an error is coming from
a type mismatch, but as I said I learned to program in loosely typed languages first, so I never created that concept of defining types in my head. I’m always extra-aware of types mismatches in my JS code and is usually the first thing I check when something goes wrong. But I have never felt the need to have a way to explicitly define the types that I’m working with. I honestly fail to see the benefit when a large amount of code that you have to interact with (libraries and such) was written in classic JS.<p>Once again. Probably unpopular opinion, so I don’t mind the downvotes.