Hacker Newsnew | past | comments | ask | show | jobs | submit | grayrest's commentslogin

> I'm sure I could learn to be slightly faster on dvorak/colemak

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...


> CATL is claiming mass production of their sodium-ion batteries starts in December, with a target price of $10/kWh.

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


You're right, I can't find any primary sources for this number. Yahoo[1] reports this number and attributes it to Bloomberg NEF but I can't find an actual article from Bloomberg with this number, or any actual target number in it.

[1] https://www.yahoo.com/news/china-10-sodium-ion-battery-16505...


Opening a socket would fall under WASI[1].

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


Rich Hickey had nothing to do with it. He did put a lot of the initial work to get Clojurescript up and running but for many years the majority of cljs maintenance and shepherding was done by David Nolan. Not sure now; I've been out of the loop for years.

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.


Thank you for the lore :)

I thought I could recall some post/article where Rich Hickey said something positive about React but I can't find it. Maybe I made it up in my head idk.


I have a Chocofi (36 key, 3x5 + 3 thumb per half). My complaint with the Cornes is that the keyboard doesn't have enough stagger for where they thumb cluster is positioned. Either the thumb cluster should move out like the ZSA voyager or more stagger is needed like Ferris sweep and most newer boards at a similar size including mine.

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


Yeah, I have found it most comfortable to use two keys on each thumb cluster. Space, Enter, Layer 1, Layer 2. I also like how ZSA's thumb cluster it moved out (Keyboardio really did it the best imho), but for some reason the keywell on the glove80 makes it much easier on my pinkies than the ortho layout on the voyager.

How did you find an ideal tent + tilt setup? Whenever I've tried I've wound up with sore wrists or hands, so just gave up. It seems like the glove80 w/out wrist rests does "good enough" so I stopped trying to optimize, even though the temptation remains.

I've seen some members of the erg keyboard community design and print their own pcbs based on their hand dimensions. I just don't have the time for it and fear how far down the rabbit hole I'd wind up if I did.


> How did you find an ideal tent + tilt setup?

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.


As an EDSF gamer (blame Tribes) I agree but I've run into issues with (IIRC) E, Shift, and Space on keyboards that aren't n-key rollover but it's been over a decade since I last owned one. So I think that's the reason for WASD.

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


While it's certainly possible to have a throttle most electric bikes require pedaling and therefore some degree of exercise. In many cases it gets people riding that would not be riding otherwise. For people that are actually interested in fitness it's a lot easier to maintain zone 2 on real roads with electric assist without the impulse to push it a bit up the hills. I did far more aggressive rides when I had access to my electric road bike than I do on other bikes because I knew I had a bail out if I pushed too far. Nobody's going to congratulate an e-bike rider on their feats of endurance or power but there are lots of points between a normal cycling effort and no effort at all.


There's a DIY forum for building those[1] but I think tow boogies[2] are more practical as a project. The idea is a battery box, controller, and motor on a boogie board and shifting the weight of the person being towed allows for steering.

[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


Roc does not have computation expressions and this specific syntax is the "something similar". Many other comments have noted that this feature corresponds to the IO Monad with do notation in Haskell and Computation Expressions are F#'s take on monads & friends. Roc's take on this is basically "why should someone need to know category theory to write to a file" and the relatively simple "use ! when you want to yield control to the platform" suffices until the programmer decides to dig into a full explanation.

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.


> "use ! when you want to yield control to the platform"

Thats quite the elegant solution indeed.

and I can certainly see the benefits to keeping it simple


> However, this flexibility seems to be primarily used by language/framework implementers themselves. Not by application developers.

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


I'm not sure whether you've seen this, but we have settled on a specific design for sharing effectful code across platforms!

https://docs.google.com/document/d/110MwQi7Dpo1Y69ECFXyyvDWz...

As you noted, a few other changes to tasks and modules need to land before we can ship that. There are currently PRs in progress to implement those changes, e.g. https://github.com/roc-lang/roc/pull/6658 and https://github.com/roc-lang/roc/pull/6683


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: