2 ms·

I have it, and it's quite good. I believe you'll change your opinion once you actually get a chance to use it in a real project. For example, I was able to have

I have it, and it's quite good. I believe you'll change your opinion once you actually get a chance to use it in a real project. For example, I was able to have it write a bunch of boilerplate for me for converting a database query into their proper TypeScript types. I could have done that manually but it's, well, called boilerplate for a reason. It also helped me learn new features or ways to do certain actions. One such case was how it used immutable data structures to represent a change rather than mutating. Think `arr = [...arr, newElement]` rather than `arr.append(newElement)` which is not exactly the code I was writing but simply an example.

omnicognate 5y ago
I have an open mind, and if I find it a useful tool I'll adopt it enthusiastically. However I remain skeptical for the reason I said. The positive comments I read from people who've tried it give examples of things it's done right, effort saved, things learned, but make no mention of the effort taken to verify what it produces. I don't know if that's because they're uncritically accepting what it produces (which would be bad), because it's only usefully producing trivial bits of code (which would put it in a race against how fast I can type, handicapped by whatever percentage of the time it gets it wrong and the time taken for me to check) or because I am somehow unusual in finding reading code much, much harder than writing it. I'm getting pretty frustrated with the limited access. I signed up months ago. Just release it already.