The differences between CoffeeScript and ES6 are much greater than the differences between Jade and HTML. Visually Jade looks radically different but at its core it just removes the <>. It has a couple of neat features around for-loops and whatnot but overall it's just HTML with less typing.
I'm in favor of using Jade because I think it's an improvement over writing AND reading HTML, but I feel CoffeeScript was a stopgap until we could write ES6 easily, so go for ES6.
BEM is another topic entirely so I won't inject my opinion on that one.
I spent a few minutes hacking around with vue-devtools to get something running in Electron. I used a second window and a modified version of the dev shell rather than trying to figure out how to make the real Chrome shell work without content_scripts.
enhance: __component sepecial field is now sortable. Thanks @pauk-slon. Close #80
new: row-detail-component -- row detail should now be implemented as a component. Suggested by @malaschitz. See examples for usage.
deprecated: row-detail-callback -- use row-detail-component instead
Don't forget to checkout many interesting use cases, questions, and answers in the Github Issues as well as the closed ones.
I take a look at the koel project project. @phanan compile all external library css files as vendor.css and all js library files as vendor.js. So I guess if we use vuejs with laravel, we can't import the file and use.
Thanks everyone. I'll stick to they way @phanan did.
Absence of server filtering means that you can't actually ask that table be presented with narrow subset of data? I imagine it's a noob question given all you have to do is just implement an inquiry method and then filter data for presentation, but what is the roadmap idea of it then?
Sorry one more question: if you write a custom directive for use on a textarea or form input, and you use v-model for two-way binding, does this mean you don't need twoWay and set()?
EDIT: I'm confused actually because I'm using jQuery onoff and have written a custom directive for it. It doesn't seem to make a difference to two-way binding if I use use v-model but if I set twoWay: true paradoxically it doesn't work. Setting it to false works even though I'm using .set(). From reading the docs I thought twoWay: true was required to use set().
So I guess I'm just after a bit more of a detailed explanation with regards to custom directives and v-model, set() and twoWay.
EDIT 2: As an example I've tweaked Evan's select2 demo so you can see what I mean. Why in this case does it only worked as expected when twoWay is false?
Before i discovered <script type="text/ecmascript-6"></script> i had a lot but that fixed a lot of them :) The only problem i know of now is the arrow function problem you pointed out. My .eslintrc forces arrow functions so it would be a bit annoying to have a lot of template errors that i can't turn off. Besides that it seems okay!