Vue forum unstable

[Vinccool96]

Vue version

irrelevent

Link to minimal reproduction

https://forum.vuejs.org

Steps to reproduce

Visit https://forum.vuejs.org/

What is expected?

Vue forum works

What is actually happening?

Vue forum returns status 500

System Info

No response

Any additional comments?

No response

[LinusBorg]

We are aware that the forum has been down and up again for the last few weeks. Unfortunately, the problem proves not to be easily resolved. We will continue working on it, but it might take some time to gett stable again.

Unfortunately none of us is very proficient in running and optimizing a Discourse Forum.

PS: moved to discussions as it's not a Vue core bug.

[vincerubinetti]

Has this been shut down permanently? I was trying to look up an old question of mine to see if it had an answer (see below), and it just redirects to the discussions here.

https://forum.vuejs.org/t/element-selectors-with-scoped-are-slow-citation-needed/130568

[cehceh]

Till now it gives (Bad gateway - Error code 502)
Visit https://www.cloudflare.com/5xx-error-landing?utm_source=errorcode_502&utm_campaign=forum.vuejs.org for more information.
2023-04-25 12:34:38 UTC

That's so disappointing ...
Anyway, I hope it returns online soon

[Tomblarom]

Bump... Still down :( A lot good resource is lost.

[0x-7c00]

Vue is a lost cause anyway. Time to move on.

Welcome to contribute to Vue for everyone rather than say Vue is a lost cause anyway here.

[Esensats]

@olfek

Vue is a lost cause anyway. Time to move on.

I'm curious why is it a lost cause?

[darrelfrancis]

It's certainly not a lost cause. It's just him being silly. It's my sole front end framework! (Although I still use the options API)

[olfek]

@Esensats

• Documentation split between Options API and Composition API resulting in,
  in-comprehensive documentation for both.
• They like to spend time making their own tools rather than using what is already
  available and focusing on what actually matters. Example, rollup.js, Vite.
• They don't listen - Support emit on <slot> #7755
• UI and UI control code not separated like in Angular. "Single-File Components" 🤢
  • SFC is a choice, but the alternative affects application behavior - more documentation split.
• TypeScript still a choice in 2023 when it is definitely the better option.
  • More documentation split because of this.
• Vue 2 was better. I've never used it, but I've come to this conclusion from the old
  documentation I've come across and peoples thoughts and opinions of it
  compared to Vue 3.

This comment will probably be removed unless criticism is acceptable here.

My recommendation would be to move to Angular or React ASAP.

[Esensats]

Documentation split between Options API and Composition API resulting in, in-comprehensive documentation for both.

Hmm it is true that it's split, but I find it very comprehensive

They like to spend time making their own tools rather than using what is already available and focusing on what actually matters. Example, rollup.js, Vite.

... and now every framework ever uses Rollup and Vite because it's just better than what was "available"

They don't listen

Idk, they seem to explain thoroughly and make strong arguments on why they're not doing that specific feature. It's not "not listening". If it was "not listening" then there wouldn't have been such a long conversation. They already discussed event bubbling of that kind with their team and they should prolly know better after such conversation

"Single-File Components" 🤢

That's the main point of Vue. Vue initially was created as a lighter, quicker, less bulkier, simpler competition to React and Angular, which were very inconsistent in their ways of solving different problems, slow, heavy, not very comprehensible.

TypeScript still a choice in 2023 when it is definitely the better option.

Does it make Vue worse? I don't understand. I love typescript, and Vue 3 is rebuilt on Typescript, you can easily use it, or if you're a casual or a beginner then use regular JS.

Vue 2 was better. I've never used it, but I've come to this conclusion from the old documentation I've come across and peoples thoughts and opinions of it compared to Vue 3.

I used it, a lot, and still do on old projects. No Typescript, no Composition API, magic global variables/properties/methods, magic strings, complete SFC, no intellisense, outdated Vuex, slow outdated Webpack, no clear conventions and boundaries to keep beginners from writing unmaintainable code and so on. It was such a relief when Vue 3 was released.

And also you're contradicting yourself, you said that you hate SFC, don't like non-typescript JS, but then you say that Vue 2 is better.

It's just opinions on a tool mate, don't take it so personally. At the end of the day, you use the framework that brings food to the table. In my city Vue is used more often than even React and therefore has more job listings. It has its own disadvantages, as everything does, and you can cherry-pick them in any framework and make hot takes, but it's objectively not worse than any other framework. You choose to use what you want, but don't misinform other people, potential new developers with opinionated takes that not everybody can agree with.