After 20 years of writing JavaScript, I've seen many changes - from callback hell to async/await. But the upcoming JavaScript features will transfo...
For further actions, you may consider blocking this person and/or reporting abuse
Another great article, Max! Thanks for sharing!
Love the new pipeline operator
(|>)- the code looks so clean!we're moving parts of the codebase to use it now. it's great!
Cool 😎 👌
I don't think i agree with the pipeline operator being as useful however, or maybe i just have an issue with the example as it seems very apples to oranges. It's displayed that it's an alternative to a set of nested functions but tbh if i was creating functions to be chained ( like how Arrays have ). I would just do this:
and i would then argue that just having
User(ourUser).enrichUserProfile().normalizeData().validateUser(). saveToDatabase()Is nicer than a
|>between each method, and needing to polyfill for earlier versions.In case of a class build composition, you can't use other methods in the build chain, but with pipeline - you can.
Been writing elixir for 6 months and these are all things I was thinking “wow, this would be cool if I could do in JS”. So cool to see the proposals coming down the pipe (pun not intended but appreciated)
I live that Temporal is finally becoming a thing. Though it doesn't feel right to call the article "upcoming" when it's talking about some proposals that are in stage 2 and 1 and were in that stage last time I checked ages ago. I'd really like to see some progress to be excited about, like Temporal, them an article would be exciting.
This was packed with so many practical examples, love it! For me, the pipeline operator is a total game changer for making workflows readable, but pattern matching is right up there too. Have you run into any gotchas using the Babel plugin in bigger projects?
Really nice article! I learnt some new tricks.
to me I think the gold star is Temporal API
I'm not sold on the pipeline operator, I'm on the fence about it, I kinda like the indentation of nested functions to visualise whats going on; and I think often it might be a code smell hint to refactor to async await promises if your code becomes nested like that. 🤷♂️
I'm pretty sure the pipeline operator proposal has moved to a slightly different syntax with a placeholder symbol (like Hack) instead of these needing unary functions (like F#), so that it could play better with async/await among other things
Pretty cool seeing JavaScript finally fix a lot of old headaches - kinda pumped to mess with some of this now tbh.
When all languages try to transition to js syntax, js wants to adopt PHP syntax??
do you mean pipeline operator? it is not from PHP, F# was the first use it
Really great post!!
Great post!
Luxon is nice! Moment.js is still in lots of codebases though.
excited for new features
really good article mate👍🧡
Hey thanks for this....
Highly recommended!!!
Upcoming ? When ? It's in phase 1 from 5y...
Good writeup ... "upcoming" features - when, which ES version? Are all these proposals already 'final'? Would you 'really' recommend using these (with polyfills etc) 'in production'?
wake me up, when this could be used without all those polyfills :)
Great article, Max 😁👍
I am so happy the Temporal API has finally landed.
The pipeline operator also looks very cool too.
Soon we won’t need to use frameworks anymore 😉
I also like the vanilla decorators as well. Which indeed at some point you won't need frameworks anymore. Or ideally the framework you are using is just using the native js solutions. So the framework won't need the slug it currently need to achieve the same functionality.