←back to thread

Framework Laptop 16

(frame.work)
465 points susanthenerd | 2 comments | | HN request time: 0s | source
Show context
kristianp ◴[] No.45033106[source]
You've got a 16 inch Laptop, why are the arrow keys so tiny! And where's the PgUp PgDn Home End Insert Delete cluster? I wish a design-based shop like Framework would have some leadership in the keyboard area. This is why I have been exclusively Thinkpads for my last 3 laptops.

Something more niche is that I also enjoy the mouse buttons above the trackpad, I can move with the thumb and click with a finger.

replies(11): >>45033670 #>>45033673 #>>45034139 #>>45034554 #>>45034750 #>>45034899 #>>45035641 #>>45036917 #>>45041177 #>>45057538 #>>45099920 #
promiseofbeans ◴[] No.45034899[source]
I mean, they made their keyboard swappable, with open-source firmware. If you are passionate enough, you can make (and sell) a replacement that solves these issues.
replies(1): >>45034949 #
bigstrat2003 ◴[] No.45034949[source]
Making custom electronics goes way beyond "passionate" and into "has specialized skills and enough capital to get these made".
replies(1): >>45035746 #
rendaw ◴[] No.45035746[source]
I think "well just make the PR yourself" comments are too reductionist myself, but in this case Framework does have space for 3rd party components in the marketplace. I don't think it'd be crazy to imagine some custom keyboards will appear there.

And here's an example of someone making a custom keyboard: https://blog.perprogramming.com/posts/framework-ortholinear-... - it looks pretty awesome, and I'm fairly sure this is the first time I've ever seen a laptop with an ergo keyboard like that.

Framework 16 is a collection of modules, so I think complaining about the modules is fair game, but it could also be seen as a basis/standard that isn't expected to fit everyone's needs, but fit maybe 90% and allow other people to make the customizations they need easier, in which case complaining about they arrow keys on a single component does feel a bit trivial.

replies(1): >>45036889 #
eviks ◴[] No.45036889[source]
> but fit maybe 90%

Bad keyboards fit 0% to the point of injuring x%. Now try to trivialize this more realistic number

replies(1): >>45037185 #
1. majewsky ◴[] No.45037185{3}[source]
How exactly does typing Fn+ArrowDown instead of PgDn lead to injuries?
replies(1): >>45037504 #
2. eviks ◴[] No.45037504[source]
Why would you miss the keyboard forest that's explicitly linked to in the comment for the tiny blade of grass that is PgDn?