Vue.js Creator Evan You Interview

That's $192k, pre-tax, between two people and likely infrastructure and tooling costs. Most developers of You's skill earn nearly double that at FAANG companies.

As far as I understand, he's not really running a company though. It's mostly a solo endeavor.

So it seems like in this case time put in ~ outcome.

Even my HN account is anonymous.

(That I think is holding me back too.)

I cannot imagine myself working like Evan.

Recently he built Vite to see if it'd be possible to have a dev setup with no bundling (just using ES modules). It's evolved since then, but he picks up work a lot on new ideas and seeing how it can drive the direction of Vue.

https://github.com/vitejs/vite#how-and-why

The tailwind project model seems like it would pay better. The profit amount might make for sense for the pretty popular project vs the extremely popular project. It's a compromise because you stop working on the core project and start building these additional businesses that take time/effort away the project.

Corporate backing would make sense but enterprise has picked react. Vue lives because it's a great framework that is easily assessible not because it started as a corporate sponsored project with a popularity boost buildin.

The Options API is still the default and remained pretty much the same.

I've primarily moved over to Django with server rendered content and sprinkles of JavaScript where needed.

Do you use Hooks in React? Because in that framework, that actually is replacing the older methods, and if you use Hooks then the Composition API is the same (and better in many ways).

4 year Vue dev here (right after 2.0 release). In Vue 2, you have a bunch of "magic" properties. Your state goes under the "data" key, computed properties go under "computed", methods go under... etc. Then you have the lifecycle hook magic methods: "created()", "destroyed()", etc.

In Vue 3, you have one function -- "setup()". This function returns the stuff you want to use inside of your component. This could be state/reactive data using "reactive()" or "ref()", derived data using "computed()", watchers, plain functions, whatever.

If you need to use lifecycle hooks, then you put an "onMounted(() => {})" or whatever in your "setup()".

The API was stripped down to essentially one initialization method where you set up everything you need.

Though to be fair, these days I write Vue like a weirdo and I use JSX with it.

  const App = defineComponent({
    setup() {
      const state = reactive({ count: 0, msg: "Hello" })
      const doubledCount = computed(() => state.count * 2)
      const inc = () => count.value++
      
      return () => (
        <div onClick={inc}>
          <p>{state.count}: {state.doubleCount}</p>
          <p>{state.msg}
        </div>
      )
    }
  })

Projects driven by "biggest things since sliced bread" tend to vane very quickly after the initial excitement, and agiotage about its buzzword feature is gone.

https://svelte.dev/tutorial/basics

Probably the same thing that stopped you from not using SFCs in Vue: One is idiomatic, the other isn’t ;)

The only way I know of to make them is to use styled components. RedwoodJS seems to doing something like a template literal for styling but that's still not really the same. In my opinion Vue's <style scoped> approach is much more elegant.

constantly scrolling up and down the file between the methods and the template/styling got pretty annoying quickly

Buy a bigger monitor. :)

Ref: https://vuejs.org/v2/guide/single-file-components.html#What-...

I also am pro human rights. Very much so. And yet I think that BLM does it all wrong, and all that will come out of their protests are more police, more government, more bigotry against the blacks, and more slums.

I suspect that there are a lot of people like myself.

But in the case of a project with over 50 branches, and hundreds of thousands of users, that advertises an active community and wants me to get involved, then it is entirely something else. There I think that great pains should be taken to keep out emotionally charged views, as there are bound to be lots of people that you actually want to be part of your community that will feel out of place. Hence my statement "large open source project".

Creds: I moved into a low-income area and have spent the past ten years providing education, money, and support, trying to improve the lives, and championing the cause of those living in such areas. I adopted a kid with a police record longer than your arm, and worked with him getting detoxed. I spend most of my waking hours on this, all volunteer.

I grew up in the projects. There was a dude some ten years older than myself - a programmer (back before computers were a thing) - who convinced me that I can do something with my life, but I have to take the onus of responsibility upon myself - even when it is someone else's fault.

That's the message I now try to give over - you guys are awesome, and some day you can change this whole here community around. But you gotta take the whole responsibility upon yourselves - especially when it is not your fault.

That's a big message, and hard for me to write in a post like this, but it works. I have hundreds of students that have healthy lives, and we have grown to 30 volunteers who help me.

When there are riots like these it passes a huge message - it is all "their" fault, and "we" deserve everything because of it, and we don't need to take any responsibility.

So, protests have a place. But the way that BLM projects it is, IMO, destructive, even if there are no riots.

Edit: I am not dismissing the bad and uncaring attitude projected by the police or government. I am not dismissing the emotion, anger and sometimes guilt of the protestors. There are protests and other actions that can be extremely useful. Perhaps thought can be put into what objectives can be gained, and how to get them, and then think if supporting BLM is really the way to get them. (Also, I know a few people who have joined BLM protests as a way of protesting Trump. IMO, not the best way to do that, either.)

I think they share more goals than they compete on, with Svelte being newer (compiler based) and Svelte taking an older style approach (Virtual DOM) to implement those goals.