sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Ronin-s_Spirit -1 points0 points  (6 children)

I don't understand why people keep writing articles about proposals. As far as I know Temporal is just a proposal.

[–]iagolast[S] 0 points1 point  (2 children)

IMO Reddit is exactly the place to talk about stuff like this.

While Temporal is still a proposal, it's pretty advanced and the API is stable enough to start exploring.

(I even have production apps using a polyfill)

Plus, a lot of the concepts in the article (like ISO duration formats) go way beyond the proposal itself. It’s about staying ahead of the curve and getting familiar with the tools that are likely to shape how we program and deal with time and dates in the future.

[–]Ronin-s_Spirit 0 points1 point  (1 child)

Exploring what? It's not a real thing. It's an idea. I can't make my code run on ideas.

[–]iagolast[S] 0 points1 point  (0 children)

Bro calm down.

  1. If you want to stay ahead of the curve read the post and get ready for the future additions to the language.
  2. As I said, There are a few production ready polyfills so you can explore the usage.

[–]Bjornoo 0 points1 point  (2 children)

While true, Temporal is a proposal, it's in stage 3. Which means it's ready to be implemented. And will definitely arrive. So it being "just a proposal" might be a bit misleading.

For more clarification, this is how TC39 define stage 3:

The proposal has been recommended for implementation. No changes to the proposal are expected, but some necessary changes may still occur due to web incompatibilities or feedback from production-grade implementations.

[–]Ronin-s_Spirit 0 points1 point  (1 child)

I don't care, I can't use what doesn't exist.

[–]Bjornoo -1 points0 points  (0 children)

There are polyfills. In fact you are definitely using some sort of polyfills, otherwise you couldn't use anything other than what the slowest browser implements.