I have thoughts. And das Keyboard.
Having typed a lot -- as a proper touch-typist -- and, of that, I've typed about 60% program code (in many programming languages) and 40% natural language, that latter split about 90% English, 10% German -- I have thoughts about keyboard design. I'm also a pianist.
I think the thing that makes mechanical keyboards seem noisy has nothing to do with the switch but rather with the way the key's action encourages the user to type and bottom-out the keys. It's the plastic cap hitting the back-plate that's loud, not the Cherry Blue switch (continuing the article's mention of that, the One True Switch) passing the activation point in the stroke but, simultaneously, the great mechanical positive reinforcement cycle of the Cherry Blue's action absolutely does feed-back to the human being at the keyboard and result in the kind of striking that results in an LTE: Loud Typing Event.
The solution is clearly apparent: designs should focus on key switches that have lots of physical feedback connected with their actual activation point and then deaden the noise by damping the bottom-out clack. Users then will learn to percieve the real actuation and not miss the lack of a clack.
Importantly, the dampener cannot be rubber and must not spring the key-cap back upwards because that feels "bouncy". It needs to be very thin, but accept just the right amount of deformation on impact to deaden the sound without feeling "squishy". (I'd guess cork would be GREAT, but far too pricey) I'd draw the response curve I'd want, personally, but not in ASCII art because I'm tying on a laptop keyboard, here, and I think we can be unanimous on declaiming those as the worst. (Also: I don't have spell-check, apparently. Thanks, Firefox.)
Unfortunately, though, there really is NO innovation in the keyboard world, alas, and what innovation there is is focussed on entirely the wrong things: RGB lighting and adding proprietary and useless extra features that don't work because the only way to use them is with the manufacturer's proprietary and non-functional "driver" bloatware: here we find the true realm of their innovation in excelling at making something as terrible as imaginable in some kind of sordid bid to be worst.
I have a keyboard in a cupboard that is also a mouse. The proprietary software thingy is also a mouse driver. Why? Because the keyboard has no pointing device features but, by using that bloatware, you can remape the scupper'd "mouse"'s "scroll wheel" to control your audio volume! Sometimes. On a good day, one ending in the letter ':qa!'
That brings me to my own personal favourite which I do carry with me like a gilded Morse key, to coding jobs: the das Keyboard 4. Personally, I find the Cherry Brown switches to be a nice near-equivalent to the Blue with just a little less activation feedback but enough to never create mis-strikes or suffer button bounce (I've used Razor stupid-premium "Optical" swiches that literally double-press themselves because of button bounce!) and the Brown are a little more socially acceptible, I find, from listening to the peanut gallery.
The das Keyboard's volume wheel sends scan codes for media volume up/down and works on every desktop OS, without any drivers. It has a bomber aluminium front-plate that makes it seem like you could drive a Panzer over it without worry. It uses only a single USB A port but has a built in USB 3.0 hub that literally is the best USB 3.0 hub I have ever used, ever! (To those in the know: I can connect to `adb` debugging on Android devices without needing to scrounge up the Specially Annointed USB cable when using my das Keyboard's hub. Any semi-decent cable will do. It's like magic!)
They don't like wine, tea or beer, though. Since I discovered the das Keyboard about ... er... well over a decade ago, I've killed three with those beverages, respectively. (One actually still works (mostly) but sometimes registers an extra right-shift when pressing many keys at once which leads to wierd surprises when coding, a lot.)