{"action":"created","issue":{"url":"https://api.github.com/repos/mishoo/UglifyJS2/issues/1181","repository_url":"https://api.github.com/repos/mishoo/UglifyJS2","labels_url":"https://api.github.com/repos/mishoo/UglifyJS2/issues/1181/labels{/name}","comments_url":"https://api.github.com/repos/mishoo/UglifyJS2/issues/1181/comments","events_url":"https://api.github.com/repos/mishoo/UglifyJS2/issues/1181/events","html_url":"https://github.com/mishoo/UglifyJS2/issues/1181","id":163261011,"number":1181,"title":"[Discussion] Future of uglifyjs","user":{"login":"avdg","id":212248,"avatar_url":"https://avatars.githubusercontent.com/u/212248?v=3","gravatar_id":"","url":"https://api.github.com/users/avdg","html_url":"https://github.com/avdg","followers_url":"https://api.github.com/users/avdg/followers","following_url":"https://api.github.com/users/avdg/following{/other_user}","gists_url":"https://api.github.com/users/avdg/gists{/gist_id}","starred_url":"https://api.github.com/users/avdg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/avdg/subscriptions","organizations_url":"https://api.github.com/users/avdg/orgs","repos_url":"https://api.github.com/users/avdg/repos","events_url":"https://api.github.com/users/avdg/events{/privacy}","received_events_url":"https://api.github.com/users/avdg/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":18,"created_at":"2016-06-30T20:34:56Z","updated_at":"2017-01-21T15:50:25Z","closed_at":null,"body":"tldr; This project got quite big and many people rely on this project to exist. However a project requires maintenance as ecmascript (which javascript is based on) evolves and users are stoking developers with requests of new features, changes and bug fixes.\n\nThe question to be asked is \"How can we guarantee a well established code base/future for UglifyJS\".\n"},"comment":{"url":"https://api.github.com/repos/mishoo/UglifyJS2/issues/comments/274269490","html_url":"https://github.com/mishoo/UglifyJS2/issues/1181#issuecomment-274269490","issue_url":"https://api.github.com/repos/mishoo/UglifyJS2/issues/1181","id":274269490,"user":{"login":"hzoo","id":588473,"avatar_url":"https://avatars.githubusercontent.com/u/588473?v=3","gravatar_id":"","url":"https://api.github.com/users/hzoo","html_url":"https://github.com/hzoo","followers_url":"https://api.github.com/users/hzoo/followers","following_url":"https://api.github.com/users/hzoo/following{/other_user}","gists_url":"https://api.github.com/users/hzoo/gists{/gist_id}","starred_url":"https://api.github.com/users/hzoo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hzoo/subscriptions","organizations_url":"https://api.github.com/users/hzoo/orgs","repos_url":"https://api.github.com/users/hzoo/repos","events_url":"https://api.github.com/users/hzoo/events{/privacy}","received_events_url":"https://api.github.com/users/hzoo/received_events","type":"User","site_admin":false},"created_at":"2017-01-21T15:50:25Z","updated_at":"2017-01-21T15:50:25Z","body":"Copying from https://github.com/mishoo/UglifyJS2/issues/1411#issuecomment-274268946\r\n\r\nJust a thought for the future: I was thinking maybe UglifyJS and Babili (babel-minify) could merge? We can discuss elsewhere too (or in a different thread) if that's more comfortable. I would say it would be easier to maintain UglifyJS 2 and then for the future UglifyJS 3 it could just be Babili? We'll have to talk about all that though but just an idea I thought of.\r\n\r\nRight now the Babili team is also very small: @kangax/@boopathi and me (only sometimes since I have trouble maintaining Babel in general) so we are also looking for help. And the whole Babel team is supporting it indirectly via improving Babel itself. But yeah, maybe it could be an opportunity to combine forces?\r\n\r\nReasoning: Given Babili is a babel-preset, it should support all ES2015+ features moving forward. This means that uglify won't need to focus on making it's on parser support every new syntax, and with Babylon hopefully outputting estree output again (this may take a while but is possible and we are willing to do it) we can all share the same AST format. Babel is used to transform ES2015+ to ES5, etc and so a minifier is a reasonable task to take on as well.\r\n\r\nEDIT: And of course just combining forces and adding like 2-3 more people to the team isn't going to mean it's sustainable, just a way to interop better. We would still need a lot more contributors/maintainers going forward. Babel itself isn't sponsored or has full-time people either. I'm just hoping that this being something developers and companies really need will cause someone to help and do something.\r\n\r\nSpecifically via https://github.com/babel/babel-preset-env it will make it easy for developers to want to compile down to ES6 and above syntax if there target browsers support it natively. Thus you would want to use a minifier that understands all JS. It's in the interest of companies, web browsers, etc as well."}}
{"actor":{"display_login":"hzoo"}}