I think it's less for tracking than for trying to combat viruses and phishing attempts. Having the spool data and writing the JavaScript mail client app makes link-based tracking redundant.
It's not the bandwidth per se, so much it's the continuous attention cost spent on keeping that bandwidth going.
Better tactile feedback and more reliable input means I don't have to constantly multitask half a task worth of attention onto making sure the input I think I'm doing went off as intended, which makes it easier to concentrate on the main task, which reduces the build up of fatigue, which reduces the rate at which the cost of mental effort increases throughout the day.
Which is not to mention things like the chance of getting hand cramps from the additional tension there caused by interacting with a less reliable keyboard, and by the tendency to use excess input force in attempt to get strokes through more consistently.
By my read y'all need more practice typing, not a fancy expensive ergo keyboard. Other than the occasional hand cramps this lifelong nerd doesn't have any of those problems on this old, mushy MS natural.
I thought so too untill I started having RSI/CTS issues. I've since switched to a 'fancy expensive ergo keyboard'. And it fantastic, I'm about as fast as I was on a traditional qwerty, but with less errors. However most importantly I have far less RSI/CTS complaints when typing on my redox than I do with a non-split (even ergo non-splits). My arms are in a far more natural position and so is my wrist thanks to the tenting and tilting I can do with the redox.
So if you are typing a lot, I would recommend getting an ergo before you start having issues.
For reference I could type about a paragraph in one go on a regular keyboard, now I can type an entire page before I start having pains/cramps.
Jumping in to chime in on this. I developed issues a few months ago, then swapped over to the ergodox, and my daily pains stopped. If you can't afford the ergodox, I also found the Microsoft Sculpt worked wonder. I picked up a used one on eBay and it's been great.
I use a Sculpt as my work keyboard and, while fantastic, have you had any issues with the range of the wireless transmitter? I feel like it doesnt go beyond a couple of inches unless it's plugged into a powered USB hub -- even then it still occasionally drops keypresses
Totally agree. I never realized this until one day it started hurting to do work which really took the wind out of my sails. Adjusting my setup to better compensate for eye strain and rsi related issues really helped.
Unrelated to parent topic, but related to your comment on eyestrain, I have found that using f.lux to change the color temperature of my monitors to match the fluorescent lighting in my office (with a color temperature of 4200K) to do wonders for alleviating eyestrain.
Changing the temp on my monitor and making additional adjustments to my workspace helped. However, thank you for the suggestion. I had previously known this as a mac only software.
Fully agreed. I am very thankful that I took typewriting classes when I was younger. I do not think it is a coincidence that I also do not have trouble with keyboards being difficult to type on, unlike 90%+ of the folks I work with. Just plain putting in the hours of practice on proper form may not be a very exciting answer, but I can't think of a more effective one.
I agree 100% with you on this. My first year of high-school we had a typing class on an IBM Selectric keyboard. Our teacher was a wizened old secretary that for a considerable portion of her career used a non-electric typewriter.
What has always stayed with me was her guidance on posture and form. The 'piano style'* on which she insisted is almost completely contrary to modern ergonomic teachings, and yet I can say almost 40-years later; still works and is effective.
I readily admit that I'm probably lucky too in that I don't follow that guidance to the T, I do however follow the basic form of it. This anecdote simply agrees with your statement.
*: 'piano style' wrists higher then knuckles, finger-tips hovering/barely touching home-row, back straight
It might be a consumer perception issue, either relating to the inexpensive (relatively) price or the Microsoft brand that keeps users away from the Natural versus other more complex designs.
Contracts state a lot of things that don't necessarily hold up. It's just words on paper. Sometimes they're even tenable in one area, then used in another state which disallows some claim or another.
Employment contracts in particular are subject to a lot of restrictions and protections regardless of what the employer makes people sign, because labor laws.
RHEL is popular for solutions like running a datacenter mostly because it has a nice enterprise support story. It's what the E in that acronym is for, after all. Ubuntu, meanwhile, is quite popular among us mere mortals who have to fix our own boxen.
Debian is popular for Docker images exactly because many of the people trying Docker were already familiar with Ubuntu. Those users quickly ended up wanting smaller images, making Debian an obvious thing to try out since Ubuntu is basically Debian with bells on.
Ubuntu fought a sea of distros and came out as what's very nearly an industry standard, if not an official one. The 90s were a fricking mess by comparison. Slackware on floppies.
(And now I need "Slackware on floppies" dubbed over the "Jesus wept" scene from Hellraiser.)
> Ubuntu fought a sea of distros and came out as what's very nearly an industry standard, if not an official one.
I think you may be living in a bubble. I've been running devops for various shops for half a decade and I've only once used Ubuntu, because it was already being used by an acquisition.
I won't deny that Ubuntu is popular. It's certainly got the lions share of the desktop market. But there is no such consensus in the server market.
It's faster, but only under the specific design condition of both having to wait for storage to finish and not caring about differences between the presented storage options.
If the design condition allows asynchronous operation and I don't need to wait for background tasks to finish before I reply, it's not faster unless I somehow care more about background CPU time per request than I do about things like storage guarantees.
If the design condition requires durable storage to have happened before I reply, putting it in Redis doesn't even count as getting started.
