@theryandreyer Yes. Many times - usually 158 avg for 2:36ish
I can send you strava links if you’re curious.
I have worked to use a higher cadence more often over the years, 158 was already an improvement and today I’d probably race with 165.
@bradford_hardin@JWLevitt@MountainRoche@Predamame “Heavier” has such a weird connotation.
I am 6’4” and at 185 I am still way too underweight.
I’ve been doing 125g for > 4hr activities and it works well to a point. I run much better at 90g for <4hr activities. 125 at high paces just doesnt process/hit right.
@shortwavlabs@zeeg@emberjs File to LOC ratio there is surprising. We’ve got about that many and 3x the code n our main app. Wonder if we can make the MCP server help you refactor.
@shortwavlabs@zeeg@emberjs One: I agree with companies that do this (to a degree).
Two: 2016 had octane - almost everything modern can be used with stuff from that era even without much upgrading because of the extended support for 3.28. Personally I’d just get to 3.28 if you aren’t as a side project.
@shortwavlabs@zeeg@emberjs Qunit does take arrow functions …
I’ve never been stuck because ember is just literally JS and quite literally everything just works with it. Libraries rarely need special bindings.
@shortwavlabs@zeeg@emberjs - routing that’s still on par or better with everything else out there.
- addons (since embroider) and components (since template tag) are always explicit
- qunit still the best testing library out there
@shortwavlabs@zeeg@emberjs Data says most ember apps are running 4.x+
We do look at the data fairly regularly to see where we can eliminate upgrade cliffs
@robboclancy@mateusjatenee Honestly would take too much effort to list the thousands of things we’ve done in the last decade since glimmer. Narrowing to just a few major hits of the last 2-3yrs: Types, vite, WarpDrive, template tag, fn helpers, renderComponent, route components, volar/ember-tsc
@robboclancy@mateusjatenee It’s not though. The only era it was held back like that was during the LinkedIn hijack. Once we got past that it started moving well again.
@rickyfm@nullvoxpopuli it’s there to be a generic opt out but no one is actually sure when that’s needed. You certainly don’t need it to be able to disconnect render of a subtree for a transition or while deprioritized.
@rickyfm@nullvoxpopuli The APIs you listed to disable reactivity are fundamentally a different concept and for a different purpose than a value simply not being reactive in the first place. And it’s a concept on which there’s a lot of disagreement as to whether it’s actually even necessary in the spec