I went through an extended project to make it faster and wound up with a loop handlebar for body position, replaced the wheelset to move from 355 to 406 for tire selection and did the drivetrain at the same time to accommodate a 9-32 cassette. Between the wheels and the sub-11 tooth sprockets I can pedal up to ~26mph instead of ~20mph on the stock setup (good enough) and the low end is about the same. It doesn't perform like a race bike but it's pretty close to an endurance road bike. I do 20 mile rides a couple times a week on it and I've done a couple centuries.

The Birdy is my main bike but I'm a folding and recumbent enthusiast in general. The addition of the fold or moving the cranks in front of the rider means the obvious solution diamond frame doesn't work and I like seeing the creativity of the solutions. I've also owned a Xootr Swift that I gave away to my nephews, a Bike Friday Sat-R-Day folding recumbent for riding slowly in the parks, and a Baron Optima lowracer recumbent that I prefer for rides over 90 minutes.

As for living with yourself:

Find some sort of exercise you don't mind doing and make it non-optional. The goal isn't to go all out, just get your heart rate up for half an hour. You won't want to do it sometimes but you still have to go. You can do a crappy job at it and slack off for a day or two but you have to go out. For me this is riding a bike.

Otherwise it's good to be absorbed in something. It's not the same feeling but there is intrinsic satisfaction in learning / building / experiencing things.

As near as I can tell, people generally type at similar speeds regardless of layout. If you're aiming for speed typing [1], I can see it making a difference, but chances are you're not going to see much of a difference. I type on an alpha-thumb layout (Hands Down Vibranium, the R key is under my left thumb) on an ergo keyboard. It's like using a fountain pen versus a cheap ballpoint or a nice mechanical keyboard vs a membrane keyboard. The experience is nicer but it's not a fundamentally different process. Being on a weird setup, I was concerned about "what if my keyboard breaks", "what if I'm on a public computer", etc and the solution is just to not forget qwerty. I use the laptop keyboard every other day or so for something short like a comment and it's fine.

What my personal setup does let me do is have my wrists in a neutral position with my arms resting on chair armrests and no active muscle effort. Between the efficient layout and small keyboard I never need to move my hands at all. This means that my wrists are just as well positioned after 12 hours as they are at the start and that's what has been letting my stress injuries recover.

[1] https://www.reddit.com/r/KeyboardLayouts/comments/1lfu1xt/fi...

This got widely reported but there doesn't seem to be any source. I'll reference this video [1] to cover the claim along with a comparison to industry projections. Apologies for the video link but I don't have an article handy that addresses the topic as directly.

[1] https://youtu.be/KjiqqafD_0w?t=861

[1] https://github.com/WebAssembly/wasi-sockets

The Clojurescript community was the first group adoption of React outside Facebook (early on they had community news blog post and mentioned it) but that because the React rendering model fit the Clojure data model. I was active in the NYC Clojure meetup at the time (Rich was from upstate and would only come in for big announcements, and David was local) and we had 4 or 5 months where there was active discussion among the web devs after the talk on how to make cljs actually work. My memory is Brandon Bloom is the one who made the React connection. David picked up the idea and promoted it to the wider community.

I had the idea that the best position for long sessions would be the most relaxed one so I put my hands in my lap on top of a lapboard (old Wacom tablet) and tried to put they keyboard halves under my fingers. I cut up a shipping box for the tenting stand. It took me eight iterations with three fresh starts but doesn't take that long with cardboard and tape. Stick the keyboard onto the stand with double sided tape, fill the cardboard pyramid with change for weight, and it's been like that for eight months. I'll come up with a more permanent solution at some point but it's working well so I'm not in a hurry.

The positioning was mostly about getting the wrists straight with the keyboard halves in-plane. The in-plane part was, naturally, the tricky part and that was mostly about getting the pinky corners set and then small adjustments until the index corners felt good. I have it set so perfectly aligned requires me to slightly lift my arms off the armrests which prevents sore spots on the forearms. At rest with the sides of my palms on the lapboard my fingers are off to the side of the keys but I can still type.

> I've seen some members of the erg keyboard community design and print their own pcbs based on their hand dimensions

I follow the reddit community and see those as well. Someone started up a business selling fitted keywell boards (Cyboard) but the general consensus seems to be that the glove80 is good enough. I have some patches on my local ZMK (mostly changing chord detection) but no particular desire to do the hardware side. If I had a 3d printer I might consider it since apparently hand wiring isn't that hard if you have a print to hold the switches.

I'm curious but not particularly enthusiastic about keywells because I find the biggest improvement with a split keyboard is the tenting. My personal setup uses heavy tenting+tilting (basically half of a square base pyramid split on the square's diagonal) with the keyboard in my lap and my forearms resting on the chair arms locks me into a neutral wrist position without any active muscle effort. Keeping a good wrist position through the entire day instead of just the first half makes a noticeable difference.

Finally, I use the neutral thumb keys for shift on hold but I don't use any other thumb holds because I believe it has stress injury risks[1]. They're used for important but relatively infrequent keys: backspace, enter, tab, esc.

[1] https://getreuer.info/posts/keyboards/thumb-ergo/index.html

FWIW, A is dodge for me and V is crouch.

[1] https://foil.zone/ [2] https://www.youtube.com/watch?v=S9z6BP8Y42U

Since the original article is about human power, I'll also link to this foil[3] which is for pump foiling long distance. I had run across the channel well before that and thought his goal for a half hour was goofy when people were getting 90s or 2 minutes so I was quite shocked when it actually got built.

[3] https://www.youtube.com/watch?v=WfJbF0xkUOY

More generally Roc is following in the footsteps of Elm in that it's an exercise in functional language minimalism. I personally like computation expressions but I think they're beyond Roc's preferred feature complexity limit. There are proposals to expand this feature either using a `?` in a `with` section that would allow for Rust-like error handling with `Result`s or a type-dependent version of `!` so the syntax could be used on something other than `Task`s. Regardless, it's expected that the IO use case is going to be the primary use case regardless so I expect they're giving people some time to play around with it and provide feedback before making further changes.

In the case of Roc this is determined by the platform and the platform corresponds to the framework level. A webserver platform is going to have a different set of execution choices than a cli platform or a platform for defining user functions in a db. So I wouldn't expect every application developer to make a platform but it's not going to be a compiler/stdlib only sort of thing.

As for the fractured IO, I'm pretty sure that every single person who has dealt with any functional language is aware of the propensity towards fractured IO ecosystems. The exact details of sharing code across different platforms in a useful way is somewhat hand waved at the moment in that there's a rough, unimplemented plan. I kind of expect that there's going to be some piggybacking on the WASM interface definitions but there are a couple changes around Tasks and the module system that are in the pipeline before that'd come up.

Note: I'm mostly an interested bystander

If you're looking for additional reading then it's arguable that Reacts matches this viewpoint but any web framework from the past few years using signals (re-popularized by Solid) is explicitly this approach. Most frameworks don't opt for graphical node editors and I've never liked the approach but I've seen a number of those as well.

More generally this falls into dataflow programming which has had a number of published papers starting in the late 80s I believe.

If you're looking for a similar computer sciency approach to UI structure you can look up statecharts which is an older idea that formed the conceptual basis for Ember Router and, in turn, most js framework routers in the past decade.

If I'm going to pick a fancy niche frame I don't want to afford I'd opt for a Jones LWB space frame. I'm actually a recumbent rider so the more likely expensive cycling purchase would be a velomobile.

I'm nowhere near an expert but I think most small (or steel) bike brands never moved off english threaded bottom brackets so I think that's mostly a major manufacturer issue. The brakes are frame dependent but calpier and cantilever arms are fairly simple/available or flatmount if discs (ignoring that Shimano just kind of decided they didn't like post mount). Finally, if you're comfortable with (ratcheted) friction shifting then most drivetrain compatibility issues are covered.

The components themselves tend to be pricier since they're targeting a niche market but there are people serving it.

This is a reasonable assumption given what I've described. It's been almost two years but from what I remember the problem was updating what should have been the same reactive binding in two different locations. When trying to debug a problem I was stepping through the code and noticed that the indicies passed to `$$invalidate` were different. Checked for typos and shadowed declarations and found none. Rolled back to checkout and found the indicies matched. In the process of undoing/redoing my conclusion was that the introduction of an unrelated reactive binding was the difference. I could have been wrong; I was pretty exhausted at that point.

> It sounds also like you’re fighting the framework.

Sure. In this case it was getting a big chunk of JSON back from an endpoint I didn't control and trying to use a number of reactive variables to select out pieces for display. I've done similar things in a half dozen other reactive/FRP libraries without issue but I assumed I was off the beaten path in Svelte.

I realize that this is empty complaining about other peoples' hard work. I don't have the code any more and I don't have a reproducible test case so I have no problem with anybody waving this off.