2 ms·

> You are contradicting yourself there. There is really no difference in clarity between an automatic path resolver and using aliases. No difference? In case o

> You are contradicting yourself there. There is really no difference in clarity between an automatic path resolver and using aliases. No difference? In case of explicit importing you get the "import" thing in the sources code and it's a huge difference in comparison of not having it there. > It's really a matter of taste. Not really, but a matter of separation of concern and good design. Besides Vue is a reactive thing, and such structure I guess makes it easy to apply reactivity observers where they are needed in a more explicit way.

pier25 9y ago
> No difference? If you are using aliases you are not using explicit imports. import something from 'something'; Where does 'something' come from? No idea unless you peek at the webpack configuration file. You don't even know if the module is actually called 'something'. > Not really, but a matter of separation of concern and good design. Then I'm guessing you consider all OOP languages badly designed since none of them have properties for 'methods', 'getters' (computed), etc. Yes?
- vladimir-y 9y ago
  > If you are using aliases you are not using explicit imports. You are as you have the "import" code line in the code sources. If you get rid of that code line, you make it happen implicitly and this is the case of undesirable "magic" happening. > No idea unless you peek at the webpack configuration file. Some IDEs do support automatic Webpack's aliases resolving, so you can navigate to the module by ctrl+click. > Then I'm guessing you consider all OOP languages badly designed since none of them have properties for 'methods', 'getters' (computed), etc. Yes? Don't be silly, we are talking about JS that has a room for adding some structure as it's being too flexible by default. Anyway thanks for the Youtube link, it helped me to realize that I'm not going to use this Marko thing.

pier25 9y ago

> No difference? If you are using aliases you are not using explicit imports. import something from 'something'; Where does 'something' come from? No idea unless you peek at the webpack configuration file. You don't even know if the module is actually called 'something'. > Not really, but a matter of separation of concern and good design. Then I'm guessing you consider all OOP languages badly designed since none of them have properties for 'methods', 'getters' (computed), etc. Yes?

vladimir-y 9y ago
> If you are using aliases you are not using explicit imports. You are as you have the "import" code line in the code sources. If you get rid of that code line, you make it happen implicitly and this is the case of undesirable "magic" happening. > No idea unless you peek at the webpack configuration file. Some IDEs do support automatic Webpack's aliases resolving, so you can navigate to the module by ctrl+click. > Then I'm guessing you consider all OOP languages badly designed since none of them have properties for 'methods', 'getters' (computed), etc. Yes? Don't be silly, we are talking about JS that has a room for adding some structure as it's being too flexible by default. Anyway thanks for the Youtube link, it helped me to realize that I'm not going to use this Marko thing.