TypeScript's Next Release Is Wild

Correct me if i am wrong but, weren't this supposed to be just training wheels for newbiesJsDevs? You like putting turbochargers on tricycles of kids now?

I never understood the need of it. But then I began with C.. 😂😂 in 2007.. so maybe im wrong

"If you're as fun at parties as we are" Thats was the most amazing line ever and it made my day

A lot of stuff that I don't want to use because my code should be accessible to beginner/moderate developers. I don't want to complicate things to much. Some complex rxjs, weird reduce statements, generics with little keyof extends Omit, but don't go too obscure.

The "reduce" thing is weird. Reduce is nothing great, nothing special, nothing terrible. It's part of an extremely common pattern and technique "Map-Reduce". That's like taking a cheap shot at the division operator...

1

When typescript will be a finished product? They always fix bugs.

Dude let your natural hair color grow. Imho, it's time to move on 😅

yes, very wild and not clickbait at all 👍

I think TypeScript doing linter stuff is not a good direction. Why do we want to mix the type checker and the linter, these are two different things. In practice the most annoying thing about this, is during development or when you debug stuff, you don't necessarily want to immediately write fully correct code. This would not be an issue, because you just turn off the linter in these phases of development. But you need to run the TypeScript compiler, and if that throws linter errors, it's more inconvenient to disable certain checks.

Nice additions and changes!
But are they WILD ? Not even close.
What is wild here, is the continuous clickbait practices seen all over the place.
No offense, I'm just sick of this strategies to catch people's attention, and get some extra monetization.
I find it very disrespectul.

In our college days, i had a friend who used to sit in the corner of tea shop, watched carefully every person and passing comment like - ohh my god 😮 she looks so gorgeous❤, he is very dirty today, his shirt is so silky and so on...


I found most of the video like that.

I'd rather typescript allow us to do a typeof on the variable we're typing and pass it as a generic to that than care about have typescript pretend to be eslint.

"Thankfully, I don't write regex. I don't get paid enough for that." So true blud.

I'm glad to see stuff I used in Groovy (and Java) coming to Typescript.

TIL about those iterator helpers. I love generators. I used them a lot in Python. But I haven't been able to use them comfortably in JS

So we can finally update to Typescript 3.4

Typescript seems more and more like a hellscape. Why would anyone be happy about so much complexity, especially when consistency is already lacking.

For of pattern? It's just a loop, a foreach loop as it is called in normal languages.

I like reduce, I use reduce, reduce is just fold by another name from other languages.

Did you just turn your nose up at regex? IMO, the better programmers are the ones that conquer regex 🔍👀

Riveting content as always. Best every i would say. Also your expressions, top notch. Everyone else should just give up and let you read everything.

if typscript have --nocheck. Why didn't we write .js instead. That's pure --nocheck. Pretty redundant to me.

All i want in typescript is full workspace diagnostics 🥲

you're the porter robinson of web dev

Every title on this channel: this release is wild (no sorry its not)

lol. %#@! typescript for BuiltinIterator.

These updates are neat... sure, but I don't really see how these methods solve the plethora of issues with using TypeScript.


All they seem to do is add unnecessary complexity to an already perplexing ecosystem filled with syntactical nuances.

I really want Rust macros in TypeScript

My beef with many TS releases over the years surround the cognitive load they incur - more syntax and language semantics to be able to model types in existing libraries in the ecosystem. Releases like this - which just make the experience better without requiring that consumers of the language learn new concepts - make me smile!

I'm a C# dev by trade, with background in many older languages (BASIC, Pascal, Fortran, etc).. I work mostly on enterprise software, and only occasionally do web apps. I know enough JS and jQuery to be able build a pretty complex web app by myself (for example a quote entry system, with many product configurators, with everything integrated into an ERP on the backend). I consider myself a full stack dev.

I just do not see the point of TypeScript. I mean I understand how it's better than JS, but since I already know JS, I don't see the point of learning and using typescript. It's just a language extension. Everything get transpiled to JS anyway. I mean sure, you get the benefits of stronger typing, some bells and whistles that make writing JS less painful... But let's be honest, most of it is jQuery event handlers or tiny UI functions anyway, and my back end is in C#... What does TypeScript really do that couldn't be done by a syntax checking IDE for JS with good heuristics? I hear you types (pun intended) complain about useless abstraction all the time, how is typescript NOT just an abstraction layer for JS?

TS is that weird uncle which touches your kids wrongly. ugh.... next, it will be called "Internet Explorer"

Typescript solving things that are not problems to create more problems is problematic. ‘Simple things are hard to create’ is a true statement.

C# Linq finally coming to Typescript, thank you microsoft ;-)

I feel like if you code TS then these are issues, if you code JS these are skill issues, weird mistakes cos you're not thinking and expecting a superset to save you... its Superman, maaaaaan

tsc --noEmit --noCheck 💀

Emoji variable names? You sicko!😅

why in the name of 79 archdevils of hell would you want to use emojis as variables

--noCheck with --watch is going to be big for DX in private monorepos

Last

The generator will not create a new value every time you call it, it creates an iterator once and then you iterate over that iterator

I'm super excited about this. Even just the `x.entries()` instead of `Object.entries(x)` syntax is going to be great.

Wow this is such a QoL update, will try out soon

first? 😀

First