3 ms·

Replying at all and in such a passive aggressive tone is petty. If you're confident in your technology (and people making something as widely used as react/redu

Replying at all and in such a passive aggressive tone is petty. If you're confident in your technology (and people making something as widely used as react/redux ought to be confident), you can let it speak for itself. As for how much this actually set the record straight or how much the original post was false information, I guess I'll have to disagree. Nothing in the original post was false per se, and I, for one, agreed with everything in it, every time I've tried to get into react since it was launched and it's always the same annoyances. It's just not for me and it's not for the author of the original post. Two different points in OP's reply were "well yeah, but it'll be different in the next version/future!" (amusingly, another point was "well, just don't use the new version!") which means that the original post was... right.

Sacho 9y ago
> Nothing in the original post was false per se, You mean besides: "I started my app with React 15.5.0 knowing that my code is deprecate before even starting" (addressed by dan) "in mobx you can prefix your store actions but “it’s just for the glam” because it won’t preserve overriding any observable property of your store as it was a normal object store.message = ‘hello’ from any component of your application!?!" (strict mode, right there on the page he even links to) "React-router is not officially maintained by facebook and the maintainers had the great idea of bumping 3 major versions in 5 months completely not backward compatible to each other" (in the link he provides, you can see version 4 was released 03.2017, version 3 was released 10.2016, version 2 was released 02.2016. Even a charitable reading of "bumping 3 major versions" doesn't get you to 5 months) I could only find one more assertion of fact, rather than opinion, which happens to be right: "Once I understood what was the issue I was dragged into the rabbit hole being forced to add empty divs all over the place to let my app work properly" However, it's also fixed in the next release.
- julianmarq 9y ago
  > "I started my app with React 15.5.0 knowing that my code is deprecate before even starting" (addressed by dan) If you buy into the fairy tale that a complete rewrite isn't going to break anything, all the power to you. I don't, and have no reason to, I've experienced it first hand what such a major change causes. So, not incorrect. > "in mobx you can prefix your store actions but “it’s just for the glam” because it won’t preserve overriding any observable property of your store as it was a normal object store.message = ‘hello’ from any component of your application!?!" (strict mode, right there on the page he even links to) So... it is possible but not when done a certain way? How that does make the point false? "well duh, you're using react wrong!" doesn't help react and doesn't address the criticism. If it allows to do something, it does, and so it can be used to make bad code, which is where every criticism of every language/framework ever originates; none of it invalid. That's just things one learns to live with, none of the tools we use is perfect. > "React-router is not officially maintained by facebook and the maintainers had the great idea of bumping 3 major versions in 5 months completely not backward compatible to each other" (in the link he provides, you can see version 4 was released 03.2017, version 3 was released 10.2016, version 2 was released 02.2016. Even a charitable reading of "bumping 3 major versions" doesn't get you to 5 months) ... Except it does? At the start of October, the official version was 2; at the end of March, it was 4. That's three different versions in five months. I gotta thank you for this one, because it precisely requires a very charitable reading of that. And even a strict reading gives us two major versions in five months, hardly all that much better.

Sacho 9y ago

> Nothing in the original post was false per se, You mean besides: "I started my app with React 15.5.0 knowing that my code is deprecate before even starting" (addressed by dan) "in mobx you can prefix your store actions but “it’s just for the glam” because it won’t preserve overriding any observable property of your store as it was a normal object store.message = ‘hello’ from any component of your application!?!" (strict mode, right there on the page he even links to) "React-router is not officially maintained by facebook and the maintainers had the great idea of bumping 3 major versions in 5 months completely not backward compatible to each other" (in the link he provides, you can see version 4 was released 03.2017, version 3 was released 10.2016, version 2 was released 02.2016. Even a charitable reading of "bumping 3 major versions" doesn't get you to 5 months) I could only find one more assertion of fact, rather than opinion, which happens to be right: "Once I understood what was the issue I was dragged into the rabbit hole being forced to add empty divs all over the place to let my app work properly" However, it's also fixed in the next release.

julianmarq 9y ago
> "I started my app with React 15.5.0 knowing that my code is deprecate before even starting" (addressed by dan) If you buy into the fairy tale that a complete rewrite isn't going to break anything, all the power to you. I don't, and have no reason to, I've experienced it first hand what such a major change causes. So, not incorrect. > "in mobx you can prefix your store actions but “it’s just for the glam” because it won’t preserve overriding any observable property of your store as it was a normal object store.message = ‘hello’ from any component of your application!?!" (strict mode, right there on the page he even links to) So... it is possible but not when done a certain way? How that does make the point false? "well duh, you're using react wrong!" doesn't help react and doesn't address the criticism. If it allows to do something, it does, and so it can be used to make bad code, which is where every criticism of every language/framework ever originates; none of it invalid. That's just things one learns to live with, none of the tools we use is perfect. > "React-router is not officially maintained by facebook and the maintainers had the great idea of bumping 3 major versions in 5 months completely not backward compatible to each other" (in the link he provides, you can see version 4 was released 03.2017, version 3 was released 10.2016, version 2 was released 02.2016. Even a charitable reading of "bumping 3 major versions" doesn't get you to 5 months) ... Except it does? At the start of October, the official version was 2; at the end of March, it was 4. That's three different versions in five months. I gotta thank you for this one, because it precisely requires a very charitable reading of that. And even a strict reading gives us two major versions in five months, hardly all that much better.