Software Dev, mostly in JS, Python. Fan of Elixir, Zig, Nim, Rust, Go. I like Linguistics, Monster Hunter 🦖, Final Fantasy, Ace Attorney, Futurama, et al.

Australia
Joined September 2013
No clue how I achieved this (maybe rogue Google translate or localisation error?) but somehow through switching documentation versions on @kotlin 's Ktor I ended up with the site renaming itself to "Which" 😅 But just made me wonder if "Ktor" is an intentional Slavic pun!
I was really excited about the CloudFlare support for 2 seconds! Pity about the Rust migration, I guess the CLI will just be extremely fast and not blazingly fast :( On a more serious note, it's interesting to see them move from CDK to Pulumi.
it's officially not vaporware! sst ion is now generally available i sat with a documentary crew to have a no BS, raw, unfiltered conversation about it it came out kinda weird, link in reply
1
Christian Meredith retweeted
Hear me out: Snake, but instead of snake it's Shai-hulud munching harvesters :D
And while I'm singing its praises, I'm liking the effort a lot of libraries have put in to having a consistent "brand" with Solid. It feels like there's a lot of enthusiasm or solidarity (hah).
Really impressed by how far the Solid ecosystem has come in a short time. There's an icon library (solid-icons), a drag and drop library (solid-dnd), there's a port of MUI (called SUID), the Solid Router supports data loading like React Router, it's neat! solidjs.com/ecosystem
Christian Meredith retweeted
Sharing an example code of `resolve` based on the ECS architecture using Donburi. `resolv` is a convenient library for collision detection and physics. #ebitengine #Golang #IndieGameDev github.com/yohamta/donburi/t…
Christian Meredith retweeted
I love how it always finds a way to talk about the peregrine falcon
38
46
2,688
This was a fun ride 😅
Stewart Butterfield resigns from Yahoo June 13, 2008
On a related note, shoutout to #Deno for great interoperability with NPM and to #AlephJS for carrying on that spirit. And likewise, to #TailwindCSS (and inspired relatives) v3 for being basically usable with, well, everything with a filesystem 😅
Replying to @Ceige_M
Re Deno, the VS code extension was great, very fast, except to cache newly added packages the first time which is a different workflow experience to Node. Import maps are excellent, I can see using these to replace dependency injection while still having testability.
The Vue support for Aleph is both surprising and appreciated, but I think the proverbial camel* that broke the straw's back was that Vetur (Vue ext.) and the Deno extension in VS Code were not on speaking terms thanks to TypeScript. The NPM ecosystem very much expects Node 😅
Re Deno, the VS code extension was great, very fast, except to cache newly added packages the first time which is a different workflow experience to Node. Import maps are excellent, I can see using these to replace dependency injection while still having testability.
Gave @alephjs a try in the office today, some blockers* but excited about a lot of the ideas. Feels like a future highly configurable generic & serverless Next JS competitor. *fetching from sibling API routes, exception causing the app to crash, import meta issues, etc.
1
1
Someone using @sveltejs needs to check their CI/CD pipeline 😅 #npmtrends
(which is probably some as of yet unidentified blend of Nim, Kotlin, Swift, and that classical chinese esoteric programming language)
I'm waiting for the 4th secret future universal language
Learn rust, go, and typescript and you will be future proof
I missed so much this month. Nuxt 3 and Nitro look really fun to use. I think Vuetify 3 is also available now too, and Tailwind has a Nuxt 3 guide already. And someone's maintaining a nuxt-auth port of NextAuth and there's nuxt-session too, both v3 compatible.
It's time for 3.0 ✨ nuxt.com/v3
See the thread for the things Dominic contributed to - quite a lot!
A few days ago I was was uninvited to a React event because the organisers thought I was "kicked" off the React Core team. I asked why they thought that was the case and they assumed I left the team because I hadn't done anything in my time on the team.
(there's 2 separate links btw: the one in my tweet is a link to the author's previous blog post, not the one the author is linking to)