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.
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.
The gaps let you use the the function keys by feel rather than looking at them. They tend to be mapped in debuggers so hitting the wrong key is a big deal.
I actually don't mind the smaller arrow keys as again, they make it easier to drive by feel rather than by looking.
I'm typing this comment on a first gen framework 16 keyboard. It's the same layout as the second gen in OP, where PgUp/PgDown are bound to fn+KeyUp fn+KeyDown and Home/End are bound to fn+KeyLeft fn+KeyRight.
I actually prefer the bindings over dedicated buttons since if I need to use home/end, I'm probably also going to need to go to the previous/next line with the up/down keys.
Still on the lookout for anything that’s not chiclet based, but they literally don’t exist.
https://dell.alienwarearena.com/alienware-debuts-the-worlds-...
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.
This is such a lame response to valid criticism.
Key remapping is not a feature that you need hardware support for and neither are macros - both can be done in the OS and/or user-space software. Different prints on key caps are also not important at all since you shouldn't need them in the first place and hardly a response to someone being unhappy with the physical keyboard layout. So basically you're saying that because Framework already provides the easy parts that the user could already do in software now no one is allowed to complain about the physical layout that users cannot alter.
Think about it... Replacement hinges that separate the upper and lower shell by an extra 1/8-1/4" plus a thicker bezel to fill that gap. Suddenly (at the cost of a thicker laptop, for those of us who don't mind) you have extra space under the screen for longer key throw, contoured key caps, trackpoint, arrow keys that overlap the lower deck to allow a proper inverted-T layout, etc. Maybe even possible to retrofit old ThinkPad keyboards in there.
Hey, I can dream, can't I?
> numpad input module
You can literally add a physical numpad if you want: https://frame.work/gb/en/products/16-numpad?v=FRAKDM0001
This logic is why I like the tiny arrow keys. I find it pretty easy to move my pinky over and tap one of those keys. With full size keys, I find that doesn't really work.
Speaking of categorically false... How would you even know if you if you've been stuck with the default bad layout on 13 inch?
With a good layout your laptop would have keys laid out in a way that is even more comfortable than those of a standard standalone numpad (which ignores the difference in finger length), so your claim that worse layout is magically massively faster is just categorically implausible.
You're just likely confused because you compare numpad to the unergonomic horizontal 1234567890 number layer, but no, you'll have a bumps numpad layer at your fingertips, so count moving your hands right to a separate module and returning back left into typing speed as well...
Also, asking for more is very rarely a form of altruism: no one asks for more to avoid (others) “decades of rsi-health-dangerously poor manufacturing quality”, it’s generally for one’s own benefit, nothing more.
Well then, back to standard answer then: pick another laptop.
I really thought for a moment we were discussing the general crowd and why they should/could/must insist on ergonomic keyboards in general, but we misunderstood each other it seems.
> back to standard answer then This is not an answer to any of the questions. But you're right, standards of conversations are just as bad as those of hardware manufacturers
> I really thought for a moment we were discussing the general crowd
I was, but then you've made up a world where no one cares about anyone else, so tried to wipe that reality off your conceptual map.