I host my blog using plain HTML and I have a compile step - a Python script that converts markdown to HTML, which minimizes the energy I spend on... wrapping everything in HTML tags?
> I host my blog using plain HTML and I have a compile step - a Python script that converts markdown to HTML, which minimizes the energy I spend on... wrapping everything in HTML tags?
If you have a business website, customers expect a clean site with good visuals and a great user experience. Unless you are as big as Amazon. Sadly overengineering things is a necessary evil nowadays. If I had the choice I wouldn't even build websites mobile friendly but well... got no choice.
Customers will use the thing that feels best, if there's a different tool that offers more but looks bad, most customers won't swap. People will use what they are accustomed to.
I used some build of blender on windows mobile, crazy how efficiently it worked on 400Mhz HTC Niki, just the screen size, so the performance part seems to be done since forever :D
I would also compare reading to being reprogrammed like EEPROM. Although the process is slower, the changes feel more permanent when learning: you need to create connections yourself from examples compared to someone demonstrating it on the video.
It sort of was debugging because I'd written a ton of stuff for them in 1-2-3 (on site). This was their accounting system for a small business and I was "debugging" something rather simple: they weren't getting all the columns printed on their dot matrix.
Mobile is indeed supported, although the performance is not yet as nice as we would like.
The trickiest issue is input, since the "look around with your mouse" interaction maps very poorly on a mobile platform where "mousemove" implies touching / clicking.
We plan to eventually figure out a mobile-optimize UX, but we will most likely prioritize improving the performance first.
There’s no proof nor counter-proof that human brain doesn’t work like that.