Re:Show HN: Turn your fancy, expensive computer into a stupi...
by eykd on Friday May 22, 2020 @04:20PM
(#23276488)
Ha, yeah, you'll have to find your skeumorphism over there. :) That's a pretty neat achievement, I have to say.
But I don't actually want to use a typewriter, I just want to force myself to write without editing.
Re:Show HN: Turn your fancy, expensive computer into a stupi...
by garaetjjte on Friday May 22, 2020 @05:19PM
(#23277176)
>missed letters if you type too fast (though I suspect it's a bug)
It states it's intentional:
>Just like a real manual typewriter, you can only press one character key at a tim
I have never used typewriter, but I don't think this is correct, the limitation should apply only for adjacent keys, not globally for all keys. This is the whole point of QWERTY layout, to type faster by spacing letters in words as far as possible to avoid jamming typewriter.
Re:Show HN: Turn your fancy, expensive computer into a stupi...
by reaperducer on Friday May 22, 2020 @05:41PM
(#23277369)
Nope. Letters from almost any part of the keyboard could jam the machine if you typed fast enough. That was one of the reasons that the IBM Selectric typewriter were so popular with professional typists. The ball mechanism had nothing to jam against.
I'm only half joking. I like the concept of re-implementing typewriter constraints on the writing process, but the skeumorphism was lacking. It took me a second to figure out why there were 2 text boxes, and the word-based tokenization is not type-writer like at all.
More importantly, one key aspect of the typewriter was lacking: the immobility of the cursor. In a typewriter, it was the page/canvas that moved, and your cursor stayed fixed. You could type paragraphs even an entire page without moving your head or even your eyeballs by just staring at the contact point of the letters.
Searching for "typewriter simulator" found this which is very close to what I was imagining: https://uniqcode.com/typewriter/
It even recreates the problem of missed letters if you type too fast (though I suspect it's a bug). At least it doesn't jam.