opencode honestly is such a chad for this

ran svelte-bench on apple's new 3B parameter on-device model... doesn't look like we'll be vibe coding with iPhone-local inference just yet 😭

wasn't sure if mythos was gonna live up to the hype.. but hell yes it peli-can! at this rate we will have to consult ornithologists to determine model progress in a few months from now.

Could you please print cute sushi faces onto my coffee's foam? Thank you

The new waymos are looking way too cute

Google I/O Day 1 - the influencer to engineer ratio at this event keeps rising, so I decided to switch camps and give the influencer thang a try

will literally circumvent the earth this May. Leg 1/5: Tokyo to Seoul, first time in an A380. my connecting flight is not before the morning so of course I'm going into the city for some samgyeopsal!

fun chatgpt behavior: if you mix languages in your prompts often enough, it’ll eventually start babbling back like a true polyglot

Next up, we have @wattanx.dev with a delightful talk on designing "pleasant animations". A very practical guide with tons of tips and tricks I can't wait to apply at work starting tomorrow!

having never built a design system myself, this talk on creating & maintaining design system documentation by @takanorip.com was really eye opening! I wonder if a storybook plugin to generate versioned documentation for non-ui parts of design systems could be useful..

@sakito.bsky.social opening up #fec_kansai with a meta talk on why we follow frontend technology and go to conferences. For me personally it's always the hallway track that makes offline conferences special

In Osaka for Frontend Conference Kansai over the weekend! #fec_kansai

Felt creative after watching an episode of "the bear", so I made a scallop carpaccio with grapefruit & papaya!

and newly connect with so many cool folks! Non-exhaustive list of folks I'm lucky to have met at VueFes: @danielroe.dev sorry 'bout your umbrella, @rebaar.com your powerbank saved me! @danabra.mov enjoy kyoto! @hiogawa.bsky.social thanks for vitest! and yes, that's me posing as a vue-themed drink 😅

@kazupon.dev & @vuefes.bsky.social staff team, y'all did it again! What a beautiful event - filled to the brim with talks from the leading edge of web development and lovely people ❤️ Grateful for getting to re-connect (@pilcrowonpaper.com, @hirok.io, @sxzz.dev, @dominikg.dev & the Svelte Japan crew)

Last but not least, we had @antfu.me test the capacities of the venue by drawing a huge crowd for his first ever conference talk in Japanese! His presentation envisioned a future where Vite DevTools make it trivial to introspect your applications - powered by an ecosystem built on DevTools Kit

Tucked away in a small room on the lower floor I listened to a hidden gem of this conference: my friend Yogo's talk on the web audio API being formally trained as a composer at Tokyo Geidai, he showcased the ins-and-outs of using filter nodes to manipulate sound on the web - fantastic talk!

multi-track conferences sadly come with some overlap between talks, so I had to sneak out from the panel to catch the next talk on how rust-based tooling runs in JS environments by my friend @ssssota.bsky.social! A very timely talk lifting the mystery behind all those rust tools showcased at vuefes!

and how could I forget these three brilliant minds engaged in an debate on the next ten years of frontend development: @dominikg.dev, @danabra.mov & @evanyou.me With a diverse set of opinions from cautious AI optimism to worried scepticism this panel discussion had just the right amount of spice 🌶️

Next up: Ogawa Hiroshi's talk with a walkthrough on what happens under the hood of vitest, explaining different concurrency modes & the history behind them. I learned a bunch of stuff, for example that the "forking" in test orchestration simply means spawning subprocesses!

Johnson Chu on the journey of the vue dev tools, from vetur to volar, to takeover mode & then onto multiple versions of hybrid mode. very impressed at the drive to not compromise on DX or performance & very excited for what can be built on the language agnostic volarjs! True dedication ❤️

lovely talk by @danielroe.dev, despite him casually dissing svelte stans 😜 three words of advice for how to prepare yourself for the next 10 years in web development: trust yourself, embrace tools & community (paraphrasing, I hope I didn't totally miss the point, but then again I'm into svelte)

Last but not least we have a LT from @yuki-ishii.bsky.social, the man who put this fantastic event together! Observability in remote functions with OpenTelemetry & @sentry.io in SvelteKit! Great refresher on @stracke.tech's amazing talk at SvelteSummit

@yamanoku.net with a LT on recent developments in a11y warnings in svelte! (A follow up to a talk by him at an earlier SvelteJapan meetip) Really looking forward to his talk at @vuefes.bsky.social tomorrow as well!

#SvelteJapan is honored to have @dominikg.dev as a guest speaker! Really going into the nitty gritty & behind of SvelteKit's new remote functions My favorite part: in his talk, he was able to directly address concerns about n+1 issues with "query" voiced in an earlier talk by showcasing ".batch"

Next up, we have mkazutaka with a comparison of superform & the form remote functions! Also: Always happy to hear about a CTO putting his weight behind svelte!

The next talk by @svelte.dev maintainer @baseballyama.bsky.social showcasing some of the insanely useful linting rules helping you write more correct & maintainable svelte 5 code! with a small excursion to Svelte MCP & how it uses svelte eslint & the raw ast for improving LLM output (with demo!)

Hitoshiro-san, who considers herself a hobby engineer, asking which layer "+page.server.ts" would fit in in classical domain modeling! if you ask questions like that, I'm pretty sure you have transcended "hobby" engineering and can consider yourself a pro 😂 Funny, clever & thought provoking talk

Let's go!! #SvelteJapan offline meetup at deno's beautiful shibuya office (40th floor!!!)

- frames as an RSC "alternative" seem like a request waterfall footgun? - the context API basically guarantees tight coupling of components - this "interval with dynamic time" example by ryan himself really drives home how bad the DX becomes without reactivity.. manually diffing state, really? 4/5