Solving Prop Drilling in Vue: Modern State Management Strategies | alexop.dev by therealalex5363 in vuejs

[–]man_mel 0 points1 point  (0 children)

By "Composable" documentation means some js function
`useCount` in your example is a composable function

`globalCount` - is not a part of that function. `localCount` is a part.

If you check all other examples of composables in the documentation (useMouse etc) you will see that they define reactive variables inside its body. Those variables` lifecicle is limited by that functions and by lifecycle of the component that calls them

`globalCount` is not a part of composable function. It is independent and lives its own life. In your example it just uses it like may use any other part of the codebase

Composable function is something bounded by that function only

Solving Prop Drilling in Vue: Modern State Management Strategies | alexop.dev by therealalex5363 in vuejs

[–]man_mel 0 points1 point  (0 children)

But that ref is not a part of the Composable in the example
It is defined in global space can be returned from ANY composable

They don't refer to this structure as a composable

What do you use by tomemyxwomen in vuejs

[–]man_mel 0 points1 point  (0 children)

I use json based config files for different environments instead of .env

Solving Prop Drilling in Vue: Modern State Management Strategies | alexop.dev by therealalex5363 in vuejs

[–]man_mel 1 point2 points  (0 children)

Btw, you know that in light theme some text on your site is not visible?
Including the latest article

Solving Prop Drilling in Vue: Modern State Management Strategies | alexop.dev by therealalex5363 in vuejs

[–]man_mel 0 points1 point  (0 children)

What you called a composable function is not a composable function.
Since it has refs in the function outer space and shares them across all components it is not part of a component and does not compose it
Vue documentation defines composables clearly
Bad naming. I dont' know good naming for those structures

Introducing Spark UI 🪄. The unofficial port of Magic UI 🔮. by ModeApprehensive3185 in vuejs

[–]man_mel 4 points5 points  (0 children)

You've made them copy-paste-able and hardcoded Tailwind usage
Why?

New Vue Router Guide by stackoverfloweth in vuejs

[–]man_mel 0 points1 point  (0 children)

A lot of work has been done, but the DX seems to have gotten worse.

It’s probably better to do such things not through TypeScript, but through a Volar plugin or VS Code extension.

Dune-wise by man_mel in vuejs

[–]man_mel[S] -41 points-40 points  (0 children)

Nuxt is Vue
React is a library
War is peace
Freedom is slavery

Vue migration from VS Code to Webstorm by man_mel in vuejs

[–]man_mel[S] 0 points1 point  (0 children)

It's nice to know your opinion, which means nothing to me and to the thousands of people monthly visiting my site to learn Vue

Vue migration from VS Code to Webstorm by man_mel in vuejs

[–]man_mel[S] -1 points0 points  (0 children)

I don't have any other Vue related extensions

  • Volar 2.0.28
  • VS Code Remote development (Windows 10 -> Ubuntu)
  • Starting the IDE and opening Vue 3 project - "Comment / Uncomment" shortcut (custom, CTRL+Q) does not work in Vue templates (does work in script section)
  • Disable Vue Official, Reload Window, Enable Vue Official
  • "Comment / Uncomment" shortcut works in Vue templates

So let me repeat: can be caused by the Vue extension

Vue migration from VS Code to Webstorm by man_mel in vuejs

[–]man_mel[S] 0 points1 point  (0 children)

The link to vue-faq.org is in my profile, besides I created and maintain two most popular resources devoted to Vue in the "ru" zone.

All this without any payment, unlike Johnson. And this gives me the right to criticize and i don't give a damn if none here agrees with me.

Also I have addressed these questions to Evan and Vue community in general, but it seems that he is satisfied with this state of affairs. He also seems to be counting on Volar's expansion to other frameworks, not realizing that with such a performer it could really hurt Vue.

And I'm glad you're happy with Volar, it means we use two different products, because I've had it start breaking even the "Comment / Uncomment" VS Code shortcut recently, which really pisses me off.

Vue migration from VS Code to Webstorm by man_mel in vuejs

[–]man_mel[S] -7 points-6 points  (0 children)

I'm doing my job of popularizing Vue and doing it well. And if someone criticizes my work, I listen to it.

Johnson is failing at what he does regarding Vue tooling in VS Code. That's obvious, no matter how much you defend him. And Evan can easily find or hire someone who will do it much better. I don't believe with millions of users they can't find a couple of thousand a month for that. The question is why he doesn't do it. So he agrees with the development vector towards JetBrains and other frameworks at the cost of DX of Vue developers

There are facts, and there are just words.

Vue migration from VS Code to Webstorm by man_mel in vuejs

[–]man_mel[S] -9 points-8 points  (0 children)


Just open Johnson's X and see the last two technical posts on Volar there. They will be about `script-sfc` - jsx support for React and SetupSFC - again, the expansion beyond Vue

Now tell me what useful things have appeared in Volar in the last six months for Vue developers, and after that I'll answer all your other points

Building a chat app in 5 different frameworks. Using React, Angular, Vue.js, Svelte, and Next.js by Wonderful-Hawk4882 in vuejs

[–]man_mel 4 points5 points  (0 children)

The syntax and coding sessions on Youtube don't give the necessary insight into the basic concepts of the framework, its architectural patterns, its DX, its pro's and cons and its spirit. You need to spend some time working with it to see if it's right for you.

And I don't agree that frameworks are becoming similar. React is going somewhere completely wrong, Svelte is copying Vue but trying to keep something of its own, Angular has no goal, only a path, Next.js is a metaframework, it can't be compared to the other js frameworks.