{"action":"created","issue":{"url":"https://api.github.com/repos/meteor/blaze/issues/131","repository_url":"https://api.github.com/repos/meteor/blaze","labels_url":"https://api.github.com/repos/meteor/blaze/issues/131/labels{/name}","comments_url":"https://api.github.com/repos/meteor/blaze/issues/131/comments","events_url":"https://api.github.com/repos/meteor/blaze/issues/131/events","html_url":"https://github.com/meteor/blaze/issues/131","id":181187038,"number":131,"title":"Vue as Blaze 2.0","user":{"login":"aadamsx","id":5341158,"avatar_url":"https://avatars.githubusercontent.com/u/5341158?v=3","gravatar_id":"","url":"https://api.github.com/users/aadamsx","html_url":"https://github.com/aadamsx","followers_url":"https://api.github.com/users/aadamsx/followers","following_url":"https://api.github.com/users/aadamsx/following{/other_user}","gists_url":"https://api.github.com/users/aadamsx/gists{/gist_id}","starred_url":"https://api.github.com/users/aadamsx/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aadamsx/subscriptions","organizations_url":"https://api.github.com/users/aadamsx/orgs","repos_url":"https://api.github.com/users/aadamsx/repos","events_url":"https://api.github.com/users/aadamsx/events{/privacy}","received_events_url":"https://api.github.com/users/aadamsx/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/meteor/blaze/labels/discussion","name":"discussion","color":"bfd4f2"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":34,"created_at":"2016-10-05T15:25:38Z","updated_at":"2016-10-19T13:04:33Z","closed_at":null,"body":"Thinking ahead to Blaze 2.0, I think we should be talking about somehow building off of Vue 2.0 https://github.com/meteor/blaze/issues/128#issuecomment-251184658 instead of duplicating efforts or talking ourselves in circles feature after feature, and getting sidetracked or bogged down.\r\n\r\nWe need to be looking at the big picture.  Vue has the momentum in the broader JS community.  Vue has the features we've been asking for and need.  Vue has the performance.  Vue has developers working full time on the project.  Vue has tempting similar to Blaze.  The only thing it's lacking is tight Meteor integration and maybe a sprinkle of Blaze flavor we are use to around these parts.\r\n\r\nI think we should be discussing how to build off Vue with a emphasis on Meteor -- as a \"Blaze 2.0\".\r\n\r\nI think the timing for a move like this is just right:\r\n\r\n* Blaze community driven and looking for change.\r\n\r\n* Meteor classic in a state of transition and flux, open to change.\r\n\r\n* Vue 2.0 just release with a feature set and performance to be envious of.\r\n"},"comment":{"url":"https://api.github.com/repos/meteor/blaze/issues/comments/254806189","html_url":"https://github.com/meteor/blaze/issues/131#issuecomment-254806189","issue_url":"https://api.github.com/repos/meteor/blaze/issues/131","id":254806189,"user":{"login":"priezz","id":6680317,"avatar_url":"https://avatars.githubusercontent.com/u/6680317?v=3","gravatar_id":"","url":"https://api.github.com/users/priezz","html_url":"https://github.com/priezz","followers_url":"https://api.github.com/users/priezz/followers","following_url":"https://api.github.com/users/priezz/following{/other_user}","gists_url":"https://api.github.com/users/priezz/gists{/gist_id}","starred_url":"https://api.github.com/users/priezz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/priezz/subscriptions","organizations_url":"https://api.github.com/users/priezz/orgs","repos_url":"https://api.github.com/users/priezz/repos","events_url":"https://api.github.com/users/priezz/events{/privacy}","received_events_url":"https://api.github.com/users/priezz/received_events","type":"User","site_admin":false},"created_at":"2016-10-19T13:04:33Z","updated_at":"2016-10-19T13:04:33Z","body":"Let me join the discussion :) My first reaction was \"Wow! Cool idea, I should upvote!\". However after some thinking I have understood that I would like to change the subject of this issue to 'Vue 2.0 as Blaze **1**.0'. The wrapping approach and keeping the full API compatibility with Blaze will definitely help to improve the performance of existing projects (for those, who really suffer). So it would be just the same good old Blaze with all it's advantages and disadvantages, but which works faster.\r\n\r\nBut why should we follow this wrapping approach for the \"Blaze Next\"? I agree with @stubailo, if you like Vue, just use Vue. If you like it, but some features are missing (which still exist in Blaze), why not to contribute directly to Vue development, extending its applicability? @msavin have mentioned nice to have features - \"easy to use handlebars, natural HTML in template tags, no special syntax or attributes\". Let's just analyze what is missing, consider is it really necessary for modern Meteor apps (probably the other, already implemented in the Vue approaches could fit better) and if it is add it into the Vue. The MDG marketing machine will do the rest to popularize the transition.\r\n\r\nWhat do you think, guys?"}}
{"actor":{"display_login":"priezz"}}