816 karma · joined May 23, 2010
Anyway, having to hit the enter and backspace keys with the thumb is what I found problematic, that's why I remapped them to alternative places with their online tool.
I'm quite susceptible to RSI but it seems that, unlike others, my weak fingers are actually my thumbs instead of the pinkies, and this keyboard puts heavy emphasis to press modifier keys (enter, backspace - EDIT: ctrl, alt, etc were included in the list by accident) with the thumb. Within a couple of days I felt sore and could barely move my fingers. I then used the remapping software to move all modifiers to their usual places (as much as possible) and the situation did really improve.
However, I frequently switch between the desk and a laptop and always had to waste a couple of minutes to adjust to the different layout. The TEK _is_ slightly more comfortable but not enough to justify its high price for me, that's why I ended up returning it.
Additionally, the return process is long and tedious since they have a tendency to ignore the first few requests and they seem to respond only if put under pressure. I managed to ship back mine last week, after a monthlong attempt at gaining their attention.
I tried many keyboards during these years and in the end I think that switching to a mechanical keyboard (Unicomp EnduraPro) and from QWERTY to Colemak did 90% of the job for me. After that the law of diminishing returns kicks in.
By paying a small sum you get access to precompiled binaries, some level of support and peace of mind that you are helping developers continue their work in a sustainable way.
Frankly I would like to see this model adopted more often in the FLOSS world.
In my experience it highly depends on the editor. With Sublime Text 3 on OS X, each keystroke is delayed by SSHFS' latency. It's a pain.
Tramp transfers the files back and forth, always working on a local copy (if I remember correctly). It provides a better experience.
In the end, I believe it is more worthwhile to just file bugs [1] en-masse to have a "this issue is public" checkbox in their bug reporting interface. If enough people request this feature hopefully they will add it.
[1]: "the keys come with a slightly textured finish. This in itself isn’t particularly noteworthy, but after just one month of typing I’ve found that many of the keys are starting to get a glossy sheen" (http://www.anandtech.com/show/6819/truly-ergonomic-computer-...)
[0]: http://www.cpubenchmark.net/compare.php?cmp[]=2238&cmp[]=815
I agree. I can barely discern pixels on my rMBP (227 dpi) and find little difference between that and the iPhone (~300 dpi), or even the Nexus 5 (445 dpi) and I am quite sensitive to fuzzy text.
400 dpi looks better on the spec sheet but I believe it is just wasteful and puts unnecessary (or, at least, with marginal returns) strain on the hardware to push all those pixels to screen.
So, from an UX standpoint, they still make a lot of sense to distribute application bundles since it compels users to "install" the application by dragging the bundle icon to the appropriate directory, which is conveniently symlinked in that Finder window. It's also easier to produce than a self-installing package.
With a .zip or .tar.gz users would be left with an app bundle and no idea of where to put it. Generally they would just throw it somewhere random across the filesystem. At least, that's what non-technical Mac users I know happen to do.
[1]: https://support.cdn.mozilla.net/media/uploads/gallery/images...
E.g.: If I add a constraint "laptops with at least 16 GB of RAM" it doesn't show the Retina MacBook Pro 13". Only the 15" model is shown, because there is a default configuration with said amount of RAM.
In the end though, I found the syntax "funny" in some places and slightly less verbose than Java but not enough to justify using it. The underlying Android API is so verbose that Kotlin by itself is nearly useless.
We ended up dropping Kotlin and rewriting the thing in Java. In terms of lines of code both versions are nearly the same.
With a 11 MB dependency, even production builds take considerably more time to complete and that gets in the way when you want to test the app on a production setting and you have to wade through a lengthy build process each time you fix a bug.