- you will mostly work on the same place (or you accept the burden of traveling with your keyboard and be "that guy" when you set it up. Personally for the same hurdle, I prefer a secondary screen on the go)
- you will mostly work on the same machine (or you have multiple keyboards, one for each machine, and if you are in a data center or tech support, you move with your keyboard).
- you will not be exposed to many different keyboards, or layouts (e.g: you don't need to go help users and customers on their machine that don't allow plugging in, you don't teach, you don't use your phone a lot, etc). Switching layouts all the time is a nightmare.
- you can afford the initial lower productivity (e.g: you are not a freelancer that needs a regular output).
- cables and taking space are ok. Taste is taste, after all.
- you have the money, and find it is better invested in this than say, a better screen, mouse, graphic card, battery, etc. And renewal. Or you have enough to have it all.
- you are certain of this model is what you need or you can afford trying many. There are many ergonomic keyboards. They are all special and expensive in their own way.
- your layout is available. I'm french, I use AZERTY. Or you are fine learning to type with the wrong letters, or using stickers. I often buy/user computers in/from the US, and just type from memory after setting the QWERTY to an AZERTY layout. One of my friend like Dvorak (actually Bepo, the fr version)...
- nobody else than you will use your computer. Or you have several setup and are ok to switch every time.
Now I understand that as it's my job, optimizing this key element of it makes sense.
1. I am "that guy", but who cares? It's like a carpenter bringing his own tools. I bought a second one after 1 year of lugging it around, because it's worth it to me.
2. Use/buy US QWERTY on everything, with US-International dead keys. I've been typing German (QWERTZ) this way for >10 years now, and it makes some programming tasks/tools easier to use.
3. Alternatively get a set of blank keycaps for your keyboard. This is actually a key ;-) feature of mechanical keyboards, you can get keycaps in all shapes and sizes and even custom printed ones. I use blanks or US QWERTY.
4. Keep a second (regular) keyboard plugged in case a coworker comes around. This is easy, as there is usually one on the desk already.
5. Borrow keyboards from friends for 2 weeks and try them out full-time. Some that I've tried were downright painful. I know it's hard to return stuff in Europe but if you can, try to.
6. Although expensive I think it's a good investment, especially if may prevent health issues in the future. Some employers may even pay for it, or offer an alternative.
Those are not solutions, those are workarounds, incomplete ones, and for only half the things I mentioned.
You may accept the price of those compromises depending of your context, what's important and the ROI or course. That's what our jobs are about after all.
I don't mean to say you should not buy those keyboards, I only want to provide another point of view.
I totally agree, but it's not all black and white.
You can still have nice things N% of the time, and just fallback to the regular stuff when away from your desk.
Also the keyboard community isn't always rational or focused on ROI. It's both parts ergonomics (preventing health issues) and optimizing for productivity and nice working conditions (regardless of cost).
So you don't share your computer with kids or the spouse (you have money or no spouse/kids), don't teach, don't do much on site user support, don't visit much clients, don't travel for pleasure or family much, don't use much virtual keyboards, are not at a university, etc.
It's not a good or a bad thing, but it would be a mistake to generalize it.
No, I don't do those things. Sharing a computer is a fairly uncommon activity for me and most people I know. And even if it is something you need to do every now and then it is always possible to add an extra layer to your kb config which is the standard layout so other people can use it.
The overwhelming majority of people use the same one or two computers (one at work, one at home), and don't mind using a laptop keyboard when travelling to a meeting or visiting a client.
Anyway, since you're in Europe, don't you have a mixture of keyboards amongst your colleagues anyway? I certainly do -- I've noticed US, UK, Danish, French, Swedish, German and Russian printed keyboards. There are also about 4 kinds of ergonomic mice in use, of which two look pretty weird -- and the users of these mice are not developers, they just had/have RSI issues.
Every case is different, that's my point. The keyboard match a very specific profile: geeky user typing a lot, with few occasions to be forced to switch.
For me, as a trainer, I'm constantly on other's people machine. Thanks god they are all the same layout.
As a freelancer dev I also can't be less productive for 3 months.
As someone that travels a lot, I don't want to package a keyboard in my bag back. Planes make you pay extra for to check luggages in now a day. Beside for the space, I'd rather have a portable secondary screen: the gain of productivity is way higher.
Again, not saying you should not buy the keyboard. It may be a very good choice for you. Just speaking of the other side of the coin.
I have quite an idiosyncratic keyboard layout and when I switch to use someone else's (normal) keyboard I'm puzzled for a moment but then switch into it. You might find you can do this easier than you think. Try a custom keyboard at home and treat it like a hobby, only using it when you feel like it.
My experience from switching keyboards or layout is that there is a initial cost in productivity: you type way more slowly and it's harder to think, for a few days up to a few months depending of the importance of the change.
I had pretty severe carpal tunnel syndrome for about a year when I did data entry full time. What helped was improving my posture, not tensing up and slamming the keyboard at full force all day, and resting/shaking out my wrists every 15-30 minutes during extended typing.
I have a mechanical keyboard today but doubt it would have helped more than any other (much cheaper) keyboard that requires less keypress force. The problem is that squishy $5 cubicle keyboards tend to be really, really bad in that regard.
I worked at a place for 6 months and in that time I developed severe wrist issues, when I left they vanished. The only physical difference I could pinpoint is desk height, both the jobs before and after had considerably lower desk heights.
More recently, when I started working from home more frequently, my wrist issues reappeared. My desk at home is higher than my desk at the office.
So I can completely understand a tweak to wrist position making dramatic changes to RSI or CTS.
It's really common for computer programmers. In every big corp I've been in, there's usually one of 10 people who has an issue with it and uses some weird keyboard. I have pretty bad RSI and it comes from just being a computer user since I was 3 and developing bad habits along the way.
My impression is that it hits data entry clerks a lot harder than programmers. Programmers end up having to stop and take breaks frequently to think about what they're doing.
A thought occurs: Are RSI issues worse with enterprise Java programmers and other people who end up having to write tons of boilerplate around all of their code?
Because it means losing control over their brand. Who knows what some random youtuber will do, who they are, etc. It's just not worth all the legal headache.
They do it anyway. And it saves you the cost of the cat and mouse game. You cannot win this unless you create a dictature. There is Mickey porn and fascist Pepa pig anyway. So why not collect the benefit of having real fans making great content instead attacking them.
E.g: nintendo killed an incredible fan made metroid game. It seems so short sighted.
We also have light receptors on the skin. And I'm assuming we have many others we don't know about.
The way we teach about the human condition is very limited, and I only started understanding a bit how my body works after I reached 30 thanks to a lot of self-experimentation.
Never got popular enough to be ported to cpython, let alone python 3.
It's no surprise though: my experience is that most python devs don't know how to use a debugger. In fact, the huge majority of tutorials to learn python don't include one, nor they give explanation about python -m, venv, pip, the python path and other very important basis.
Even the people using pdb don't know very important commands like until, jump, up or tbreak.
Wait what? Do you know about the %debug magic? It is the best thing ever, particularly when prototyping in the notebook which keeps most of the state.
I saw Fernando Pérez use it in a YouTube video. Shame I cannot find it anymore. He was saying he debugs his code only by placing 1/0 in the part of the code he wants to inspect. After the exception is thrown %debug allows you to step into the stack and explore it via a repl. I found that crazy and tried it it. It is life changing. That's how I debug my python code for years now.
It's sad really. I gave a talk a year ago on debugging with the pdb, the basics. Turns out I was the only developer who had ever used the pdb as opposed to bucket listing it.
same with arduino. breaking from pro emedded work to Arduino for some just for fun projs, im flummoxed wo my debuggers and astonished how unfamiliar the community is!
Maybe that's because of the different kind of work I do with but I have wrestled, frustrated at some bugs hard to spot with gdb, but I never felt retrained by pudb despite it being, I guess, more limited.
All the bugs I had in python were easier to reproduce, probably because it provides less rope than C or C++ to hang yourself. Usually, stopping a bit before the exception, exploring the variable states was enough to spot the bug.
Isn't there something about garbage-collected, dynamic-types, GIL-constrained languages that makes their typical bug easier to spot with a more limited debugger?
I can attest to that. Micro-dosing is only a bonus. In fact, I regularly stop taking them when I don't feel like it, and I'm just back to my normal self, not lower. No negative side effect, no dependencies, and it helps taking care of yourself: eating better, sleeping more, etc.
But OP is right on one thing: it is not a substance the body needs. It's an artificially induced condition, and it's why it's important to take days off. Sometimes I take a week, not just the 1/2 days of the most popular protocols.
This way you can see if you are improving deep inside, and that it's not just the drug saying you are fine. Plus those substance allow it: no hard in stopping cold turkey. It's beautiful how positive this stuff is.
Up to now, I can attest than, yes, even when I'm not taking it, I'm better. Mostly because when I take it, I live a better life.
On the topic of micro-dosing, I microdosed around 3-6ug LSS/day for 1.5 years. Stopped abruptly one day and haven’t used it since. So echoing your sentiment about how easy it is to stop.
Not OP but can confirm the exact same experience when microdosing psilocybin. I get them from friends who grow them. Spores are not illegal, they can be bought online and sent through the mail.
I think of all the illicit activities one can discuss with friends/neighbors/coworkers, magic mushrooms is the least concerning and most likely to result in a positive connection. At least here on the west coast anyways, lots of people have access to mushrooms and consume them occasionally. You just have to develop trusting relationships with people around you, and that's generally regarded as a good thing anyways.
It's not too difficult to ask some people if they want to go camping, and while out in the woods bring up a curiosity about magic mushrooms. Anyone who goes camping with you is very likely to be open to the idea if not pull a bag of shrooms out of their backpack on the spot.
If it's very cheap, fast and convenient, then it's enough for at least screen the population regularly. Catching only part of the cancers is quite nice already.
Sensitivity is what fraction of the affected people are actually found. Here: 90%, so 10% are missed.
Specificity is what fraction of the unaffected people are detected as such. Here: 95%, so 5% wrongly detected ("false positives").
In Europe, there are 60 cases of lung cancer per 100 000 people.
That makes 54 correctly detected per 100 000, missing 6 cases.
That also means 5000 people incorrectly suspected of lung cancer (5% of 100 000).
Update: using the accuracy from the article itself, we would still get a total of 1000 of false negatives (affected but not detected) and false positives (unaffected but suspected). Incidence is still 60/100 000.
Yup. And some of those follow on tests could be quite invasive and risky in their own right. With that kind of false positive rate, you'd be risking the life of a not insignificant number of people.
Either that or driving up healthcare costs significantly as those 5000 people are going to need an MRI or CAT scan or something else to rule out cancer.
What follow on test for suspected lung cancer would risk the life of a not insignificant number of people?
An MRI without contrast has no impact. An MRI with contrast has relatively little impact. A biopsy would only be done if the MRI with contrast lit up areas of concern. At the point a PET is ordered, you have narrowed the false positive pool substantially and probably want the scan no matter what.
Just telling millions of people per year they might have cancer... say the MRI is booked for 2 weeks out... which they are then going to majorly stress about the whole time regardless of how low you tell them the risk is - is going to have some crazy societal impact.
I typically have several MRIs per year. I'm not claustrophobic and don't stress about them, but sometimes MRIs cause me physical discomfort, even without contrast. With contrast, its slightly worse, it seems.
I think its related to a genetic disorder that causes me to retain high levels of iron, but I have nothing to back this up.
This discomfort in the MRI comes in the form of waves of warmth I feel throughout my abdomen. Its mostly annoying/distracting and not painful. The loudness of the MRI is far worse than the slight warming I feel. Less annoying than the pee your pants feel of a CT with contrast.
I believe the stress would come from the uncertainty of whether or not they have cancer, not from going into the MRI machine.
Just looking at myself, I feel a great level of distress over other, less serious, variations of uncertainty.
Having been told I might have cancer, and then not getting to know for certain this very instant would be nothing short of nerve-wracking...
The warmth is caused by the RF pulses and has nothing to do with the magnet or iron levels. Basically the scanner behaves the same as a microwave oven.
That's why you have to enter the patient weight and size before scanning, in order to keep the SAR within acceptable values and limit body heating.
My father has hemochromatosis which causes high iron uptake. He didn’t discover this until his fifties and it’s like he has rust in his joints. I did 23andMe and I only have one allele so I don’t have it. If you suspect you do, a dna rest will tell you. Please get that checked out. You can deal with it if it’s early in your life.
Ive been tested, and I have hemachromatosis. That's what my next MRI is for - to check on my liver.
So far, for me, it's monitoring. Some dietary changes such as cutting back on red meat and high iron vegetables (mostly cut out spinach, which sucks because I've loved spinach my entire life, especially the Greek dish spanikopita).
My blood iron levels fluctuate a lot based upon diet. Ive mostly got it under control, but normal for me is still on the high end of the normal ramge for normal people.
It probably went undiagnosed for a long time because I used to give blood regularly, but had to stop when my work hours changed to be 7am-7pm and could not make it to a facility to donate. Thats when blood tests started ahowing a problem. Not yet to scheduled phlebotemy, but probably the best option if it becomes an issue.
We don't really know. Data that show X dose of radiation increases the probability of developing cancer by Y% is based on studies on survivors of atomic blasts. The number of people exposed to an amount of radiation equivalent to a handful of CT scans is pretty small relative to the effect size that's claimed, so there is reason to be skeptical.
It doesn't have to instantly and directly kill somebody to be bad in aggregate.
This kind of analysis has been done, most memorably for breast cancer screening. The conclusion I recall was that it did more harm than good a few years ago (opportunity cost of unnecessary spending, pain and complications of biopsy, unnecessary mastectomy, psychological damage, etc. etc.). The follow-up tests and analysis also have an error rate and no treatment is zero cost.
That's also why there was no screening for thyroid cancer after above-ground nuclear weapons testing. Thyroid cancer itself isn't that hard to treat. So the risk of follow-on testing outweighed cancer risk.
And that's assuming that the 99% accurate really means 99% sensitive, 99% specific.
To amplify your point,
99% sensitive from 100000 people with an incidence of 60 means 1 false negative, assuming you can't detect .4 of a person and floor to integer.
99% specific from the same pool means 999 false positives, same assumption.
You mentioned that re: 1000 total, but the kicker:
Total population, 59 true positives + 999 false positives.
So, if I test positive, absent any more knowledge that means it's a 59/(999 + 59) chance of being true, or around a 6% chance of being true.
Probably enough for followup testing, but an interesting demo of why the statistical accuracy is meaningless unless you also know the actual incidence. 99% becomes not many % right quick.
The article says 99% accuracy for 13 cancer types.
Some cancers like pancreatic are a death sentence because it's usually caught too late.
"Toshiba says its device tests for 13 cancer types with 99% accuracy from a single drop of blood"
"The test will be used to detect gastric, esophageal, lung, liver, biliary tract, pancreatic, bowel, ovarian, prostate, bladder and breast cancers as well as sarcoma and glioma."
Cancer diagnostics do not rely on a single test. There's a number of (more expensive) metabolic and endocrinology panels, imaging, biopsies, etc. that follow to validate.
The idea is that you have something cheap and easy up front before or in parallel to further downstream diagnostic procedures.
I think it's pretty intuitive once your attention is called to the issue. The specific numbers aren't even that important. The general principle is that a screening test for any condition that is rare compared to the error rate isn't going to be very useful due to the large number of false positives. And most severe conditions we want to know about are rare.
Even though those false positive rates are high, I don't think that in itself is enough reason to dismiss the idea.
You'll still be able to identify a pool of people that as a group will develop this cancer at a rate 20x above the normal population. That still seems like a big deal, for instsance if I discovered I had a genetic factor that made me 20x more likely to get a particular cancer I think I would want to be tested for it out of precaution. This seems like the same thing.
(Now if the only further test you can do is itself super invasive or risky, that obviously has to be weighed into the decision too).
It's kind of silly to argue from first principles when you can ask the people who study this stuff, epidemiologists. 90% detection and 95% specificity would be horrible numbers if you asked any of them.
Isn’t the gain of this kind of machine that you are testing many people that weren’t tested at all before? Some of those will get a scare for nothing, but more will find out earlier that they have cancer.
If all it takes is a drop of blood (as opposed to more invasive tests) to know with ~90% accuracy if I have cancer or not (and when the machine says I do, then do a more accurate follow up test) then it’s far more likely more people will get diagnosed sooner.
That would decrease the amount of people correctly identified. And you're also under the assumption that the misclassification of people is a random phenomenon. In the real world that wouldn't be the case and some type of blood may get misclassified all the time by the system.
Is there “error” for these these tests independent when performed on the same person spaced out over a long enough time period?
Say you run the test every day/week/month, can you look at the total results or do the failure cases for the tests themselves depend on the individual?
Many diagnostic blood tests for cancer markers are more useful as a data series over time than as single point in time tests, because individuals have variable "normal" or baseline levels. You establish an individual baseline for each marker (for each patient) and then re-test every 6 months. If a number moves from its baseline, then you investigate.
Screening techniques are a real problem if their false positive rate is high. Any significant increase in the work up rate will be a real burden on the health system (so you had better see a corresponding benefit). Worse, gold standard for follow up is going to vary by disease and location, but if it is say a biopsy and you are screening a large population you are often going to start killing people without the disease. Not many, of course, but you have to balance that against the putative improvements.
No, because you'll be telling 1 out of 20 healthy people they tested positive for cancer. Or, if it's 95% selectivity per test, which it probably is, 13 out of 20 healthy people will test positive.
This is true for any medical act you perform on a massive scale really. Including vaccination, supplementation, etc. Everything is a cost/benefit ratio.
Yes, and this math has been done on many of those interventions (certainly for vaccination) and the benefit holds up. That statistical base rates are problematic for cancer detection is a pretty well-understood problem.
Reading the RFC, this seems to make HTTP stateful:
"A subscription is different from a GET connection (e.g. a TCP connection, or HTTP/2 stream). If a client requests "Subscribe: keep-alive", then the subscription will be remembered even after the GET connection closes."
It also uses PUT to patch things, but then why not use PATCH ? You could say it's non standard, but at this point, everybody uses it. Plus their stuff apparently deviates from the HTTP standard as well by allowing headers after the first line of the payload and introducing the forGET command.
Or am I missing something ?
Interesting anyway, especially the way they create of graph of unique ID to solve the ordering problem. Feels like Git. The flow of patch reminds me of react-redux.
Plus it's great to have more geeky technical things on HN. I'm missing it, among all the news and start up things.
I agree, this RFC seems to propose a great deal of different additions/changes to the HTTP protocol without a unifying reason why. But the committee/process is all in the open, through the IETF, so now is the time to voice your concerns!
> Reading the RFC, this seems to make HTTP stateful
The reasoning behind this seems to be that the alternatives right now are either polling or a homegrown websocket based protocol. The authors argue that rather than continuing to let different implementors make bespoke or otherwise non-standard polling/subscription based websocket implementations, to standardize on a RESTful way to subscribe to a stream of updates.
> It also uses PUT to patch things, but then why not use PATCH ? You could say it's non standard, but at this point, everybody uses it. Plus their stuff is apparently deviate from the original standard as well by allowing headers after the first line of the payload and introducing the forGET command.
I've personally seen both PUT and PATCH used for updates, so this didn't seem particularly odd to me, and seemed more like a nod to one particular method of updates.
But yes, the overall RFC is proposing to modify HTTP from a state transfer protocol to a state synchronization protocol, so that clients and servers have to hold onto state and send diffs between their internal states, and then implement some reconciliation algorithm (e.g. OTs or CRDTs) to merge state. This seems like it is in response to a myriad of bespoke long-polling or websocket based update mechanisms.
> this RFC seems to propose a great deal of different additions/changes to the HTTP protocol without a unifying reason why
To read more of the unifying why, I suggest checking out the original Braid draft from last July: https://datatracker.ietf.org/doc/html/draft-toomim-braid-00. We had a much longer introduction in that version, but shortened it in braid-http-01 so that we could cut to the meat.
If the why still isn't clear after reading braid-00, please let us know on the mailing list: https://groups.google.com/forum/#!forum/braid-http. And on the other hand, if something in braid-00 helped, we'd also love to hear what, so that we can add that back into the braid-http-01 draft.
> Braid is a proposal for a new version of HTTP that transforms it from a state transfer protocol into a state synchronization protocol. Braid puts the power of Operational Transform and CRDTs onto the web, improving network performance and robustness, and enabling peer-to-peer web applications.
> At the same time, Braid creates an open standard for the dynamic internal state of websites. Programmers can access state uniformly, whether local or on another website. This creates a separation of UI from State, and allows any user to edit or choose their own UI for any website's state.
to be very useful to set the overall motivation. If I could humbly request, I think having them in subsequent drafts would be very nice! Thanks for the reply and thanks for all the good work!
- do you think it would make sense to allow the "Patches" header only in PATCH and not PUT?
- how do you feel about a generic "subscribe" mechanism that is not specific to sync but can just say "I'm interested in this topic, with this params" ? Then this could be specialized with the version+parents params to get sync. This way we get a generic HTTP standard for PUB/SUB, which is badly needed, and is a very basic primitive you can build many things on. It would be a shame to have to add one after the fact.
I'm also curious what use-cases you have for a generic pub/sub beyond synchronization. In my experience, 95% of pub/sub implementations are used as a substrate for synchronization.
As for using PATCH vs PUT, this is an open question. I'd love to see more discussion of it on the mailing list: [email protected]. There are a number of pros and cons on both sides.
EventSource is only from the server to the client. Pub/sub goes in any direction: client to client, client to server, etc.
Crossbar.io provides that with websocket.
Eventsource + the sync rfc would mean everybody would build a non standard bridge for this to link a publication, a sync from the server and an event source. And because we only need 2, and they are overlapping, several completly incompatible de facto solutions would emerge.
Pub/sub is useful for any kind of communication that doesn't involve a resource: notifications of events , communication between microservices, etc. Basically anything that doesn't have a need for an history.
Of course, you can always create abstract conceptual resources you sync with to obtain this effect. E.G: the "streaming service is down event" could be a sub to a "service/streaming/heartbeat" event that you sync, and ignore versions and give no parents. It's just a bit twisted.
It feels more natural to have a pub/sub primitive that goes back and forth in any direction, and build the specific case for sync with that. Even if sync is 90% of the time what you want.
> "I'm interested in this topic, with this params"
Couldn't you just do this with URIs? Like if you "GET /topic/foo" with a Subscribe header you get the foo topic, and "GET /topic/bar" gets the bar topic?
> The reasoning behind this seems to be that the alternatives right now are either polling or a homegrown websocket based protocol.
Right. Same with routed RPC and routed PUB/SUB. I currently use the WAMP (protocol, not stack) for that, as it is a Webocket based IANA standard, but with http2/3, having the HTTP version of it would make sense to have this baked in as well.
In fact, their subscribe thingy should probably be more generic and accept a topic and optional params. Params could be then use to upgrade the use case, like version+parents for sync. Plus client may want to push events as well.
I don't know how one can contribute to the debate. Would you explain it to me?
> I've personally seen both PUT and PATCH used for updates, so this didn't seem particularly odd to me, and seemed more like a nod to one particular method of updates.
PUT in REST is for sending the full object, PATCH is for partial updates. So both are valid, but I would allow the "Patches" headers for the PATCH method only.
> I don't know how one can contribute to the debate. Would you explain it to me?
The official venue for IETF discussions is the mailing lists. Braid is being discussed in the HTTP Working Group, on this mailing list: [email protected]. I suggest drafting an email saying something like:
"Hi, I learned about the Braid spec on Hacker News. I am interested in it for reasons X, Y, and Z. Overall, my thoughts on the spec are W. However, the current draft allows sending patches in PUT, POST, and PATCH, and I would only allow the Patches header in the PATCH method. Does anyone have thoughts on this?"
Thank you! I'd love to have your thoughts contribute to the consensus process.
Yes -- depending on how you look at it. HTTP already has cookies to implement stateful sessions. Braid does add subscriptions; but HTTP 1.1 and 2 also has keep-alive at the TCP level: https://en.wikipedia.org/wiki/HTTP_persistent_connection
> It also uses PUT to patch things, but then why not use PATCH?
You can use PATCH, or even POST, too. We haven't settled on a single best method to use, and in fact you'll notice different methods being used in different specs, depending on the personal preferences of the author that wrote that spec. :) I recommend checking out the Range Patch spec for more: https://datatracker.ietf.org/doc/html/draft-toomim-httpbis-r.... You'll see a lot of PATCH in there. :)
Also, please feel free to start a discussion on the mailing list about this: [email protected] It's an issue that needs discussion and consensus more generally in HTTP.
People don't use it and a lot of web frameworks don't have first class support for it. The main benefit is making the request more semantic. Idempotency etc. isn't always that useful on the protocol level so GET & POST is more than sufficient for most purposes.
I misunderstood your original comment. The reason why there were 500 requests is because I was showing a background full of creepyfaces. It made the site look much nicer but it turns out it didn't scale very well.
Turns out the other heads were removed so it's not doing 500 requests anymore. So where does that leave us? Should we keep arguing over the original situation?
- you will mostly work on the same place (or you accept the burden of traveling with your keyboard and be "that guy" when you set it up. Personally for the same hurdle, I prefer a secondary screen on the go)
- you will mostly work on the same machine (or you have multiple keyboards, one for each machine, and if you are in a data center or tech support, you move with your keyboard).
- you will not be exposed to many different keyboards, or layouts (e.g: you don't need to go help users and customers on their machine that don't allow plugging in, you don't teach, you don't use your phone a lot, etc). Switching layouts all the time is a nightmare.
- you can afford the initial lower productivity (e.g: you are not a freelancer that needs a regular output).
- cables and taking space are ok. Taste is taste, after all.
- you have the money, and find it is better invested in this than say, a better screen, mouse, graphic card, battery, etc. And renewal. Or you have enough to have it all.
- you are certain of this model is what you need or you can afford trying many. There are many ergonomic keyboards. They are all special and expensive in their own way.
- your layout is available. I'm french, I use AZERTY. Or you are fine learning to type with the wrong letters, or using stickers. I often buy/user computers in/from the US, and just type from memory after setting the QWERTY to an AZERTY layout. One of my friend like Dvorak (actually Bepo, the fr version)...
- nobody else than you will use your computer. Or you have several setup and are ok to switch every time.
Now I understand that as it's my job, optimizing this key element of it makes sense.
But hell, that's a lot of per-requisites.