31–34 of 34 posts
In this instance, though, I do feel that the changes weren’t necessary. All API changes come with a cost, and I’m unconvinced that the benefits outweighed it this time round.
Earlier quoted context omitted.
I am. I wrote a bang-simple extensible blogging system several months ago using Vue. I started very, very simple. I ended up with multi-component files. No vue-cli. Three files. A few hundred lines of code. Works fine. Never had to touch it again.
Might I ask if you could open source it? I badly need dead simple Real World examples.
Earlier quoted context omitted.
Sure. Hell I'll not only open-source it, I'll do a 10-minute video walkthru if I can get some coders to watch and ask questions.
If you upload it to YouTube, I'll watch and probably have a question or two for the comments section :-)
I came in cold, having not looked at the code in 5 months. I figured that would make for a much more honest walk-through than doing a lot of prep beforehand.
I think the best part about Vuejs right now is how simple it is and everything just works! A vue component is still as simple as {template: 'hi'}. You don't need webpack or any transliteration for it to work. Just drop the script tag like the good old jQuery and it's working! No wonder it has gained so much popularity as I don't think you can make it more KISS. Transition from vue1 to vue2 was really simple. I just h…
I keep hearing this "a vue component is still as simple as {template: 'hi'}". Genuine question: I've been using Vue for the last couple of months, is anybody actually using this in the real world? Instead of vue-cli apps with single-file components (which is the other argument often seen)?
And Rivets.js seems to be defunct.