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

VueJS turns 10 years old

twitter.com

Post reply on HN
Print view View original

41–50 of 97 posts

Re: VueJS turns 10 years old

#41

Post by jgalt212 »

todd3834 wrote: post #37
synergy20 wrote: post #33

This is an amazing project, it tells yet another story how one guy can start a project ended up challenging big companies like Google(Angular) and Meta(React). While React is adding all those complexity by SSR and server component etc these days, Vuejs separates them wisely, if you need just the original SPA, use vuejs as-is, if you want SSR, add Nuxt. I am moving back from React to Vuejs after realizing how heavily…

I build React apps without SSR all the time. What has changed in React besides optional support for it?

If the preponderance the documentation and examples favor SSR, I can see what the poster is speaking of.

Re: VueJS turns 10 years old

#42

Post by samwillis »

I think it's a shame the reactivity/signals system from Vue 3 wasn't broken out as a separate project under a different name. They had so much success with building Vite as a separate project, and the reactivity system they built for Vue 3 is so good it warrants the same attention.

It can, and is, used outside of Vue, see Alpine.js, but it's adoption would be so much greater if it was packaged under its own name.

There is this project that even combines it with react: https://github.com/antfu/reactivue.

I wish we had slightly looser compiling between templating and reactivity systems...

Re: VueJS turns 10 years old

#43

Post by qudat »

impulser_ wrote: post #40
synergy20 wrote: post #33

This is an amazing project, it tells yet another story how one guy can start a project ended up challenging big companies like Google(Angular) and Meta(React). While React is adding all those complexity by SSR and server component etc these days, Vuejs separates them wisely, if you need just the original SPA, use vuejs as-is, if you want SSR, add Nuxt. I am moving back from React to Vuejs after realizing how heavily…

Svelte is not SSR first. Svelte has nothing to do with the server. There is no server related code in Svelte. Svelte is a UI library/framework/language w.e you want to call it. SvelteKit can be bundled with server code, but it's just as easy to bundle it without any server code. SvelteKit is essentially just a Vite plugin. You can add adapter-static and have to bundled as an SPA and not change anything with you code…

You haven’t described anything different from what the OP is saying: the main dev behind svelte now works for a company that wants you to use SSR for all your projects. That absolutely impacts feature development to favor sveltekit. The same thing is happening with react.

The same thing is happening with deno as well: most active dev is with deno deploy.

VC has infiltrated open source development and is driving how features are built. Not saying it’s necessarily bad but it does change the incentive structure.

Re: VueJS turns 10 years old

#44

Post by jacobr »

ipaddr wrote: post #38
Hasu wrote: post #23

Earlier quoted context omitted.

I'm genuinely curious - what features does jQuery have that make it better than modern vanilla JS? Back in the day the vanilla DOM APIs were bad, so jQuery was great, but I haven't felt the need to reach for it in ages.

Better and shorter syntax, plugins, ecosystem. Hide Show ``` $(".box").hide(); $(".box").show(); vs document.querySelector(".box").style.display = "none"; document.querySelector(".box").style.display = "block"; ``` Both work. The first is more clear

```

const $ = document.querySelector.bind(document);

$('.box').hidden = true;

$('.box').hidden = false;

```

Re: VueJS turns 10 years old

#45

Post by gherkinnn »

synergy20 wrote: post #33

This is an amazing project, it tells yet another story how one guy can start a project ended up challenging big companies like Google(Angular) and Meta(React). While React is adding all those complexity by SSR and server component etc these days, Vuejs separates them wisely, if you need just the original SPA, use vuejs as-is, if you want SSR, add Nuxt. I am moving back from React to Vuejs after realizing how heavily…

React with SSR is fine. Astro and Remix both do it well and it's effortless.

Vercel pushing Next's terrible app router has a VC stink to it. That's the only way I can explain their downright awful solutions.

Re: VueJS turns 10 years old

#46

Post by synergy20 »

impulser_ wrote: post #40
synergy20 wrote: post #33

This is an amazing project, it tells yet another story how one guy can start a project ended up challenging big companies like Google(Angular) and Meta(React). While React is adding all those complexity by SSR and server component etc these days, Vuejs separates them wisely, if you need just the original SPA, use vuejs as-is, if you want SSR, add Nuxt. I am moving back from React to Vuejs after realizing how heavily…

Svelte is not SSR first. Svelte has nothing to do with the server. There is no server related code in Svelte. Svelte is a UI library/framework/language w.e you want to call it. SvelteKit can be bundled with server code, but it's just as easy to bundle it without any server code. SvelteKit is essentially just a Vite plugin. You can add adapter-static and have to bundled as an SPA and not change anything with you code…

Svelte has no routing for client-rendering, and itself recommends everyone to just use SvelteKit as boilerplate, which is SSR-first.

I spent two months with SvelteKit for a SPA project,it did not fly, the SSR-first (e.g. documentation etc) made CSR-SPA a second class citizen plus added unnecessary burden for those who does not need SSR, no it's not as easy as just "setting this flag you will be golden for CSR".

If I need SSR sometime, I might as well just do Django, Rails, Laravel etc which are solid. Please give me a true SPA as it used to be, and make SSR optional instead of the default.

Re: VueJS turns 10 years old

#47

Post by impulser_ »

qudat wrote: post #43
impulser_ wrote: post #40

Earlier quoted context omitted.

Svelte is not SSR first. Svelte has nothing to do with the server. There is no server related code in Svelte. Svelte is a UI library/framework/language w.e you want to call it. SvelteKit can be bundled with server code, but it's just as easy to bundle it without any server code. SvelteKit is essentially just a Vite plugin. You can add adapter-static and have to bundled as an SPA and not change anything with you code…

You haven’t described anything different from what the OP is saying: the main dev behind svelte now works for a company that wants you to use SSR for all your projects. That absolutely impacts feature development to favor sveltekit. The same thing is happening with react. The same thing is happening with deno as well: most active dev is with deno deploy. VC has infiltrated open source development and is driving how f…

What feature was added to SvelteKit on the behave of Vercel?

Re: VueJS turns 10 years old

#48

Post by y-c-o-m-b »

I've been in FAANG for a couple of years now and stuck in React world unfortunately. Prior to that I had to use Angular, which imo was even worse. I've had a couple of short opportunities to use Vue professionally in an enterprise application though and damn I loved every second of it. Vue is still my favorite by far. It's just so elegant with its simplicity, it allows me to actually focus on the app and not any bullshit cognitive overhead dealing with state or weird incoherent syntax (looking at you, Angular). I wish there was a larger adoption of Vue.

Re: VueJS turns 10 years old

#49

Post by impulser_ »

synergy20 wrote: post #46
impulser_ wrote: post #40

Earlier quoted context omitted.

Svelte is not SSR first. Svelte has nothing to do with the server. There is no server related code in Svelte. Svelte is a UI library/framework/language w.e you want to call it. SvelteKit can be bundled with server code, but it's just as easy to bundle it without any server code. SvelteKit is essentially just a Vite plugin. You can add adapter-static and have to bundled as an SPA and not change anything with you code…

Svelte has no routing for client-rendering, and itself recommends everyone to just use SvelteKit as boilerplate, which is SSR-first. I spent two months with SvelteKit for a SPA project,it did not fly, the SSR-first (e.g. documentation etc) made CSR-SPA a second class citizen plus added unnecessary burden for those who does not need SSR, no it's not as easy as just "setting this flag you will be golden for CSR". If I…

SvelteKit is the "router".

We use SvelteKit for a internal application that we embed into a Go binary. It as simple as adding adapter-static as the adapter and not using .server files.

You can use SvelteKit the exact same way as the API for server and client are nearly the same. Load function on the server work the same as the Load function on the client expect for where they are called.

What problems did you have?

Re: VueJS turns 10 years old

#50

Post by simultsop »

tinco wrote: post #28
MatekCopatek wrote: post #9

Earlier quoted context omitted.

As someone who started using Vue before 1.0, I find that characterization unfair. The overall API didn't change much from 1 to 2. 3 was initially going to be a big change, but after a lot of community resistance, they decided to make the reworked API entirely optional so people wouldn't be forced to make changes. AFAIK this is still the case and the classic variant (Options API) is still fully supported.

I fell for a feint though. Reading their docs it seemed like they were going to go in the direction of class components with attributes (class decorators). So we built our app for that, thinking we'd be future proof, but alas the community went 180 degrees the other way, and our Vue 2 app became super hard to upgrade to Vue 3.

Without more context can't comment on your upgrade process. But as others stated above, there's not much difference betweeb 2 and 3, except you do not get composition api on a v2 project, while you can use composables but can't go full composition api and have to stick to options api. Other than that most of v2 code would work on v3.
Post reply on HN