If I ever do need to see two things side-by-side, I’ve also got Rectangle for window positioning. A single cmd+caps lock+H/J/K/L for left-half/restore/maximise/right-half is all I’ve found is necessary.
185 karma · joined June 22, 2020
If I ever do need to see two things side-by-side, I’ve also got Rectangle for window positioning. A single cmd+caps lock+H/J/K/L for left-half/restore/maximise/right-half is all I’ve found is necessary.
I think the central hypothesis of using these keyboards is flawed. It seems to all centre around thinking that less movement is better, and that keeping as close to the home row as possible is king, even if that means chording, contorting your hands to reach far keys, and over-relying on your weak pinky fingers.
Human bodies are meant to move. I've found that since I've started dancing over keyboard more with my fingers (a sort of advanced hunt-and-peck using all fingers but the pinky), combined with using a low profile keyboard, my hand pain has disappeared, and I'm at my fastest WPM yet (105). YMMV of course, but it's worth considering if you're peering into the rabbit hole.
In the main article: > Researchers have reached data rates of over 224 Gbit/s
Am I missing something here, or does the claim in the summary need to be adjusted?
Also unrelated but the shocked dude in the last pane looks way too much like Elon Musk for my liking.
* That initial "How to use it" diagram completely puts me off the product - it seems dizzyingly complex, and to have that right at the top before I even know what the product is seems like a mistake.
* Consider getting a native speaker to review the text - the grammar is off in a fair few places.
* Write a simpler paragraph for what your product does - I've read through the entire landing page, and your HN comment, and I still don't understand what it is you are selling.
How do you handle split screen? Do you never have two programs side-by-side on the same screen? I've tried doing that in the official fullscreen mode but found the whole experience a pain, so I use rectangle to shift windows left and right.
Other than that, no complaints! A fanless, performant laptop is a dream.
There's also the question of prepping, but I'm a chronic optimist, so I don't think a true collapse is coming in my lifetime. And if does, there's always that CollapseOS which was posted here a year or so ago to get me through. Though thinking about it - I think perhaps whether or not I can browse HN during the apocalypse will be the least of my worries.
On the one hand, it really kicked off my imagination, and I started to yearn for absolute computing simplicity and efficiency. A world where I can run absolutely anything I want off of a Raspberry Pi Zero and a small battery pack. I even spent half an hour looking into the most lightweight GUI toolkits available, to start to contribute to this vision.
On the other hand... it all seems so futile, and out-of-touch with reality. In the real world, I need to pick the best tool for the job at work, regardless of the philosophy of the tool. And in my spare time, I can't help but feel like it's a pointless endeavour. I'm not living on a boat, and I'm not working on a Raspberry Pi. Why rewrite the software I use into something more lightweight when I can just use the software without consequence now, and save all that pain?
Plus, there's a certain amount of 1. pretentiousness and 2. hypocrisy that I read in the article, that I don't want to touch with a 10 foot pole. Using your own time system is nothing more than a "I want to be different" gesture. I honestly can't see the benefit at all, despite his explanation. If you want to do 2 week sprints, just do a 2 week sprint. If you want to work to 40 minute Pomodoros, just do 40 minute Pomodoros. The main benefit that I can see is the element of mysticism to seeing things on the wiki timestamped as `14X05`, to add to the feeling that this is some other-worldly operation going on that's just out of reach. Yet he scoffs at the interview for suggesting it's an aesthetic thing.
Regarding the hypocrisy - Devine preaches for energy efficiency and simplicity above all else, then writes half his tools using <canvas> on a bloated web browser. It doesn't quite stack up for me.
Long-term, I can see once in a blue moon going back to the exact thought process during an issue would be invaluable if something similar crops up, but 99 times out of 100 is this not over-documenting? I'm not trying to criticise here, I want to understand what value you get from it.