This is a very confused interpretation of history and the current state of reality. Prompted by this issue, I kindly ask for an executive revision of TypeScript toward the effect of enumerating and prioritizing issues, most of them with a history of so many years, so that its adoption is not hampered by such behaviors that are counterintuitive TypeScript has grown a lot, it'd be useful to take a breath, look back and marvel at the amazing progress, and finally complete the basics for a tight, homogeneous baseline strength, while also reducing many of the pain points in the learning curve of TS, many of them caused by incidental rather than essential complexity, or suboptimal prioritization of solving gaps, an example for which is this one, four years and counting. Prompted by this issue, I kindly ask for an executive revision of TypeScript toward the effect of enumerating and prioritizing issues, most of them with a history of so many years, so that its adoption is not hampered by such behaviors that are counterintuitive and/or One of the biggest is, lack of nominal typing, one can add angles in radians with angles in degrees because number. TypeScript has leapt ahead in many esoteric, rarely used directions, while the basic quilt has gaps. the claim is structural typing, yet extra properties of objects most often fly under the radar (except with literals, an unexpected counterexception within the exception), despite it impacts structure just as much as missing properties do. The decision process around TypeScript evolution comes into question, based on this issue and other issues where TS is also a leaky, non-contiguous abstraction, eg. TypeScript maintaining this gap promotes poor coding practices, because one can't extract and name (sometimes common) constants, which is one of the most basic tools for readable, maintainable and efficient code. Many closely related tools including TS tools themselves already engage in various ways of flow analysis. It's at a point of maturity, being worked on since 2012.
I also believe that for TypeScript to live up to its promise, it needs to bite the bullet and do flow analysis. I agree with the proposal from as a stop gap because it retains almost all the brevity of the original ask by and may address a good part of the objection by that it'd require flow analysis it doesn't appear structurally different to the function case at least when the const is directly used (substitutability). I agree with that the typeof is an even simpler case.
0 kommentar(er)
