Hacker News new | comments | show | ask | jobs | submit login

Mechanical machines are really satisfying, for their tactileness and simplicity. I have a typewriter, watching real impressions appear on real paper is way more fulfilling, and the organicness of the interaction is not even nearly matched in any computer program I used: you're always detached from the circuitry, where with mechanical devices you're a part of it. But the advantages of computerised production far outweigh those of mechanical devices, so I only type on my typewriter every once in a while as a recreative activity.



I too have a typewriter at home. I don't use it often, but when I do it's very satisfying for some reason.

I find it to be a pretty useful tool as well. I like to type out initial contact or offer letters for potential clients. In a digital world, receiving something that was typed really says something - or at least I've been told. Every key stroke is done with thought, as one screw up and you'll have to start over.


So, how exactly do you propose compiling and testing the code on your typewriter?


What makes you think they want to propose anything like that?


I do not only write code.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: