Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vue.js Creator Evan You Interview

evrone.com

Post reply on HN
Print view View original

81–90 of 129 posts

Re: Vue.js Creator Evan You Interview

#81

Post by matthoiland »

langitbiru wrote: post #26
apacheCamel wrote: post #10

>Another important thing is that I take long breaks (several weeks) whenever I feel I need to — which is probably harder to do if I’m a full time employee at a company. A "Patreon-funded full-time job position" and the ability to take weeks off at a time? What an amazing career path Evan has taken. He sounds so passionate about Vue and he is fully funded to be able to do it. And what a good project to fund, always mo…

And the money is not bad. https://blog.patreon.com/vue-js-creator-evan-you

>$16,000/mo, enough to cover his salary along with his new hire

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.

Re: Vue.js Creator Evan You Interview

#82

Post by mesaframe »

agumonkey wrote: post #76
mesaframe wrote: post #59

Earlier quoted context omitted.

I experience similar anxiety. For too long I kept my profiles (GitHub/Twitter/..) pseudo-anonymous. So that If I mess up somewhere I don't have to face the consequences after I shut that account down. This is primarily due to social anxiety rather than having any malicious intent. Even my HN account is anonymous. (That I think is holding me back too.) I cannot imagine myself working like Evan.

I think it's a side effect of internet. By working too much in isolation we fear approval or rejection ? It frees us from following others opinions or a group direction but we also lose track of something (I'm blurry I have no precise word for this)

> It frees us from following others opinions or a group direction

This! The biggest pro is the freedom to say politically incorrect things.

Re: Vue.js Creator Evan You Interview

#83

Post by rk06 »

apacheCamel wrote: post #10

>Another important thing is that I take long breaks (several weeks) whenever I feel I need to — which is probably harder to do if I’m a full time employee at a company. A "Patreon-funded full-time job position" and the ability to take weeks off at a time? What an amazing career path Evan has taken. He sounds so passionate about Vue and he is fully funded to be able to do it. And what a good project to fund, always mo…

It sounds pretty good until you realise that it is the peak of open source full time job. And survivorship bias is taking place here.

Evan took a huge leap of faith when he quit his job for working full time on vue. I am happy that it has worked out well for him.

But it does not mean this path will work for other open source developers, of course they can still get corporate backing(node.js) or paid to work on it (react/angular) or make a business offering around it (laravel/tailwind)

This road is very less travelled.

Re: Vue.js Creator Evan You Interview

#84

Post by rk06 »

matthoiland wrote: post #81
langitbiru wrote: post #26

Earlier quoted context omitted.

And the money is not bad. https://blog.patreon.com/vue-js-creator-evan-you

>$16,000/mo, enough to cover his salary along with his new hire 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.

Well, those developers also live in silicon valley which is an expensive location.

I think the money is decent and Evan must also consider it to be decent enough to get a person working full time with it. And that's what matters

Re: Vue.js Creator Evan You Interview

#85

Post by nailer »

uallo wrote: post #14
candiddevmike wrote: post #4

Isn't this a little ironic considering the backlash against Vue 3 and the creation of Svelte?

> backlash against Vue 3 What backlash against Vue 3? I know that there were very passionate discussions about several different RFCs that eventually lead to the current Composition API. But as far as I can tell, the current Composition API is very well accepted in the community. Also, the Composition API is an addition and does not replace the API of Vue 2. So do you refer to the controversies about older RFCs? Beca…

I don't know much about Vue but the single file components used in Svelte was inspired by Vue.

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.

Re: Vue.js Creator Evan You Interview

#86

Post by brightball »

brylie wrote: post #80
brightball wrote: post #63

Earlier quoted context omitted.

This is the appeal of Phoenix LiveView for me. Server rendering was already incredibly fast with Phoenix, but the ability to forgo the majority of JS with LiveView bypasses all of these framework complications.

Yes, LiveView is very exciting, although I haven't used it. For those interested in LiveView-esque functionality in other frameworks , there are some similar projects cropping up: - Django Reactor https://github.com/edelvalle/reactor - Laravel Livewire: https://laravel-livewire.com/ - Rails Stimulus Reflex: https://docs.stimulusreflex.com/ - Intercooler.js: https://intercoolerjs.org/

I’d be very curious if those can be implemented in a performant way.

There’s a combination of low level features that combine to make LiveView work effectively.

Re: Vue.js Creator Evan You Interview

#87

Post by kyawzazaw »

matthoiland wrote: post #81
langitbiru wrote: post #26

Earlier quoted context omitted.

And the money is not bad. https://blog.patreon.com/vue-js-creator-evan-you

>$16,000/mo, enough to cover his salary along with his new hire 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.

DO we know where he lives? Patreon is not his sole revenue source.

Re: Vue.js Creator Evan You Interview

#88

Post by [deleted] »

matthoiland wrote: post #81
langitbiru wrote: post #26

Earlier quoted context omitted.

And the money is not bad. https://blog.patreon.com/vue-js-creator-evan-you

>$16,000/mo, enough to cover his salary along with his new hire 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.

[deleted]

Re: Vue.js Creator Evan You Interview

#89

Post by hasperdi »

syndacks wrote: post #65

How was Evan able to work on Vue while employed by Google? Didn't his contract have a clause in it (as I know most tech companies do) that more or less states: anything you make while working here is ours, regardless of wether you do it in your free time or not (especially an Angular competitor).

I think he started Vue after his Google time. Tde story is covered in thing short documentary https://m.youtube.com/watch?v=OrxmtDw4pVI

Re: Vue.js Creator Evan You Interview

#90

Post by manigandham »

midrus wrote: post #38
jdellinger wrote: post #28

So I recently had the opportunity to use the new composition API, which will come in V3, in a project and want to share my two cents. The project had some limitations tho: no webpack and no typescript (so basically inline x-templates and pure browser JS). Starting of with the composition API was great. No "this", easy reuse of logic via react-like "useXYZ" hooks and a general fast development. But two things really b…

I used to prefer (and by a lot) Vue more than React because of its simplicity and completeness (router + store + everything you need). After trying to use v3 for a new project and trying out the composition API, I've gone back to React. With v3, and the composition API, to me, it lost all of its appeal (being simple, easy and complete). Now to me it has the worst of both worlds... it's not as easy anymore, has a lot…

This doesn't add up. None of the simplicity or completeness has changed, and the composition API is completely additive and optional. You can still use Vue exactly like you always have, with better performance and flexibility.

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).

Post reply on HN