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

91–100 of 129 posts

Re: Vue.js Creator Evan You Interview

#91

Post by agumonkey »

sethetter wrote: post #79
agumonkey wrote: post #76

Earlier quoted context omitted.

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)

Accountability! It can be scary, but it's also important and a driver for positive change. I deal with all of these things as well, but have pretty much decided to not go the anonymous route, because I would rather try to build that confidence in myself and embrace the accountability that comes along with it. That said, I still don't comment or publish much online out of this same anxiety. /shrug. It's a work in prog…

personally I dropped the whole thing, it's useless.

I'm going back to good old life.

Re: Vue.js Creator Evan You Interview

#92

Post by manigandham »

petepete wrote: post #27
onion2k wrote: post #12

Vue is awesome. The encapsulation that comes from single file components is something I would love to have in React.

That's my least favourite thing about Vue. One directory per component makes so much more sense to me, not having a mix of syntaxes in a single file. Still, Vue is my favourite tech for SPAs.

Vue (like with most of its features) let's you do that if you want. The and tags in the .vue file can reference other files so you can have a directory per component with separate code files. Sometimes that's helpful for better code completion and formatting too.

Re: Vue.js Creator Evan You Interview

#93

Post by pqdbr »

imhoguy wrote: post #66
Tolexx wrote: post #34

Earlier quoted context omitted.

Does it incorporate well with rails?? Again I think that stimulus.js can also give a feel of an SPA like when Vue is used

Yes. No issues with Webpacker as Vue is officially supported. In fact my quite old project is now augmented with Vue to make several micro-SPAs in interactive parts. Layout HTMLs are served the standard way with Haml. To get things faster I sometimes render data JSON objects in HTML page script tags to get rid of initial fetch - works nicely.

We do the same. The page loads with a div containing something like: ` `

Re: Vue.js Creator Evan You Interview

#94

Post by manigandham »

azangru wrote: post #24
genidoi wrote: post #18

Earlier quoted context omitted.

The Docs take Vue to a league of its own. I'd contend that no other JS ecosystem has docs that are as lucid, concise and beginner friendly as Vue's. This intro to VueX (Vue's state management library) is a good example: https://vuex.vuejs.org/

Are you guys all using ad blockers? I open Vue docs — and the right-hand column of the screen is a wall of ads. For comparison, I open React docs — and there are only docs there (unless you count the obligatory BLM header). With a larger font, too, because there, docs don't need to compete for page space with the ads.

Yes, there are ads. Top promo, 2 spaces for sponsors, and a small banner from Carbon ads. Depending on your resolution, it can take up significant space:

It's not noticeable on larger screens but they should consolidate these to a single location and definitely don't have a banner ad in the main page header.

Sample screenshot: https://i.imgur.com/bDste7S.png

Re: Vue.js Creator Evan You Interview

#95

Post by wetmore »

kyawzazaw wrote: post #87
matthoiland wrote: post #81

Earlier quoted context omitted.

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

New Jersey iirc.

Re: Vue.js Creator Evan You Interview

#96

Post by Pelic4n »

sam_goody wrote: post #37

I was turned off of Vue when they put a big "Join BLM" banner on the top of their site. In my vue, that is mixing politics and personal opinions into a public coding project. I believe this to be a non-no. It implies that those that don't share your [unrelated] views are not legitimate. In this example, it implies that those who are pro-minority rights but anti-protests are in some way less committed than their pro-r…

I disagree with you and I will explain my reasons why: BLM is not about politics or personal opinions, it is about human rights, so is the LGBT flag stuff, so is speaking out against the chinese governement for the Uyghurs genocide currently being carried out.

You know what has happened to Georges Floyd, Breonna Taylor and many others. People murdered routinely by the police without any consequences. Using whatever platform you have to speak out against it is morally right. Protests happens after decades of police violence against black communities, by being against those you are standing against an human rights issue (Whatever is your reason, even COVID). You need to be aware of that and think if that's a good use or your life. Plenty of people do, usually white nationalists, KKK members and neo-nazis, who are vocally againsts humans rights and equality between white people and people of colors.

Re: Vue.js Creator Evan You Interview

#97

Post by helloxyzxyz »

sam_goody wrote: post #37

I was turned off of Vue when they put a big "Join BLM" banner on the top of their site. In my vue, that is mixing politics and personal opinions into a public coding project. I believe this to be a non-no. It implies that those that don't share your [unrelated] views are not legitimate. In this example, it implies that those who are pro-minority rights but anti-protests are in some way less committed than their pro-r…

BLackMail. If you don't add the banner it's because you're a racist.

The equation is do you lose more patrons by having or not having the banner (and be accused of being a racist). Easiest, and most profitable, to just to add the banner...

Re: Vue.js Creator Evan You Interview

#98

Post by jtwaleson »

petepete wrote: post #27
onion2k wrote: post #12

Vue is awesome. The encapsulation that comes from single file components is something I would love to have in React.

That's my least favourite thing about Vue. One directory per component makes so much more sense to me, not having a mix of syntaxes in a single file. Still, Vue is my favourite tech for SPAs.

I really love single file components. We are extending the syntax more by also adding and tags to single file components. Great for automatically generating documentation and keeping it in the same place as the components. Was a bit afraid that the compiler would protest, but so far so good.

Re: Vue.js Creator Evan You Interview

#99

Post by wetmore »

sam_goody wrote: post #37

I was turned off of Vue when they put a big "Join BLM" banner on the top of their site. In my vue, that is mixing politics and personal opinions into a public coding project. I believe this to be a non-no. It implies that those that don't share your [unrelated] views are not legitimate. In this example, it implies that those who are pro-minority rights but anti-protests are in some way less committed than their pro-r…

People are not obligated to tell you why they don't like what you say. It's nice when you do get a reason but to liken a downvote to "angry destruction without reason" is a major reach. You are not entitled to their time.

I didn't downvote you but I'll tell you what rubbed me the wrong way about your comment. I think people who did downvote you probably felt similar. In short, I think your comment is patronizing. You imply that the people protesting are doing so in part as a result of "media exaggeration" and being "turned into victims". I read this as you saying that things aren't actually that bad, and the people protesting are doing so based on false pretenses. Your comment has the paternalistic air of "I know how to help these people better than they know how to help themselves".

Re: Vue.js Creator Evan You Interview

#100

Post by gavinray »

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…

Have you considered that this might be an issue on your end, and not the V3 Composition API's end?

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 () => (
        
          
{state.count}: {state.doubleCount}

          
{state.msg}
        
      )
    }
  })
Post reply on HN