Am on 🦋now!

https://bsky.app/profile/runspired.com

For Bay Area folks: the next Oakland @emberjs
Meetup will be this coming Tuesday, April 2nd at 6pm at Original Pattern Brewing in Jack London Square https://linkedin.com/feed/update/urn:li:activity:7178617583200346112?utm_source=share&utm_medium=member_desktop
#emberdata

On this #PiDay it's important to remember that eating too much pie does not count as the sin of gluttony as the sin of PI is always 0.

@marcoow one thing I think remix and next have been saying a lot lately that I think I’d like to see us start saying with embroider (because it’s true): embroider/ember (the meta framework) is “just a build plugin”

@marcoow what’s also cool about svelte is its current router is the closest to the edge router I intend to ship with EmberData of anything out there so far. Has the ability to handle the full vision even under the hood though sveltekit hasn’t exposed the desired functionality publicly.

@marcoow bindings for everything else is pretty simple. We extracted our reactivity into a small “signals” bit where we intend to either plugin starbeam or expose a config hook for folks to wire up any reactivity primitive of their choosing.

@marcoow kinda excited at the prospect of y’all maybe pioneering the svelte usage. Svelte will have to improve a lot though, it’s the only framework today I fear isn’t good at intercompat due to its reactivity requiring a compiler.

@marcoow tbh I’d argue that any app that uses fetch or a rest API even a little needs everything EmberData provides. And whats nice is we’ve managed that without the weight and with greater flexibility than alternatives like Protobuf, tRPC, MobX, TanstackQuery, or Apollo. And as we get further into the “it’s a data framework for all apps” story I think we’re going to be able to show that off well.

Want faster and more stable parallelized test runs in CI? Add your support to this Chromium issue https://bugs.chromium.org/p/chromium/issues/detail?id=1492377

Recently, I had the opportunity to give a talk on the intersection of complexity, performance, and developer velocity at EmberFest. Some attendees described the experience as "mind-blowing" and reminiscent of a "Matrix-style manifesto." Personally, I just hoped to put the seeds of some ideas out into the world.

https://www.youtube.com/watch?v=DNZ6a0v-VCk

@chriskrycho @locks happy to anytime. 1:20 is pretty comfortable for me so could get you there smoothly

@roguelazer this isn’t template-lint. It’s a separate project called lint-todo that it sounds like the app you’re working on has configured.

Latest #emberdata 5.4 Beta has some secrets 👀

👋 mostly popping in to say you should try threads. Because while I was hopefully for Mastodon the community here never grew beyond a tiny subset of something already niche. Threads is hopping.

@nullvoxpopuli @tb I think there’s some folks that just are mentally stuck. If you don’t want change the only acceptable migration path is to keep doing what you’ve been doing and that won’t fly. Model/Adapter/Serializer/Transform were always a major mistake as paradigms.

@nullvoxpopuli @tb broadly though confused by TB’s statement. EmberData has extensive docs and examples on all the new stuff.

@nullvoxpopuli @tb yeah all deprecations have a guide. The RFCs contained the guidance just needed ported. I’d doubt most folks who are on 4.X have much trouble reaching 5.X

2.X and 3.X users are those that it’ll be hard to create paths for, but I suspect by 5.4 the case is going to be so compelling no one doesn’t try.

Published a blog post detailing what’s up next for EmberData and discussing what was delivered in 4.x

https://blog.emberjs.com/ember-data-5-x-update-2023-04-15/

There’s 2 key items not on the tracking list (so 101 total to ship EmberData 4.12) but we’re 80% of the way there and it’s gonna be a fun final push this week to get all the way. https://github.com/emberjs/data/issues/8086

And yes, to ship 4.12, because 5.0 will simply remove deprecated code. More importantly: shipping a very robust v2 cache and RequestManager implementation Pre-5.0 is paramount to giving folks a broader selection of migration paths from 3.x to 6.x so that no one gets stuck.

In 2019, trains in the US traveled 777 million train-kilometers and experienced 1,338 derailments.

The same year trains in the EU traveled 4.5 billion train-kilometers and experienced 73 derailments.

Japan: 2 billion train-kilometers and 9 derailments.

https://www.cnn.com/2023/03/30/us/raymond-minnesota-train-derailment/index.html