remember a guy who worked in some fany BLUE in basic developed application for accounting on his dosbox windows xp. he wanted a new tool, he had a bunch of web

remember a guy who worked in some fany BLUE in basic developed application for accounting on his dosbox windows xp. he wanted a new tool, he had a bunch of web apps made for him, but all the time he hit the simple fact, that page refreshes and lack of keybindings made his work incredibly tedious and slow. Made a curses implementation of his old application so he could work full speed with the exact same interface and keys. a modern implementation of his oldskool app, so he could finally ditch dosbox and windows xp for a more modern operating system. happy chap after that, he wondered why people even use web UIs for local things. funny lesson in that 'modern' doesn't mean 'fancy', just like in this case. you can modernise something and not make it fancy, that is what they wanted. this guy made it fancy, which is useless. i try to tell people (hard to hear for IT people i know) that internal applications are not 'user apps' in the same sense a website is. so they should be treated differently as well. if you would ask the users what they want before redesigning the thing they use for hours a day i'm sure such mistake can be prevented.