5 ms·

I can vouch for the author's points on the good parts of vue.js. We've built our single page application (SPA) web app with vue.js and are very pleased with th

I can vouch for the author's points on the good parts of vue.js. We've built our single page application (SPA) web app with vue.js and are very pleased with the results -- https://checkoutclip.com https://checkoutclip.com. We were able overcome most of the stumbling blocks by looking up https://vuejs.org/v2/guide/ https://vuejs.org/v2/guide/, https://github.com/vuejs/vue/issues https://github.com/vuejs/vue/issues and https://forum.vuejs.org https://forum.vuejs.org. For server side rendered (SSR) pages, we're using nuxt.js, which is working out great as well. E.g. SSR page: https://video.checkoutclip.com/-LDQ5TtL_yywYCgUNb6K https://video.checkoutclip.com/-LDQ5TtL_yywYCgUNb6K I would recommend vue.js for anyone building their first SPA even if they don't have prior experience building one...it's easy to pick up.

ppiuser 8y ago
Have you looked at your site with javascript disabled? Additionally, was vue used just for the website or the chrome app as well?
- carusooneliner 8y ago
  Our site does't work with js disabled. Serious question: is it common for folks to disable js? vue is used only for the web app. No js frameworks used in the chrome app.
  - jazoom 8y ago
    It's not common. My site with hundreds of thousands of users has been using React/Vue for years and I've never had one complaint about JavaScript. If JavaScript is disabled I just show a message saying the site needs it. I also only support modern browsers and haven't had a complaint for 3 years. About 3 months ago I completely dropped support for any browser that doesn't support CSS grid (no more IE 11!). Again, no complaints. This one is more "brave" but I use Modernizer and show a clear message outlining all the required features the user's browser doesn't support and why they would want that feature in a browser. There's a link to a website to help them find a modern browser on their platform. Edit: I realised that based on what I said you could argue that users are annoyed but I'm just not aware. I doubt this is the case since the users are keen and vocal. I get messages almost daily from them telling me the features they want to see. The last time this had to do with browser support was one message 3 years ago about IE9 not supporting the TLS certificate or something. They were forced to use IE9 at work.
    - RussianCow 8y ago
      Without hard data, this is pretty meaningless. If I were to visit a site that didn't work correctly in my browser, I would close the tab and never give it another thought. I would certainly not take the time to write a complaint. > I doubt this is the case since the users are keen and vocal. I get messages almost daily from them telling me the features they want to see. Maybe existing users (and even for that, I'm skeptical), but how many potential users did you lose because they couldn't even open your app? I'm not saying you are wrong, just that "users didn't complain" != "users weren't affected".
      - jazoom 8y ago
        >If I were to visit a site that didn't work correctly in my browser, I would close the tab and never give it another thought. I would certainly not take the time to write a complaint. And I wouldn't miss you. I can make the service better faster if I don't support the lowest common denominator. I'm sure I'd lose more users if the website was bloated with fallback code and my development speed was such that features are a year behind where they are now.
        RussianCow 8y ago
        But dropping support for certain browsers/clients without having data on how many of your customers would be affected is silly, IMO. You might decide to drop support for IE 11 because you want to use CSS Grid without hassle, but then it turns out that 10% of your users use that browser! As with everything, you have to weigh the tradeoff, but you can't do that if you don't have the data to begin with.
        jazoom 8y ago
        > without having data on how many of your customers would be affected is silly You're making the assumption I don't have and use data like that? That's an incorrect assumption.
        8y ago
  - tambourine_man 8y ago
    Graceful degradation: https://en.wikipedia.org/wiki/Fault_tolerance https://en.wikipedia.org/wiki/Fault_tolerance Progressive enhancement: https://en.wikipedia.org/wiki/Progressive_enhancement https://en.wikipedia.org/wiki/Progressive_enhancement
  - shakna 8y ago
    > Our site does't work with js disabled. Then please have a noscript tag. > Serious question: is it common for folks to disable js? That's not the only reason you'll find for JS being unavailable. Windows Updates has managed to disable JS in various situations across both Edge and IE over the years due to tightening security policies. Chrome has had V8 crashes over the years, as has Firefox. The browser might be misbehaving, but rarely will the user attribute it to the right place - your site will get the blame.
  - benbristow 8y ago
    It's best to use some sort of server-side rendering so you get the best of both worlds. JavaScript-only is not friendly for SEO.
    - carusooneliner 8y ago
      Agreed! We're working on prerendering some pages -- https://ssr.vuejs.org/#why-ssr https://ssr.vuejs.org/#why-ssr .
  - j1elo 8y ago
    Well for what is worth, I had been thinking on the idea for a while after growing tired of so many scripting and tracking everywhere, and I felt encouraged to make the jump and disable Javascript after reading this comment in HN (thanks bmurphy!): > The single best improvement I've made to my mobile browsing experience in years wasn't getting a new faster phone, it was installing Brave and disabling javascript. [1] To be honest, (s)he was right. But at the same time, it's disgusting, and plainly bad, to see how much of the Internet is _broken_. Which by my definition means requiring JS even to show some text and images on a web page. I understand that more advanced features might require some scripting, but come on, I'm pretty sure that's not the case for printing some good old letters and pixels on a browser window! And still, lots of places seem to not know how to do it without dynamic code all around. (I'm not talking about this specific site, in any case. Just felt like ranting.) [1]: https://news.ycombinator.com/item?id=14153588 https://news.ycombinator.com/item?id=14153588
  - ppiuser 8y ago
    I usually leave it enabled, I just tested it when I viewed the page source and saw very little was there beyond JS. I guess I come from a different time where you used as little JS as possible/was required. I'm also not familiar with vue so I was trying to work out if it was used to build your web page or the actual chrome app. The web page is fine but I just wasn't sure where vue came into the picture for such a simple site.
mcbits 8y ago
Five (5) megabytes of JavaScript for a basic brochure site... I assume 99.9% of that is only necessary after signing up and signing in, not while unfortunately viewing the page on a less-than-flagship mobile device and metered data plan?
- joshschreuder 8y ago
  Welcome to web in 201x. This is not a problem exclusive to Vue. With that said, the new vue-cli uses Webpack 4 now which can do code splitting, and you can code split on route also to make individual page bundles smaller.
- carusooneliner 8y ago
  It's going to change and get less hefty, we're looking into code splitting.
  - caseymarquis 8y ago
    Vue makes it incredibly easy!
    - BJanecke 8y ago
      The new module system makes it easy ;)
- sametmax 8y ago
  Not to mention the images. The home page background image alone is 600ko ! More than the entire HTML. Saving the site on the hard drive gives me a wooping 10Mo for a home page. with a menu, a few pictures and some text. This is insane.

ppiuser 8y ago

Have you looked at your site with javascript disabled? Additionally, was vue used just for the website or the chrome app as well?

carusooneliner 8y ago
Our site does't work with js disabled. Serious question: is it common for folks to disable js? vue is used only for the web app. No js frameworks used in the chrome app.
- jazoom 8y ago
  It's not common. My site with hundreds of thousands of users has been using React/Vue for years and I've never had one complaint about JavaScript. If JavaScript is disabled I just show a message saying the site needs it. I also only support modern browsers and haven't had a complaint for 3 years. About 3 months ago I completely dropped support for any browser that doesn't support CSS grid (no more IE 11!). Again, no complaints. This one is more "brave" but I use Modernizer and show a clear message outlining all the required features the user's browser doesn't support and why they would want that feature in a browser. There's a link to a website to help them find a modern browser on their platform. Edit: I realised that based on what I said you could argue that users are annoyed but I'm just not aware. I doubt this is the case since the users are keen and vocal. I get messages almost daily from them telling me the features they want to see. The last time this had to do with browser support was one message 3 years ago about IE9 not supporting the TLS certificate or something. They were forced to use IE9 at work.
  - RussianCow 8y ago
    Without hard data, this is pretty meaningless. If I were to visit a site that didn't work correctly in my browser, I would close the tab and never give it another thought. I would certainly not take the time to write a complaint. > I doubt this is the case since the users are keen and vocal. I get messages almost daily from them telling me the features they want to see. Maybe existing users (and even for that, I'm skeptical), but how many potential users did you lose because they couldn't even open your app? I'm not saying you are wrong, just that "users didn't complain" != "users weren't affected".
    - jazoom 8y ago
      >If I were to visit a site that didn't work correctly in my browser, I would close the tab and never give it another thought. I would certainly not take the time to write a complaint. And I wouldn't miss you. I can make the service better faster if I don't support the lowest common denominator. I'm sure I'd lose more users if the website was bloated with fallback code and my development speed was such that features are a year behind where they are now.
      - RussianCow 8y ago
        But dropping support for certain browsers/clients without having data on how many of your customers would be affected is silly, IMO. You might decide to drop support for IE 11 because you want to use CSS Grid without hassle, but then it turns out that 10% of your users use that browser! As with everything, you have to weigh the tradeoff, but you can't do that if you don't have the data to begin with.
        jazoom 8y ago
        > without having data on how many of your customers would be affected is silly You're making the assumption I don't have and use data like that? That's an incorrect assumption.
        8y ago
- tambourine_man 8y ago
  Graceful degradation: https://en.wikipedia.org/wiki/Fault_tolerance https://en.wikipedia.org/wiki/Fault_tolerance Progressive enhancement: https://en.wikipedia.org/wiki/Progressive_enhancement https://en.wikipedia.org/wiki/Progressive_enhancement
- shakna 8y ago
  > Our site does't work with js disabled. Then please have a noscript tag. > Serious question: is it common for folks to disable js? That's not the only reason you'll find for JS being unavailable. Windows Updates has managed to disable JS in various situations across both Edge and IE over the years due to tightening security policies. Chrome has had V8 crashes over the years, as has Firefox. The browser might be misbehaving, but rarely will the user attribute it to the right place - your site will get the blame.
- benbristow 8y ago
  It's best to use some sort of server-side rendering so you get the best of both worlds. JavaScript-only is not friendly for SEO.
  - carusooneliner 8y ago
    Agreed! We're working on prerendering some pages -- https://ssr.vuejs.org/#why-ssr https://ssr.vuejs.org/#why-ssr .
- j1elo 8y ago
  Well for what is worth, I had been thinking on the idea for a while after growing tired of so many scripting and tracking everywhere, and I felt encouraged to make the jump and disable Javascript after reading this comment in HN (thanks bmurphy!): > The single best improvement I've made to my mobile browsing experience in years wasn't getting a new faster phone, it was installing Brave and disabling javascript. [1] To be honest, (s)he was right. But at the same time, it's disgusting, and plainly bad, to see how much of the Internet is _broken_. Which by my definition means requiring JS even to show some text and images on a web page. I understand that more advanced features might require some scripting, but come on, I'm pretty sure that's not the case for printing some good old letters and pixels on a browser window! And still, lots of places seem to not know how to do it without dynamic code all around. (I'm not talking about this specific site, in any case. Just felt like ranting.) [1]: https://news.ycombinator.com/item?id=14153588 https://news.ycombinator.com/item?id=14153588
- ppiuser 8y ago
  I usually leave it enabled, I just tested it when I viewed the page source and saw very little was there beyond JS. I guess I come from a different time where you used as little JS as possible/was required. I'm also not familiar with vue so I was trying to work out if it was used to build your web page or the actual chrome app. The web page is fine but I just wasn't sure where vue came into the picture for such a simple site.

mcbits 8y ago

Five (5) megabytes of JavaScript for a basic brochure site... I assume 99.9% of that is only necessary after signing up and signing in, not while unfortunately viewing the page on a less-than-flagship mobile device and metered data plan?

joshschreuder 8y ago
Welcome to web in 201x. This is not a problem exclusive to Vue. With that said, the new vue-cli uses Webpack 4 now which can do code splitting, and you can code split on route also to make individual page bundles smaller.
carusooneliner 8y ago
It's going to change and get less hefty, we're looking into code splitting.
- caseymarquis 8y ago
  Vue makes it incredibly easy!
  - BJanecke 8y ago
    The new module system makes it easy ;)
sametmax 8y ago
Not to mention the images. The home page background image alone is 600ko ! More than the entire HTML. Saving the site on the hard drive gives me a wooping 10Mo for a home page. with a menu, a few pictures and some text. This is insane.