25
AleCx04
8d

Good documentation is always a fucking good experience man.

And I particularly like how the Vue.js documentation is laid out. Straight up the framework is:
Easy to use
Concise
Has a lot of sane ideas
Good separation of concerns
Good Typescript integration
A really good cli tool

And above all this good shit is the documentation. Of all the major JS fronted tools I would say that this one is the one i like working with the most all in account of how easy to find the shit that I need is. Have built some otherwise complex shit using nothing more than documentation....albeit i have done this with most frontend shit i use.

Comments
  • 12
    Look I'm gonna need y'all to hold off on any further posts about how great vue is until I at least get through the set of react lessons I signed up for 🙄
  • 4
    @M1sf3t you can't go wrong with either or man.React is flipping awesome. I sorta kinda GREATLY dislike JSX. But its great otherwise
  • 2
    @AleCx04 So far I haven't found anything I can say I really dislike but some of the syntax throws me off a little. I'm even entirely sure whether it's react or just some of the more recent updates to javascript itself though. Guess we'll have to see what happens when I try to do something that isn't scripted already 😅
  • 1
    This nigga aint heard of reason lmao
  • 4
    @M1sf3t It's likely just ES6, as React is just plain javascript. (Or maybe it's the JSX part, if you're referring to something with html-like syntax.)
  • 1
    @ganjaman i told U about reason smdh -_-
  • 1
    I know, thats suppose to be the joke
  • 3
    Man, the vue docs... ho-ly shit.
    I think it's the best piece of documentation I've ever read.

    It has that awesome API to back it up, ofc.

    Definitely agree on jsx, it feels so off standard.
  • 0
    @Root I'm thinking most likely es6 too. I only learned certain parts to begin with and the only thing I've done since then to catch up was the stuff available at freecodecamp. Not completely knock their curriculum or anything but that particular section seemed a bit slapped together.

    But like arrow functions for instance, i get the basic syntax,

    name = () => {};

    but then get to one inside of another one like so....

    const ImageList = props => {

    const images = props.images.map( image => {

    return <ImageCard key= { image.id } image={image}/>;

    });

    return <div className="image-list">{images}</div>;

    };

    and the syntax for using the arrow within the map function I don't ever remember seeing.

    But then again, you've seen the first page I did, I only needed so much of the basic js that I learned and there were some things I wanted to do that I just utilized the jquery that was already plugged into bootstrap 🤷🏻‍♂️
  • 0
  • 2
    @M1sf3t
    The parenthesis around arrow functions' params are optional when there is only a single param, so people often omit them. Example:

    x => { console.log(x) }
    (x) => { console.log(x) }

    These two are identical, though the second is definitely easier to read.

    The html-like format is JSX, and it's really just syntactic sugar around very hard-to-read method calls.
  • 2
    @Root I am gonna be honest with you, and maybe you can help me see it. But I never understood when people say that React is "just Javascript". I just don't see it. I know that it goes down to Javascript once everything goes through the babel transpiler. But return(<div>{(youget) ? no : ifs}</div>) just does not feel like Javascript to me.

    My biggest pain point with it will always be the feeling that we are mixing in presentation with logic. I like it(I love React really) but JSX was always a pain point to me.
Your Job Suck?
Get a Better Job
Add Comment