• Welcome to Righteous Wrath Online Community. Please login or sign up.
 

Vue.js: there's a documentary for that

Started by Darren Dirt, February 28, 2020, 12:55:41 PM

Previous topic - Next topic

Darren Dirt

"Vue.js: The Documentary"
https://www.youtube.com/watch?v=OrxmtDw4pVI   Vue.js - The Documentary (Honeypot 24Feb2020)
"What began as a side project of a Google developer now shares the JS leaderboard with #React and #Angular..."


Also, wow, on the "Honeypot" yt channel there's a BUNCH of these!
https://www.youtube.com/channel/UCsUalyRg43M8D60mtHe6YcA/search?query=Documentary
Techie infotainment for nerds by nerds



After watching these 2 videos...

https://www.youtube.com/watch?v=KMX1mFEmM3E   Angular vs React.js vs Vue.js - My Thoughts! (Academind 15May2017)
https://www.youtube.com/watch?v=SWZ_4YBFBhs   React.js vs Angular vs Vue (Academind 31Jul2018)

...I guess it's safe to say that after 2.5 years there has been a lot of growth in terms of interest and usage of Vue.js!
_____________________

Get better at getting better. Daily.
_____________________

Mr. Analog

Gonna have to watch this tonight...

Sent from my Pixel 2 XL using Tapatalk

By Grabthar's Hammer

Darren Dirt

Quote from: Mr. Analog on February 28, 2020, 02:02:17 PMI'll have to check this out too. I've worked with angular in the past so I'm curious how this guy sees them contrasted

Angular 2? Or the much more simple Angular 1?

Apparently back in 2016 or so, when Google released Angular 2, it was so "shockingly different" that a ton of developers jumped on board Vue, as it "filled this void of people who wanted a lower barrier to entry, but they also wanted the strength and flexibilty that you had with something like React"
"Vue.js: The Documentary" @ 19:13

_____________________

Get better at getting better. Daily.
_____________________

Mr. Analog

Angular 2 was such a alien thing compared to Angular that it wasn't even comparable and turned a lot of people away initially because it meant rewriting everything from the foundation up. I don't know about Vue too much (watched the videos though, interesting history)

I might give Vue a try but for now the money is in React / Angular (like the comparison video says)... who knows it could really take off one day
By Grabthar's Hammer

Darren Dirt

At your new jorb it is all React? Or Angular1? Or Angular2?

And is most of the coding you do just defining relationships and bindings and whatnot, or is there a lot of low-level JS that you get to build to do custom things?
_____________________

Get better at getting better. Daily.
_____________________

Darren Dirt

On the subject of TypeScript (since Angular2 requires using it)...

Quote from: Darren Dirt on March 05, 2020, 09:57:54 AM
Quote from: Mr. Analog on March 04, 2020, 08:59:33 PMYes! Learn typescript!!! I use it developing React and man is it ever nice. Finally, strongly typed JavaScript, all the benefits of both worlds really.
Ironic, since the reason some folks claim to prefer React over Angular is that with React they are not forced to use TS (which Angular requires -- here's why** https://vsavkin.com/writing-angular-2-in-typescript-1fa77c78d8e8 ).


Quote from: Mr. Analog on March 04, 2020, 08:59:33 PMI have to say you can do everything Angular / Vue does with React though maybe not as cleanly.
State management, Routing, you name it you can do it with React. I can see how it got to be as popular as it has, it's very easy to learn.
https://reactjs.org/docs/getting-started.html


Impression I have so far is that the biggest advantage of React is how long it has been around and thus how many modules libraries components etc. have been built and real-world tested by a variety of devs and use cases... Kinda getting a similar vibe with Python (aka built-in core is solid and good enough for most needs, but any extra stuff There's A Library For That).


** one reply = LOL, them's fighting words! (But is he wrong?)
Quote from: https://medium.com/@neaumusic/typing-is-for-noob-enterprise-developers-who-cant-bowl-without-gutter-bumpers-who-can-t-code-in-87ac662497c4Typing is for noob enterprise developers who can't bowl without gutter bumpers, who can't code in legible organized statements without expanding the file 2-3x and having the IDE tell them what's wrong.
Java-land, legacy slow developers rely on that tooling, but it's a hinderance to proficient developers, and it's sad that tooling takes the place of testing and simple, legible code.

Fail fast / early return, don't write getters setters for non-dynamic variables and don't pull random @%&# out as constants.
It's frustrating that people think abstract is always better, but flat, redundant, simple and legible is often better for maintenance.
If you want stability with coders that rely on tooling, you should make test-driven development mandatory.
Stay out of the JavaScript ecosystem please, go back to Java.

JS relies on numbers, strings, booleans, functions, objects, and arrays, you can keep your abstract classes and memory management!!
_____________________

Get better at getting better. Daily.
_____________________

Darren Dirt

_____________________

Get better at getting better. Daily.
_____________________

Mr. Analog

Quote from: Darren Dirt on March 05, 2020, 09:52:40 AMAt your new jorb it is all React? Or Angular1? Or Angular2?

And is most of the coding you do just defining relationships and bindings and whatnot, or is there a lot of low-level JS that you get to build to do custom things?
It's all React baby

Sent from my Pixel 2 XL using Tapatalk

By Grabthar's Hammer

Mr. Analog

Quote from: Darren Dirt on March 05, 2020, 10:09:26 AMAnd is most of the coding you do just defining relationships and bindings and whatnot, or is there a lot of low-level JS that you get to build to do custom things?

At the moment it's mainly debugging BUT I did write a new High Order Component (HOC) that combined two component contexts into one and passed it down to another component. I guess I'm mainly working with relationships you could say. As far as low level code goes there's not a whole lot - and that's kind of the point of React. If something gets complicated it's probably meant to be a series of nested components each doing its thing rather than a complex blob of JavaScript (or in my case; Typescript.)

Thinking in React is Different(TM) it goes against everything I know from JQuery, XML parsing and other JavaScript I've written in the past as in there's no big picture at any given moment, no worrying about the whole DOM, it's all about a component and what it does in its little bubble and how it relates to other components.
By Grabthar's Hammer