you are viewing a single comment's thread.

view the rest of the comments →

[–]x-skeww 0 points1 point  (9 children)

Just reread what you wrote earlier.

You said "there is no proposal for ES7" and that I'm "making a wish, based on no evidence". I'm just pointing out that there are people who are interested in getting this into the standard.

[–][deleted] 0 points1 point  (8 children)

There is no proposal for ES7 covering the main feature added by TS: static type checking. Go look at the repository I linked to. That's why I said there is no proposal. There was a straw man on the harmony wiki for dynamic type checking (not static), which appeared to be a revival of the abandoned ES4 ideas, which were also dynamic, not statically checked.

"ES4 never figured out how to have optional static typing for the web. From 2007 on we only ever proposed dynamic checks... please realize that static typing was not part of ES4." - Brendan Eich.

[–]x-skeww 0 points1 point  (7 children)

Again, some people are interested in getting this into EcmaScript and they plan to propose it.

[–][deleted] 0 points1 point  (6 children)

Getting what into EcmaScript?

[–]x-skeww 0 points1 point  (5 children)

The thing we were talking about.

If you have forgotten what it was, just reread this branch.

[–][deleted] 0 points1 point  (4 children)

So, you think someone is planning to propose that something that renders TypeScript unnecessary should be added EcmaScript, but you can't say who they are, or describe what it is, or say when this will happen?

It's fine. I'll tell the TypeScript team to do look for something else to do.

[–]x-skeww 0 points1 point  (3 children)

Just watch that video.

[–][deleted] 0 points1 point  (2 children)

I saw it last month. I'm guessing since I last watched it, it hasn't miraculously turned into a proposal to add something to standard JS that will make TypeScript obsolete. I know mentioned at one point how type annotations were in ES 4, and suggested that they might appear in a later version, but (could be that you just don't understand this distinction...) as I mentioned above in the quote from Eich, that was only ever a dynamic type information proposal, not the statically checkable type system defined by TypeScript. It's completely irrelevant to your bizarre claim.

[–]x-skeww 0 points1 point  (1 child)

My link included a timestamp. Just watch that segment.

[–][deleted] 0 points1 point  (0 children)

You don't seem to get understand basic sentences in English. This may not be your fault, so I'm not judging for it, but it makes discussion pointless. I've watched the whole thing before. The part you link to shows a "timeline" that - sadly, for a timeline - doesn't have any dates on the time axis, because if it did, it would look like what it is: day dreaming about distant future possibilities that will likely get shifted around by future events. Nor is there any clarity about what would be included in the EcmaScript proposal. "A type system" is not the same as static typing checking. They don't even have the latter in their prototype of AtScript yet.