Hacker News Reader

Comment by scotth | Hacker News Reader

What was improved with this release?

Here are the commits. Looks like the biggest backwards compatibility issue comes from the "Drop Angular" commit. He also changed the screw_ie8 option to be called ie8 now. A few bug fixes, too, but I'm definitely paraphrasing here.

https://github.com/mishoo/UglifyJS2/compare/v2.8.23...v3.0.0

> He also changed the screw_ie8 option to be called ie8

That's a shame, I always enjoy that silly bit of humour every time I scan my uglify configs!

I totally get why it's safer to not do that sort of thing, nonetheless it does have a certain charm when done sparingly. I wonder if the change was in response to some specific feedback / complaints?

Maybe in Victorian times using the word 'screw' would be considered offensive. The explanation is likely much more inoccuous. Using negative variable names is confusing and leads to programmer errors.

Uglify is a mature and widely-used package. I use it and I love it. It's been years since uglify2, and I was excited to see this.

But... it appears that there are no release notes for version 3, apart from the three negative points at the top of the README: backwards incompatible, twice as slow on the latest Node, and still no ES6 (edit out of the box). No rationale for (or detail of) the breaking change is given. Really bizzare.

Given the (rude and unhelpful) reply from the team, I suppose it was a premature release.

https://github.com/mishoo/UglifyJS2/issues/1875

The issue opener's phrasing was probably why the response was also rude.

While the issue opener is quite brisk and curt, they hardly goes as far as overt rudeness. The blank non-response is astoundingly rude and dismissive in contrast.

Give me a break. The project maintainer is volunteering his time to help the javascript community and is doing a fantastic job fixing dozens of bugs and adding new optimizations and features - often the same day as issues are opened. Rather than nag him, step up and review the commits yourself and make a pull request implementing a ChangeLog.

Exactly. And asking the opener (or somebody in general) to do so would've been a reasonable and polite response.

Unceremoniously closing the ticket on the other hand seems to me to indicate the maintainer really doesn't care.

it now mangles property names.

but still to see if as good as the custom solution we have. it's something we did since early 2000 and save us a good 30% of size. but dangerous as hell.

UglifyJS2 also supports this with the --mangle-props option [1]. Is there something different about how this is done in UglifyJS3?

[1] https://github.com/mishoo/UglifyJS2/blob/master/README.md#us...

Reply on news.ycombinator.com