4 ms·

I'd love to read the follow up article 1 year from now. And then 3 years, and 5 and 10. Vue 2.0 was a complete rewrite and their "long-term-support" for v1 was

I'd love to read the follow up article 1 year from now. And then 3 years, and 5 and 10. Vue 2.0 was a complete rewrite and their "long-term-support" for v1 was 9 months of security updates. I'm not trying to single out Vue, but I wonder how many job posting are for someone to maintain a legacy framework code base. (Legacy meaning 6 months old.)

huskyr 9y ago
The difference to me with other frameworks (most notably Angular) is that the transition from Vue 1.0 to 2.0 was relatively smooth. I've migrated a couple of smaller applications and that was done in just a couple of minutes. If Vue keeps the core and focus small i think maintenance will be easier than with comparable frameworks.
- bartread 9y ago
  Agreed. I used to be a fan of Angular but all that drama put me off it for good.
- krob 9y ago
  Vue is the php of JS frameworks. Feeling a bit ironic for using it, I'm also a user of php, and it just feels right.
ohceecho 9y ago
Anecdotal, but I had to migrate a mid-sized app (about 400 components) from Vue 1 to Vue 2 and it took less than a day of work to modify the code, test it and push to production. We weren't using that many removed features to begin with, though.
bartread 9y ago
Yeah, I'm always a bit sceptical of these kinds of articles. Been saying to people for years that everything we build today is tomorrow's legacy. This whole idealistic fantasy that this time around "we're going to get it right" - whether it's because we're smarter than those who came before, or we have better tooling, or a better framework, or better languages, or whatever specious reason is given - is just that: fantasy. In the face of changing business and product requirements, and evolving markets and technologies, you have to accept the fact that almost every piece of software you build has a shelf life, and that shelf life is often surprisingly short. Therefore, rather than try to guess the future (and get it wrong, because most people do, most of the time) you're much better to focus on the problems you have to solve right now. Sure, don't code yourself into a corner by building some sort of tightly coupled ball of spaghetti, because that's always going to turn out badly, but to think that's what you're resigning yourself to by focussing only on problems you need to solve right now is to conflate two entirely separate issues.
- HumanDrivenDev 9y ago
  > This whole idealistic fantasy that this time around "we're going to get it right" - whether it's because we're smarter than those who came before, or we have better tooling, or a better framework, or better languages, or whatever specious reason is given - is just that: fantasy. I'm glad smart people before me have decided that they're going to try and get stuff right or at least more right. Say what you will about Java or C# enterprise software, but I can't imagine COBOL was any more fun.
  - bartread 9y ago
    I'm not against doing things well - far from it - but the idea that you should try to build a perfect system that takes into account every unforeseen eventuality is madness. Also, agree about COBOL, but software systems these days - in C#, Java, whatever - are often larger and more complex than those written in COBOL. Partly this is because of higher user and business expectations of what can be achieved with technology, partly it's because the modern tools make it easier (or even realistically possible!) to do that. It's still the same deal though: it's all legacy in the end.
mercer 9y ago
For me this is actually a reason to use React even if Vue might be more appropriate. I fear that the 'front-end ecosystem' is still a bit too much in flux to settle on a framework as relatively opinionated as Vue. What makes React both nice and complicated is that it's really pretty bare-bones (even with Redux), and as a consequence a lot of the stuff you learn with either be useful for JS programming in general, functional programming, and UI building in general. For example, I've been working on a little command-line tool in Elixir, and a lot of what I do in the view/render code is very much like React and what I learned by using React.
Can_Not 9y ago
VueJS 2 was an easy upgrade. Most people are probably starting on VueJS 2 anyways, coming from jQuery or ng1. When I started using VueJS my biggest pain point was how much bootstrap assumed you were using jQuery.

huskyr 9y ago

The difference to me with other frameworks (most notably Angular) is that the transition from Vue 1.0 to 2.0 was relatively smooth. I've migrated a couple of smaller applications and that was done in just a couple of minutes. If Vue keeps the core and focus small i think maintenance will be easier than with comparable frameworks.

bartread 9y ago
Agreed. I used to be a fan of Angular but all that drama put me off it for good.
krob 9y ago
Vue is the php of JS frameworks. Feeling a bit ironic for using it, I'm also a user of php, and it just feels right.

ohceecho 9y ago

Anecdotal, but I had to migrate a mid-sized app (about 400 components) from Vue 1 to Vue 2 and it took less than a day of work to modify the code, test it and push to production. We weren't using that many removed features to begin with, though.

bartread 9y ago

Yeah, I'm always a bit sceptical of these kinds of articles. Been saying to people for years that everything we build today is tomorrow's legacy. This whole idealistic fantasy that this time around "we're going to get it right" - whether it's because we're smarter than those who came before, or we have better tooling, or a better framework, or better languages, or whatever specious reason is given - is just that: fantasy. In the face of changing business and product requirements, and evolving markets and technologies, you have to accept the fact that almost every piece of software you build has a shelf life, and that shelf life is often surprisingly short. Therefore, rather than try to guess the future (and get it wrong, because most people do, most of the time) you're much better to focus on the problems you have to solve right now. Sure, don't code yourself into a corner by building some sort of tightly coupled ball of spaghetti, because that's always going to turn out badly, but to think that's what you're resigning yourself to by focussing only on problems you need to solve right now is to conflate two entirely separate issues.

HumanDrivenDev 9y ago
> This whole idealistic fantasy that this time around "we're going to get it right" - whether it's because we're smarter than those who came before, or we have better tooling, or a better framework, or better languages, or whatever specious reason is given - is just that: fantasy. I'm glad smart people before me have decided that they're going to try and get stuff right or at least more right. Say what you will about Java or C# enterprise software, but I can't imagine COBOL was any more fun.
- bartread 9y ago
  I'm not against doing things well - far from it - but the idea that you should try to build a perfect system that takes into account every unforeseen eventuality is madness. Also, agree about COBOL, but software systems these days - in C#, Java, whatever - are often larger and more complex than those written in COBOL. Partly this is because of higher user and business expectations of what can be achieved with technology, partly it's because the modern tools make it easier (or even realistically possible!) to do that. It's still the same deal though: it's all legacy in the end.

mercer 9y ago

For me this is actually a reason to use React even if Vue might be more appropriate. I fear that the 'front-end ecosystem' is still a bit too much in flux to settle on a framework as relatively opinionated as Vue. What makes React both nice and complicated is that it's really pretty bare-bones (even with Redux), and as a consequence a lot of the stuff you learn with either be useful for JS programming in general, functional programming, and UI building in general. For example, I've been working on a little command-line tool in Elixir, and a lot of what I do in the view/render code is very much like React and what I learned by using React.

Can_Not 9y ago

VueJS 2 was an easy upgrade. Most people are probably starting on VueJS 2 anyways, coming from jQuery or ng1. When I started using VueJS my biggest pain point was how much bootstrap assumed you were using jQuery.