Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Maybe this is what happens when you’ve been coding for years and years but the thing is I was using this particular foot gun and it was working well. I don’t need a framework developer to babysit me and prevent me from misusing a feature. I know when it is a foot gun and I can treat it as such. It sounds like the Vue devs simply removed this feature that was in some ways useful and didn’t replace it with anything better. They removed it because it enabled people to do something they didn’t like, which yes as a maintainer of a popular framework is kind of your responsibility to be help people figure out. But this is like if C removed the ability to dereference pointers because it’s dangerous to do. Of course it’s dangerous, that’s why it’s so powerful. If you can’t use it responsibly, that’s on you, not on the framework developers.

Basically, it’s not like they added a formalized way to create notification buses. They simply removed a useful and widely used feature because they didn’t like how people were using it. This is exactly the kind of shit that killed Angular and honestly makes me reevaluate the trust I’ve placed in Vue. Improvements are always welcome. Wholesale removing useful features without providing an alternative, not so much.



Well, unlike angular, the event bus thing isn't integrated into vue self in any way (and it don't need to). It didn't prevent you from use it if you must need to either.

Moreover, You can polyfill it simply in one line. And it actually exist long before the vue ever exist.

const { EventEmitter } = require('events').

It always make me wonder why was vue ever want to pack this into itself given it did not use it as all.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: