Surprised Ergodox is not mentioned, that's the keyboard that started the movement. Very safe pick since firmware is open source and it can be both self-assembled and bought.
It has too many keys in thumb clusters and bottom row, but you can easily remove them.
I included ZSA's other boards (Moonlander and Voyager) since they seemed to have superseded the Ergodox in popularity. But yes, it definitely was one of the first to come out. ZSA is still a company paving ways though!
I feel like the Ergodox was traditionally a lot of people's first wacky split keyboard -- but for those that stuck around, it was rarely their last. These days, there are so many better options that it's hard to recommend Ergodox despite its historic importance.
1. No pointless layer of "inner" keys that you never use
2. The thumb keys are closer to the main keyboard, so more of them are in a natural reach, rather than being a big stretch (this is the biggest one in usage)
3. Uses all 1u keys, so greater keycap compatibility (any ortho kit will work)
4. If you're comparing to the Ergodox EZ, construction is better, with a metal case instead of plastic
5. Takes up less desk space
And it's still QMK, still hotswappable, still has the columnar layout. I don't think the Ergodox offers anything over it.
The narrative about AI replacing humans is just a way to say 'we became 2x more productive' instead of saying 'we cut 50% jobs', which sounds better for investors. The real reason for job cut is COVID overhiring plus interest rate going up. If you remember, Twitter did the job cuts without any AI-related narrative.
In Java it’s called Vector / list refers to linked list. Python doesn’t have a linked list type so it’s kinda irrelevant. But also not every language has to be Algol centric even though Algol has largely dominated the design space of popular languages due to familiarity.
> In Java it’s called Vector / list refers to linked list
What?!! No! Vector is almost never used in Java code. When you need index-based access, ArrayList is the much more common one, and it does implement List. So I would agree with parent commenter that List is the equivalent in Java.
If you care about why Vector is nearly never used: it is synchronized by default, making it slower and more complex than ArrayList. Most Java programmers would prefer to implement synchronization themselves in case multi-threading is required since it nearly always involves having to synchronize multiple list operations at the same time, which cannot be done with Vector.
It's the same reason no one uses StringBuffer, but StringBuilder.
I’m aware. The preferred name is clearly Vector and ArrayList is the wordy alternative they had to use to not break back compat. List is the name to the interface which encompasses a lot of different data types. But ask a Java programmer of they prefer to use arrays or lists and I suspect they won’t even think twice about understand that the list you’re referring to is a linked list rather than asking what you mean because arraylist implements list. A fun Java weirdness is that of course arrays themselves do not implement list
You are really out of touch, LinkedList is very widely regarded as bad for performance in nearly every scenario possible and thus hardly ever used. Array VS Arraylist is a valid question because they have very different properties.
[author here] Very good questions; I definitely would like to revisit num32 very shortly. I'd say the initial rational of having num32 is not coherent right now, but I'll have to verify removing the support.
we have floating point type(It was missing from the type list in readme. I have just updated that seeing this comment. thank you!)
Well, clarity would be achieved with a name like u64. Is num signed? What's the range? Is it integers or floating point? All these things are hidden. With u64 there would be no questions open. (Well a few maybe, like overflow behavior, but can't have it all..)
There cannot be any num32.
num is a number, which can be fixed size integers, floating point numbers (of fixed size or not) or bigints. Some also add decimals
2 pieces of UI in different parts of the page that depend on the same data - that's the line (also matches the initial goal of React - sync FB chat widgets).
reply