4:01 AM
@TomJNowell, I didn't say that the people working on the standard are idiots. good features are good features, but the need to get to the point were all 3 browsers agree to implement them otherwise the most basic requirement fron the language - browser inter comparability will be broken. This do not mean that JS do not evolve, it means that it evolves slower than PHP that need only a majority vote for adding new features.
As for angular, this is what happened and there was a huge cry about that. Probably part of why some people prefer react now. I do not have an idea about the internal details, but the switch required rewrite
As for supporting old versions.... seriously, neither google nor almost anyone else in tech (maybe microsoft is an exception) have a BC policy that comes even close o the WP one.
the half life of a JS framework is two years and after it starts to decline good luck finding any support
IIRC one of the SE posts claimed that even jquery is on decline, at least when you analyz the questions here
As for HHVM, there might be people still interested that add PRs, but the major development was done by FB. without the money put into it by them the project is on a sure decline.
And the same will happen with react. Once FB will lose interest it will be less maintained, no new features etc
Maybe I should say what I said before in a different way. Using any of the JS frameworks adds a dependency and neither of the maintainers showed the will to keep software projects fully running when they lose interest. So unless you can afford switching frameworks when the time will come, you better avoid the thing in the first place
4:34 AM
as for hhvm in a true display of how big companies just don't care it deprecated supoort for php - hhvm.com/blog/2017/09/18/the-future-of-hhvm.html "last HHVM release that commits to PHP5 support" and "HHVM will not aim to target PHP7"
12 hours later…
4:31 PM
@MarkKaplun but they do, and they name the standards, hence ES2015 ES2016 ES2017 etc, so you can transpile into the target standard. Babel changed how it works too since some ES2015 and ES2016 features are widespread now, so that rather than setting ES2015 as a target, you tell it what browsers you intend to support and it figures out what needs transpiling, if anything does
> As for angular, this is what happened and there was a huge cry about that. Probably part of why some people prefer react now. I do not have an idea about the internal details, but the switch required rewrite
That's because Angular 2.0.0 was a new framework, they use semver, and by incrementing it was a major change. Same thing happened with Symfony 2, etc, it's just semver. Angular 2 was not meant to be an update to v1, and v1 wasn't abandoned. Rather the community jumped on the Angular 2 bandwagon and the Angular 1 community shrank fast as a result
That's because Angular 2.0.0 was a new framework, they use semver, and by incrementing it was a major change. Same thing happened with Symfony 2, etc, it's just semver. Angular 2 was not meant to be an update to v1, and v1 wasn't abandoned. Rather the community jumped on the Angular 2 bandwagon and the Angular 1 community shrank fast as a result
5:09 PM
@TomJNowell, those are selective statistics about the rate of JS change. before that there was almost no change for very long years. It is not surprising when you take into account that only one of the major browsers companies have major web assets. For years before that microsoft just didn't play ball and nothing did change.
as for angular... if the difference is big enough does it make any real difference if this is a semver or just a total new language? You can see that with PHP, moving from major version to another can be painful, but than there is a deprecation mechanism in place to smooth it out, and you do not wake up one sunny day to discover, with no prior warning, that you need to rewrite your code ASAP if you still want to enjoy the goodies of the framework
as for jquery I meant this post - stackoverflow.blog/2018/01/11/…. The amount of questions regarding it is declining
« first day (2689 days earlier) ← previous day next day → last day (2270 days later) »
