I've been a React engineer for the past 5 years. I love React. I love making React applications. I think it's one of the best UI frameworks available right now.

1. V Slot Vue
2. Vue Slots Vs Props Play
3. Vue V-slot Props
4. Vue Slots Vs Props For Real
5. Vue Slot Or Prop
6. Vue Slot Examples
7. Vue Template Slot

However, there are a few competitors in this space. One of the biggest is Vue.js.

I've played around with Vue.js a little bit in the past but I figured it was way past due to do a deep dive into how Vue.js works, and how it makes my life as a UI engineer easy.

After delving deep into the Vue.js docs and playing around with Vue.js (note: I am in no way a Vue.js expert) I was shocked to find myself liking the way Vue.js did some things better than React.

Ultimately I hope that React steals is inspired by these things that Vue.js does and starts doing them as well.

Vuejs Slots Vs Props exclusive to new SuperCat customers. No deposit is required to claim although you must first create a new casino account and verify your account. The bonus offer may vary depending on Vuejs Slots Vs Props your location. Wagering requirements and terms and Vuejs Slots Vs Props conditions apply. Spread the love Related Posts How to create more complex slots in VueVue.js is an easy to use web app framework that we can use to develop Passing Props to Vue.js Route Components with Vue RouterVue.js is an easy to use web app framework that we can use to develop Create Styled Vue Components Easily. Photo by Mohammed Kabir on Unsplash. Vue 3 is in beta and it’s subject to change. Vue 3 is the up and coming version of Vue front end framework. It builds on the popularity and ease of use of Vue 2. Vue comes with two different ways of storing variables, props and data. These can be confusing at first, since they seem like they do similar things, and it's not clear when to use one vs the other.

Different Philosophies

One of the key differences between Vue.js and React is how they market and refer to themselves.

Taken straight from their home pages, React describes itself as 'a JavaScript library for building user interfaces' whereas Vue.js describes itself as 'progressive JavaScript framework' (emphasis mine).

React is a library, Vue.js is a framework. I think in many ways that is the underlying reason for the difference in how and why each UI framework does the things it does.

I wanted to highlight this so you keep it in mind while you read this post. Frameworks are historically more comprehensive and exhaustive in what they provide and require, whereas libraries are slimmer and do less, but what they do focus on they do extremely well.

Both Vue.js and React have components as a building block to create your UI.

Components are commonly comprised of 3 parts:

V Slot Vue

• UI (HTML)
• Behavior (JavaScript)
• Appearance (CSS)

Vue Slots Vs Props Play

Vue.js has their concept of a 'Single File Component' which is an out of the box way to write components that covers all 3 parts.

Here's what it looks like:

You don't have to be a Vue.js engineer to understand what's going on here.

React components include UI and Behavior out of the box, but style is very much kept out of the equation:

Of course React has a very rich community so if you do want to include styles you can easily reach for Emotion or Styled Components and they will fill the Style hole, but:

• It's not built in
• You have to know these libraries exist to use them.

As opposed to Vue.js where it's there, for free, by default.

Officially Supported Related Libraries

Any sufficiently large and complex UI application requires two additional pieces of functionality to support their large size:

• Router
• State Management

Vue.js has officially supported libraries that cover both those use cases, Vue Router andVuex respectively.

These libraries are explicitly mentioned on the Vue.js docs page and they are developed and maintained alongside Vue.js core. That's simply phenomenal.

It gives new Vue.js engineers a clear path towards a solution to their problems and gives them the confidence that these libraries are built to last so they can be confident when choosing them.

Having first-party supported libraries doesn't limit community solutions, but it does provide a go-to solution for new comers.

Uh, I want React to have this yesterday. Before you even read this section click the link and browse around Vue.js' style guide.

It answers so many questions newcomers to Vue.js may have. It provides best practices and guidelines on how to write 'proper' and approachable Vue.js applications.

It shares and codifies battle tested and community vetted best practices and patterns.

To top it all off - it's maintained and supported by Vue.js itself! Terrific!

As mentioned above Vue.js has built in support for styling. Further than that Vue.js essentially has the library classNames built-in.

Classnames is a terrific library for easily concatenating and dynamically constructing CSS classnames that should be applied to an HTML element.

In React land you'd have to know this library exists, and then install it.

In Vue.js it's just another built-in feature. From the docs:

Given a Vue.js template like this:

And data like this:

The resulting UI will be:

Having this built in is awesome.

Vue.js goes even further with their support for inline styles. Vue.js, like React, supports inline styles, however where Vue.js outshines React is its ability to auto prefix CSS that needs it.

When you use a CSS property that requires vendor prefixes in :style, for example transform, Vue will automatically detect and add appropriate prefixes to the applied styles.

Truly shows the strength of being a framework and controlling your own template syntax.

Everything in React is a prop.

If you want to render multiple arbitrary children in a React component then you just add more props:

This works fine but it's a tad awkward, especially if the content inside the props gets large.

Vue.js takes a different approach via Slots, and I think it's API is a little more cleaner.

Vue.js uses Slots (which is inspired by the Web Components spec draft) to clearly denote where content goes inside a component.

Something that Vue.js does repeatedly is provide shorthand for common tasks. In this case, the above example can be abridged with the Slot shorthand:

Vue.js has this feature called Directive Modifiers that I think are really really cool.

Before I can talk about Directive Modifiers let me give you a quick pitch on what a Directive is.

Directives are 'special attributes with the v- prefix' which you use inside Vue.js templates.

A directive's job is to reactively apply side effects to the DOM when the value of its expression changes

For example:

There's directives for event handlers:

Vue V-slot Props

Directives also support modifiers.

It's a very developer friendly way to perform common tasks with common directives.

For event handler directives (v-on) there's a whole slew of modifiers:

If you wanted to do this in React you'd either make a helper function or a custom component. Which is fine, but doesn't feel as clean compared to directive modifiers.

I am curious if someone could make a Babel JSX superset so you could write code like:

And it would transform to:

It's not in the ethos of React, but I still think it's a super neat productivity win.

There's many more Vue.js modifiers. Some of the coolest ones are key modifiers:

Very, very cool.

The v-model directive has a really interesting characteristic when binding data to form input elements.

From the docs, v-model internally uses different properties and emits different events for different input elements:

• text and textarea elements use value property and input event;
• checkboxes and radiobuttons use checked property and change event;
• select fields use value as a prop and change as an event.

What's great about this is you don't need to care about how the data is synced, just that it's taken care of for you.

Let's compare how React would do these bindings and how Vue.js does it:

Detecting a pattern here?

Now, one thing I will say in React's defense is that React encourages (and requires) you to learn how the data is actually set and how it changes. Which means that if you were to ever write a form with Vanilla JS you'd have a lot more knowledge on how it works and be able to code it correctly. As opposed to Vue.js which just abstracts away all those quirks for you.

Like any good framework you can create your own custom directives in Vue.js.

Vue Slots Vs Props For Real

Vue.js does note that 'the primary form of code reuse and abstraction is components' however one of the best examples of why a custom directive may be better is with their custom v-focus directive to automatically focus an input element on mount:

In React you'd probably write a custom component to accomplish the same thing, which seems a little heavy for such a light task.

Last but not least, Vue.js was recently rewritten from the ground up in TypeScript.

This means their TypeScript support is first-class as the framework itself is written in TypeScript.

Ultimately it doesn't really matter what React is written in, and I don't think it makes that much of a difference, but it's still a small little thing that was nice to see Vue.js have.

Video

I've expanded on these thoughts in video form as well! Feel free to watch if you're interested:

Vue Slot Or Prop

Closing Thoughts

Vue Slot Examples

After all that am I going to abandon React and start using Vue.js exclusively? No. I still very much enjoy the 'library-ness' of React and frankly I'm already very proficient at writing React applications.

Vue Template Slot

However I would love to see React grab some inspiration from Vue.js and incorporate some of these great ideas into React. If I had to choose just one from this list it's absolutely the style guide. I would love to see React have an officially supported and maintained style guide.

Hopefully I've opened your eyes to some things that you didn't know Vue.js did! I was certainly surprised to find myself really enjoying the way Vue.js did things!