Lightnews — Scholar-powered news

Ryan Carniato @ryansolid.bsky.social · 18h

A lot of conferences going on this week. Join me on stream tomorrow as we talk about it all:
www.youtube.com/watch?v=8bpj...

This Week in JavaScript Conferences

YouTube video by Ryan Carniato

www.youtube.com

1 9

Ryan Carniato @ryansolid.bsky.social · 1d

Received this in the mail today for my son. I see the @solidjs.com mascot is alive and well.

Thanks @davedbase.com!

6 31

Reposted by Ryan Carniato

Dominik 🔮 @tkdodo.eu · 3d

It turns children into siblings 🤯. @ryansolid.bsky.social blowing every React dev's mind with nested data fetching and fine-grained reactivity 🔥

www.youtube.com/live/fnyK-xX...

JetBrains JavaScript Day 2025

YouTube video by JetBrains

www.youtube.com

1 3 34

Ryan Carniato @ryansolid.bsky.social · 6d

Although to be fair my biggest interest here is nested statements, not native control flow. That is just a bonus. More fine-grained solutions don't need state to be owned by components and can nest it at will. Which is powerful because it removes a lot duplication around control flow logic in state.

2

Ryan Carniato @ryansolid.bsky.social · 6d

JSX hasn't proven this isn't needed. You might argue React's model has never been able to leverage this so JSX is perfectly adequate. I think your response is inline with what I'd expect on the React side of the spectrum. This is different enough to feel uncomfortable.

1 1

Ryan Carniato @ryansolid.bsky.social · 6d

The idea isn't making this Solid specific. I'm just pointing out at some point JSX has to evolve if it is going to keep up with other innovations in templating in the space. Those others don't have certain characteristics that JSX has and can't preserve backwards compat. We'd still support JSX.

1 2

Ryan Carniato @ryansolid.bsky.social · 7d

Nested declarations of state need statements in JSX which is basically the problem. With fine-grained components don't matter, so putting createSignal under and if actually can simplify logic and make it more portable. Native control flow was just a bonus. Could help with type narrowing.

3

Ryan Carniato @ryansolid.bsky.social · 7d

Yeah you wouldn't most likely. Would just need to build it out like any other tool chain with its own extension.

3

Ryan Carniato @ryansolid.bsky.social · 7d

The key is the extension isn't JS. This is a different language that happens to be a superset of JS. It introduces new type of block. Could just stop there and not have a `component` keyword and just use the `@{}` on functions too.

1 3

Ryan Carniato @ryansolid.bsky.social · 7d

The best part of the proposal is people can. Each feature is separately adoptable.

1

Ryan Carniato @ryansolid.bsky.social · 7d

Do expressions look like they are never happening. But the templating power is a real thing. Especially for fine-grained systems that could locate state anywhere in the template.

2

Ryan Carniato @ryansolid.bsky.social · 7d

JSX are templates? Obviously I want to use templates.

1 2

Ryan Carniato @ryansolid.bsky.social · 7d

There could be a reference transform for Babel, which then could be used in Vite etc as a baseline. But yes this is a whole other thing so it requires language server, code completion etc..

3 2

Ryan Carniato @ryansolid.bsky.social · 8d

Be honest is this just a bad idea?

Future templating while keeping backwards compatibility with current JSX.

Is this something people would be interested in?

hackmd.io/@0u1u3zEAQAO...

A True Successor to JSX - HackMD

I love the idea of Ripple's templating. Nested statements and the ability to analyze native control flow gives this power that seems incredible.

hackmd.io

10 1 23

Reposted by Ryan Carniato

daniel at ⚡ viteconf 🇳🇱 @danielroe.dev · 8d

this is worth saying:

nuxt is an independent open source project and not directed or owned by any company.

check out github.com/nuxt/governa... for specifics.

you can see the companies which sponsor the project financially on OpenCollective and GitHub Sponsors.

GitHub - nuxt/governance: Nuxt Project Governance

Nuxt Project Governance. Contribute to nuxt/governance development by creating an account on GitHub.

github.com

7 9 150

Ryan Carniato @ryansolid.bsky.social · 8d

I can definitely respect the desire to be principled here. The first thing I noticed is not having all the facts in terms of which projects would be impacted. And ultimately if people are going to arbitrary about it, I'd like to point them at a more sensible line.

1

Ryan Carniato @ryansolid.bsky.social · 8d

My interest is obviously in preserving science and innovation. OSS support is power in the same way as philanthropy is. These projects run independently and do important work. Work that is far more important than who currently sponsors that work.

2 1

Ryan Carniato @ryansolid.bsky.social · 8d

Sorry I don't mean about specifically the Guillermo issue. His last post was about social responsibility, and was being critical of people justifying posting on X because that is where their followers are.

1

Ryan Carniato @ryansolid.bsky.social · 9d

It doesn't even directly impact me but there is so much wrong with that. Obviously nothing in the face of the genocide. But it doesn't make it anymore right.

1 2

Ryan Carniato @ryansolid.bsky.social · 9d

Alright I suppose I'm done then. It just really really irks me how everything gets lumped in with that asshat as you called him. The dedication and passion that goes into keeping OSS takes a big enough toll without this sort of garbage. Then making these projects targets.

1 3

Ryan Carniato @ryansolid.bsky.social · 9d

These jobs aren't normal jobs. They get to work on projects for the betterment of everyone without contributing to the bottomline of the companies that employ them. It isn't about finding 7 positions. It's about finding 7 positions worth of pure charity. In this economy too..

1 2

Ryan Carniato @ryansolid.bsky.social · 9d

When this can have real impact on projects that do important work I will say something. It's hard enough to make a difference.

I'm not saying don't hold Guillermo and Vercel accountable.

1 4

Ryan Carniato @ryansolid.bsky.social · 9d

So in a sense while it isn't impossible to find new Patrons, it takes some doing. The real challenge is this allowed teams to grow in a way they haven't historically. Backtracking on that is basically spells out the end.

2 3

Ryan Carniato @ryansolid.bsky.social · 9d

The alternatives are like Next, where you are ran by the company and part of their roadmap. You can start your own company but then you need to come up with an angle to be profitable. Hard when your software is innately free. And multi-sponsorship is unstable at best. Look what happened to Babel.

1 3

Ryan Carniato @ryansolid.bsky.social · 9d

We can get into the funding models for open source. Maybe I will do a stream about it. The problem is the "patronage model" is probably the best we have right now in terms of balance. It just works a lot better for researchers than it does for production tools, since so dependent on single entity.

1 2