Basically reactifying JS? I’ve found it very hard to read react code and find out where an event / signal comes from. Somewhere, something changes and at some other place it has an effect. Probably because I abandoned JS a long time ago, I’m not up to date on the advantages of react, but JS nowadays has never been harder to read.
The problem is that browsers all decided to solve problems differently, then nodejs came along with ideas that browsers couldn’t implement easily (modules for example). To get around that, people wrote “polyfills” but each polyfill did it differently again. So, javascript builders were introduced that automatically inserted polyfills or rewrote javascript code to work on the server and in the browser and they had different solutions.
Of course browsers work differently and have different features, so libraries specialised in exploiting those differences came up and became popular.
Now in an effort to reduce differences, the “best” solutions (aka the most widely used which of course doesn’t mean best) are being integrated into the language. Promises, modules, String functions, classes, typing, etc.
It was a grand mess long ago and it seems to continue to be that way.
Ha. Like I said, there’s a reason I straight up quit trying to learn JS. I see other devs working in it and I’m just over here like “what the fuck is that sorcery?”
No, not reactifying JS. That’s not the intent of this as I interpret it. Take a moment to read through the whole thing and I’m sure any fears you have about this should go away. This is mainly for framework authors, rather than application developers. A standardized and optimized way to code reactivity, reducing framework bundle size, reducing bugs, among other things, no need for weird hooks or Proxy objects and things like that. Good stuff.
Basically reactifying JS? I’ve found it very hard to read react code and find out where an event / signal comes from. Somewhere, something changes and at some other place it has an effect. Probably because I abandoned JS a long time ago, I’m not up to date on the advantages of react, but JS nowadays has never been harder to read.
CC BY-NC-SA 4.0
JS just feels like anarchy to me with how certain events/methods work.
*whispers* because it is
Okay glad I’m not insane. I gave up trying to learn JS because of that.
The problem is that browsers all decided to solve problems differently, then nodejs came along with ideas that browsers couldn’t implement easily (modules for example). To get around that, people wrote “polyfills” but each polyfill did it differently again. So, javascript builders were introduced that automatically inserted polyfills or rewrote javascript code to work on the server and in the browser and they had different solutions.
Of course browsers work differently and have different features, so libraries specialised in exploiting those differences came up and became popular.
Now in an effort to reduce differences, the “best” solutions (aka the most widely used which of course doesn’t mean best) are being integrated into the language. Promises, modules, String functions, classes, typing, etc.
It was a grand mess long ago and it seems to continue to be that way.
CC BY-NC-SA 4.0
Jesus fucking christ…sounds difficult enough. I’ve literally had an easier time learning Mandarin.
I’d rather learn mandarin too than get up to speed with JS 😂
Ha. Like I said, there’s a reason I straight up quit trying to learn JS. I see other devs working in it and I’m just over here like “what the fuck is that sorcery?”
@SatouKazuma @onlinepersona
Just read The Good Parts. No really, There’s a book called JavaScript: The Good Parts and its still the foundational text of the language.
No, not reactifying JS. That’s not the intent of this as I interpret it. Take a moment to read through the whole thing and I’m sure any fears you have about this should go away. This is mainly for framework authors, rather than application developers. A standardized and optimized way to code reactivity, reducing framework bundle size, reducing bugs, among other things, no need for weird hooks or Proxy objects and things like that. Good stuff.
Maybe even one day React will have property support.