Atila
@atila.io
2.5K followers 320 following 600 posts
@neon.tech | @solidjs.com | GDE Web Tech ↳ atila.io/youtube Puns are usually intended.
Posts Media Videos Starter Packs
atila.io
You were here, my friend!

w/ @thealexlichter.com
Atila and Alex with Patak’s nametag
Reposted by Atila
lianghai.dev
Solid advice from @atila.io at #ViteConf.
atila.io
@pi0.io on stage at @viteconf.org 🔥

NITRO V3!!!!
atila.io
that's awesome to hear, Gil!!

The project I spend most time on is neon.new
But my team is responsible for finding features users are craving and what they need to build cool things (at whatever scale), so send **all** your feature requests, comments, complaints!
Neon Launchpad
Instantly hosted Postgres. No config, no account. Perfect for OSS platforms, quick tests, and AI agents.
neon.new
atila.io
Seeing @neon.com Launchpad mentioned on stage at @viteconf.org during @biilmann.blog 's talk was mind-blowing to me

That's what we built to power @netlify db init and neon.new

Very proud to have so many happy users on something I help building 🚀
Matt Biilman talking about Neon Launchpad on ViteConf stage
atila.io
💯

To be fair, there’s been public debates between some core members of each side

But no animosity, it was more a “agree to disagree” kinda thing

I haven’t watched the stream, but seems like there was a U-turn on their side. That will definitely reignite some old debates (in a healthy way 🤞)
atila.io
Moreover, @ryansolid.bsky.social has actively helped every framework under the Sun to implement signals

So no, Solid has problems with no one
atila.io
There isn’t beef at all.
Solid advocates a lot in favor of signals and React has traditionally been against them. That’s all.

@solidjs.com ‘s team generally likes everyone using signals and we’re ready to help. The idea is to always pushing the community forward and upwards!
atila.io
he needs a squiggle moustache
atila.io
Starting off this crazy week

1st @neon.com offsite 🇪🇸
then @viteconf.org 🇳🇱

Meeting a bunch of cool people in a very short amount of time 🔥
Reposted by Atila
danielroe.dev
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
atila.io
Atila @atila.io · 13d
After ~12y in Germany, I renounced that feeling.

Instead of fitting in what "locals" call "Berliner", I have decided I now extend the definition

imho, much happier mindset. But prone to conflict with some groups of people (who I don't really care about)
atila.io
Atila @atila.io · 15d
🛟 and if you're one of those people who already built integrations, reach out!

I'd love to hear your feedback and build features that you actually need

neon.new
Neon Launchpad
Instantly hosted Postgres. No config, no account. Perfect for OSS platforms, quick tests, and AI agents.
neon.new
atila.io
Atila @atila.io · 15d
Nice Friday finding is that there are quite a few folks building templates with @neon.com Launchpad

💡 PRO TIP

add the `--ref` flag so we can identify single usage and get some cool stuff on your way
atila.io
Atila @atila.io · 16d
Oh no!! I hope things are alright on your end

So sad we aren't going to meet in person
You'll definitely be missed over there 🫂
atila.io
Atila @atila.io · 21d
Blueprint track has hit the ground running with @pkozlowski.bsky.social and @danielroe.dev here at @wts.rocks

Coming after the coffee break is yours truly.
Talking about SPAs, MPAs, @solidjs.com Start, and @tanstack.com Start

See you soon!!
atila.io
Atila @atila.io · 24d
"ready for" means it can / should be used
"workarounds exist" means there are improvements needed

So, IMHO, both are true

Categorically saying "not ready for" implies there are better options and advises people to look away.

So, while I agree with improving ergonomics, I disagree with the tone
atila.io
Atila @atila.io · 29d
Getting your data properly wired up is how your up becomes truly reactive and declarative, otherwise you're just imperatively triggering updates
atila.io
Atila @atila.io · 29d
Signal is the data coming in.

Subscriber is every part of your app that depends on this data.

Derived signal is a read-only computation that uses your data (signal)

Effect is one or more side-effects outside your JSX block that will trigger once one or more signals are updated
atila.io
Atila @atila.io · 29d
Signals aren't about performance
Push/Pull architecture forces better data understanding

🛰️ Signal: state getter/setter
📡 Subscriber: anything w/ a signal getter inside
💻 Derived Signal: compute + getter from other signal,
🤖 Effect: a side-effect from one or more signals,