> The whole thing stinks. Will Rome Tools employees get called out and shamed in public if they don't have enough visibility on their github profile?
I had no idea he had started a competing project. This really stinks, almost like he is sabotaging his competitor.
My eyebrows would be a little raised. Not that I would call them out in a tweet, but I would at least be curious where that guy is spending his time.
It is one thing to raise the issue in private with "Project A", another thing is to tweet this to thousands of followers. Especially after "Project A" already had resolved the issue on its own.
At that point, a huge amount of someone's time is spent managing bug tickets, attempting to isolate debug, etc.
Folks should just develop their own shims where necessary and TEST AGAINST VARIOUS BROWSERS.
Sure no one likes doing that, but it’s important to follow the fast-pace ECMAScript adoption.
I mean, how does that not just push all of this towards companies and open source solutions that provide access to old browsers and what not? I mean no matter what direction you push, it's going to be someone else's open source code that needs money.
I guess what I’m getting at is that most current browsers support very nice JavaScript features anyway. And instead of adding yet another layer between our code and the browser—embrace the current generation of (at this point very robust) language features available.
And if that’s not good enough use something like TypeScript!
Maybe that's true for users in the western world. However, if you are in the asian market, there are popular browsers you've nerver heard of (some localized fork of chromium that's way behind). That is not to mention the poorer populace of the world still uses whatever that runs on WinXP or something, if they have Internet at all.
As software engineers it's not our job to use technology to dictate (control) how people access information, telling them to use newer browsers and newer hardware and what not, our job is to support as many people out there as we can.
In any case, for the plethora of down voters: Babel states: “Use next generation JavaScript, today”
At some point next gen == current gen, and therefor given enough stability, Babel becomes obsolete.
Folks, donate to Mozilla instead they actually move things forward not backward.