Earlier quoted context omitted.
You don't have to render stuff on the server?
I never felt any pain that my servers do rendering. Did you encounter any problems with it?
[deleted]
Vue.js and Brunch: Webpack Alternative
71–80 of 113 posts
Re: Vue.js and Brunch: Webpack Alternative
#72Do you guys use any public websites that are based Vue, React or alike? Everytime I search for sites that use frameworks like Vue or React, I came up with mostly empty hands. Except for example pages or pages by coders for coders. Or pages that "use" one of the frameworks but seem to make no use at all of the functionality. When I ask around people usually tell me "Well, at my company we make a dashboard for another…
Just install the React Developer Tool extension on chrome:
https://chrome.google.com/webstore/detail/react-developer-to...
It will light up whenever you are navigating a page built w/ React. Plus, you can dig around and see how they structured it.
Some times you get funny surprises, like how the Microsoft node js page was using React, but they had deployed a Development build instead of a Production build.
Re: Vue.js and Brunch: Webpack Alternative
#73Earlier quoted context omitted.
We're using React on NFL.com's new home page and Vue on https://nextgenstats.nfl.com/ (two different teams). AirBnB is mostly React too.
Interesting. What would you say are the main advantages over simply passing the data through a server side rendering library?
In my opinion, client-side rendering is here as a justification for the unfortunate splitting of the Fullstack developer into Frontend/Backend roles.
Frontend developer used to be a designer who also knew HTML/CSS but the problem with that is that in order to do CSS well, you need to be a programmer. Especially if you're trying to achieve effects that work best as a mix of JS/CSS. Unfortunately, when it comes to design, UX and UI, most developers are lazy and refuse to learn the basics of it. So in order to prevent PMs from assigning them design-related tasks, the role of Frontend developer was born.
And once there was a separate role, it only made sense to isolate the Frontend developers' environment from the backend developers' so that they could stop stepping on each others toes.
Essentially, the whole Single Page Application architecture is because there is a class of developers who imagine that it's sensible to completely ignore design considerations and who built a moat around their responsibilities in the form of an unnecessary abstraction. Now rather than our views having direct access to our databases, we need a separate API endpoint for every single database call and since we can't trust client code, we need to authorize/authenticate every single little action rather than being able to blindly trust the code that's being run like we used to.
Re: Vue.js and Brunch: Webpack Alternative
#74Earlier quoted context omitted.
I know this will get downvoted, but here I go anyway: Please stop reinventing the wheels. Just stick to one library/framework whatever crap they are. Why? Because your new shiny wheel will be as crap as the old one very soon. I am myself refusing learning new tools in javascript. I think I have spent enough time learning enough of them. I have a selected set of them, and I turn down projects which fall out of that se…
one thing i learned to accept with the web is just how fast a trend can change in this industry. after i invested time in knockout, then came angular. then once i invest in angular, then came react. then after investing time in react, then came vuejs. it seems to either be a systematic cycle of people wanting to always try new things or that the tools are infact getting better and better. and once a group of pack sta…
the FE world used to be anemic in term of options. Then came Ajax, stronger web standards and eventually ES6, HTML5, etc.
So that was a period of transition where finally all of the stuff the rest of world had was within our reach. But since we were starting (almost) from scratch, we had a chance to make it better. However, to do that, we had to experiment (and fail a lot).
Thats where you saw all these tools as people iterated on it. It slowed down a lot now, and a lot of concepts bubbled up on top and we're down to only a couple of mainstream options (there's a lot of more obscure ones, but that's true in JVM/backend land too, and that's been around for a while).
Re: Vue.js and Brunch: Webpack Alternative
#75Great ideas. It seems like this sort of 'sane defaults' functionality could easily be added to future versions of webpack, and that might really help with adoption... rather than this community endlessly switching tool chains.
I'm surprised we haven't seen config packages for webpack take off along the lines of the configs in the ESLint community. There's nothing stopping anyone from publishing an extensible base config.
There IS an abstraction on top of Webpack called "terse webpack":
https://github.com/ericclemmons/terse-webpack
It seems to have presets for sane defaults on the roadmap.
Re: Vue.js and Brunch: Webpack Alternative
#76Do you guys use any public websites that are based Vue, React or alike? Everytime I search for sites that use frameworks like Vue or React, I came up with mostly empty hands. Except for example pages or pages by coders for coders. Or pages that "use" one of the frameworks but seem to make no use at all of the functionality. When I ask around people usually tell me "Well, at my company we make a dashboard for another…
https://youpic.com/ (press explore) uses React and Redux.
Re: Vue.js and Brunch: Webpack Alternative
#77Do you guys use any public websites that are based Vue, React or alike? Everytime I search for sites that use frameworks like Vue or React, I came up with mostly empty hands. Except for example pages or pages by coders for coders. Or pages that "use" one of the frameworks but seem to make no use at all of the functionality. When I ask around people usually tell me "Well, at my company we make a dashboard for another…
Just install the React Developer Tool extension on chrome: https://chrome.google.com/webstore/detail/react-developer-to... It will light up whenever you are navigating a page built w/ React. Plus, you can dig around and see how they structured it. Some times you get funny surprises, like how the Microsoft node js page was using React, but they had deployed a Development build instead of a Production build.
For Vue, you can use the Vue Devtools extension to do the same. If they deploy in production mode you won't see any details though.
Re: Vue.js and Brunch: Webpack Alternative
#78Earlier quoted context omitted.
The loading spinners happen when data is being fetched from the database. The app itself is downloaded upon initial load and anything from the database will trigger a loading spinner as it's being fetched.
Yup, I got that. But couldn't a bit of text be loaded instantly instead? Is the time the spinners run determined by the time the server needs to deliver the data? Would they go away when you put the site behind a CDN that delivers the data faster?
> But couldn't a bit of text be loaded instantly instead?
Yep. You could code your website in such a way to use a mix of serverside rendering and ajax components. This has always been true. Consider something like a server-rendered blog post that has a client-rendered Disqus widget.
> Is the time the spinners run determined by the time the server needs to deliver the data?
Basically. But you can also render your react app or vue on the server and then have client side rendering take over once the page is loaded. This is perhaps the ideal case but it's more complicated and takes some work to set up (I haven't actually done it).
Re: Vue.js and Brunch: Webpack Alternative
#79I really love using Laravel Mix [1], which is a wrapper around webpack. I know nothing about webpack, because mix makes it easy to just get going on my actual project instead of futzing about with configuration. Edit: FYI, Laravel not required. 1. https://github.com/JeffreyWay/laravel-mix/tree/master/docs#r...
Agreed - Laravel Mix makes it absurdly easy to get started with Webpack, while still getting a lot of power out of it. And you can use it in anything: a mostly server-side app (like a typical Laravel project, where Mix originated), a complex SPA, or even a WordPress theme (which I found myself doing over the weekend).
Re: Vue.js and Brunch: Webpack Alternative
#80Do we still need Webpack when all connections can use HTTP/2 and TLS thanks to LetsEncrypt ?
You need webpack to actually use a Vue component (template + script + CSS).
You can use Browserify or Rollup too.