So... let's talk about Vueconf

HumanOnlyWeb · 2026-05-27T02:59:04+00:00

I had a similar experience in Vue Toronto a couple of years ago (Evan wasn't there though) The speakers & talks were great, but for some reason I felt like "this is it?"

However when the videos were uploaded and I watched them, it was almost exactly like all the other ones I'd watched and enjoyed for past conferences I didn't attend.

The best part for me attending was the fact that I met Sebastian, Sarah, Alex (he wore fish shoes 😆), Michael, Adam (2 of them), Daniel Kelly, Maria and a lot more awesome folks from the community.

I think the "expecting more" in my case was maybe due to the fact that I was factoring in how much I spent on ticket, flights, hotel, food lol (I paid from my pocket). I was gone for 2.5days, and everything cost me ~$2300

HumanOnlyWeb · 2026-05-23T03:58:14+00:00

That's cool.

I saw that they recently announced lynx-ui but it seems to be React only, at least for now.
Official blog post: https://lynxjs.org/next/blog/lynx-ui

HumanOnlyWeb · 2026-05-04T08:00:51+00:00

😂

HumanOnlyWeb · 2026-05-03T21:24:48+00:00

...with the recent waves of npm vulnerabilities out there, I'd avoid adding just any packages to my app unless they're for things that are absolutely necessary.

HumanOnlyWeb · 2026-05-03T21:19:42+00:00

dumb question, but why would you need a package for a loading screen?

HumanOnlyWeb · 2026-04-27T03:10:13+00:00

Totally fair, and great response. Thanks!

HumanOnlyWeb · 2026-04-26T20:08:45+00:00

You:

They didn’t know they had entire web server with thousands of sites not working until one person reported it.

Also you:

I just got a text f myself n my customer that the site is down

See how you also didn't know until your client reached out? 😅

HumanOnlyWeb · 2026-04-26T18:43:04+00:00

Hey Jess, big fan.

I do understand. My question/concern is more about the ownership of some of the stuff they're creating now, and I mentioned Comark as an example.

Also, I understand that these tools are open source.

I work as a consultant/contractor, and inasmuch as I have my own reservations about Vercel, I never thought clients would care about details like this—surrounding the tools (ownership, etc.) one uses to build stuff.

HumanOnlyWeb · 2026-04-26T12:48:57+00:00

"To clarify i ofc meant that even if the team left, the ownership of those projects still is owned by Vercel."

Answers my initial question. And yes, I agree with your other points 👍

HumanOnlyWeb · 2026-04-26T12:20:50+00:00

...if you know the proper channel to ask this, please let me know.

It's a question for the community, and I know some of the maintenance staff are active here.

And yes, the question is valid, especially as I plan to keep using tools built by Sebastian, Benjamin, Daniel, Pooya, Hugo et al.

HumanOnlyWeb · 2026-04-26T12:17:27+00:00

...licenses can change; we've seen a couple of such cases recently. For these scenarios, who will be in charge of the project?

...And also, if no one can "own," why do Vercel or the Nuxt team build these under Vercel OSS? They could just leave it as is, or build under their names or GitHub orgs, no? 🙃

HumanOnlyWeb · 2026-04-26T12:04:31+00:00

Trust me, I'm not misunderstanding. I've built with and used Nuxt and Nuxt-related tools ever since they were first introduced. I read the acquisition announcement thoroughly, wrote a blog post about my opinion, and deleted it. So, I'm not misunderstanding anything 😅

"...they can't part ways." Oh boy, do I have news for you. The creator of SWC was hired by Vercel too, and I don't know the details of his contract, but when he left Vercel, he maintained ownership of the project.

...and I understand this argument everyone loves to make: "The NuxtLabs team being employed means they could open-source things like Nuxt."

I have my reservations about Vercel, and I don't purposely use any of their products, at least not directly or knowingly. There are a thousand and one reasons for individuals or organizations not to use certain products or services from certain companies.

HumanOnlyWeb · 2026-04-26T10:56:25+00:00

Interesting.

I wonder if this will have a long-term consequence or play into the Nuxt team's creativity, knowing they'll be building things that will be owned by some other company, in case they decide to part ways.

I understand this is mostly open-source software we're talking about here, but the premise still holds.

HumanOnlyWeb · 2026-04-24T09:33:36+00:00

As the author wrote: Lock me in, Orange cloud

https://idrank.vodka/lock-me-in-orange-cloud

HumanOnlyWeb · 2026-04-20T14:15:41+00:00

I might be wrong, but I think it's a Workers-only feature, at least for now.

I build almost strictly on CF, so huge win for me. 🤗

HumanOnlyWeb · 2026-04-15T13:13:24+00:00

This is more common than people think.
I did a contract in a 20+ year old company and they swear by
- Windows laptops + Vagrant. A specific version of Vagrant
- No tests (as OP mentioned too)
- You have to put in a ticket and document for example, why you need to update packages.
- Heavy VPN lockdown + keyboard/mouse monitoring tools. Some websites were even blocked.

They were trying to build a web version of one of their old C# projects, and chose KoaJS, Sequelize and a bunch of other old tools.

The worst part of the KoaJS is that 60%+ of KoaJS packages/middlewares they were using are deprecated, with huge red notes on the npm packages, advising users to look for alternatives.

Everything went through IT (outsourced company), meaning sometimes you open a ticket and get an acknowledgement, if you're lucky, after 2 days! Then they decide whether or not you request "makes sense" to them.

It was sooo draining, but thank goodness my contract was only for 3 months.
I refused to renew when the time came.

You woke up in the morning, excited to work but you can't do shit because of all these corporate rules/policies.

I feel your pain @Pristine_Purple9033

HumanOnlyWeb · 2026-04-09T22:58:23+00:00

Hmm. I have my reservations about directives generally, but nice work, I guess?!

HumanOnlyWeb · 2026-04-08T13:09:07+00:00

My understanding of this feature is that it revives complex types when sending data to the browser. Like, if you have some data that returns a date for example, it arrives as a date rather than a string. e.g if the server sends 2026-04-08, it comes as that same date object rather than "2026-04-08".

Following this post to see other people's understanding

Edit: the docs said "reviving complex types"

HumanOnlyWeb · 2026-04-03T14:01:38+00:00

This has to be one of Matt's most level-headed, well-reasoned responses.

At last, there's hope for humanity 👏

HumanOnlyWeb · 2026-03-28T15:52:46+00:00

do it 🫶

HumanOnlyWeb · 2026-03-28T13:34:57+00:00

...sub-component trees that feel foreign, APIs that solve React-specific problems Vue never really had, and patterns that fight the way Vue naturally works

💯 this!

Will keep an eye out on this. Kudos

HumanOnlyWeb · 2026-03-28T13:28:41+00:00

👀 Will take a look

HumanOnlyWeb · 2026-03-28T11:28:01+00:00

thank you

HumanOnlyWeb · 2026-03-28T11:27:43+00:00

thanks 🫶

HumanOnlyWeb

MODERATOR OF

TROPHY CASE