|Chrome removes backspace to go back|
|By Thom Holwerda on 2016-05-20 11:22:25|
The reason we're making this change is that users regularly lose data because they hit the backspace button thinking that a form field is focused. After years of this issue, we realize we're not going to have a better way to solve that problem.
I absolutely hate this change. I deeply, deeply, deeply hate this change. This is a classic case of instead of addressing the core problem - web forms shouldn't lose their content when you navigate back and forth - you just try to hide it a little more by making navigation harder.
Emblematic of software development today, especially in operating systems: instead of fixing core problems, let's just add more layers to hide the ugliness. You see it everywhere - from still relying on an operating system written for timesharing machines with punchcards, to trying to hide broken, complicated and obtuse file system layouts behind "just use convoluted cloud storage".
People carrying around ugly battery packs just to get through a day of use on their devices running an outdated timesharing mainframe punchcard operating system from the '60s tells you all you need to know about the complete failure of modern software development - and this tiny little change in Chrome only underlines it.
Good software does not exist.
- Solving the mystery of the OP1 processor in the Chromebook Plus - 2017-02-23
- Google's not-so-secret new OS - 2017-02-15
- Open-sourcing Chrome on iOS - 2017-02-01
- Google AMP is not a good thing - 2017-01-24
- More related articles