| ▲ | yomismoaqui 4 hours ago |
| The only constant in mobile development is churn. I had apps on Google Play and every year I had to upgrade libs, recompile and loose and afternoon (or two) to not win anything, just churn for the sake of churn. Compare this to plain HTML, CSS & vanilla JS. You can deploy a webapp today and if you are not using any beta JS Chrome API you will be able to use that site in 10 years without touching a line. |
|
| ▲ | rescbr 2 hours ago | parent | next [-] |
| Now compare this to Windows. You can run a Win32 program built in the 1990s, and it would work fine. |
| |
| ▲ | monocasa an hour ago | parent | next [-] | | I wish that were true. Modern windows won't even play crysis without a binary patch. | |
| ▲ | paulryanrogers 2 hours ago | parent | prev [-] | | Half the 90s was DOS and Win16 which got dropped a while back. Still, I salute them for supporting backward compatibly much longer than most. |
|
|
| ▲ | jimkleiber 2 hours ago | parent | prev | next [-] |
| This hits too close to home. I built an app for micro-journaling [0] in 2013. I think the iOS version stopped working in 2016, the Android version maybe a year or two after (I switched to iPhone so don't know for sure). The interactive demo site I built in JS? Still works exactly the same. And I tried to make the apps as backwards compatible as possible. Maybe AI could help make OS upgrade maintenance easier? [0]: www.ifeelio.com |
|
| ▲ | pjmlp 4 hours ago | parent | prev | next [-] |
| Unfortunely using plain HTML, CSS & vanilla JS feels like being a hipster in the age of using SPA or WebAssembly frameworks for displaying static text. |
| |
| ▲ | stronglikedan 3 hours ago | parent [-] | | > for displaying unselectable static text FTFY (but seriously, why do so many sites do that?!?) | | |
| ▲ | amluto 2 hours ago | parent | next [-] | | Unselectable static text is so last year. The cool new thing is these funny blue bits of text with click handlers that, when all the stars align, navigate to a different URL. Somewhere on the road map is context menu support, and the ability to open in a new tab is on the will-never-happen wishlist because no one can figure out how to do it in a cross-platform manner. Showing the target URL in a status bar didn’t even make the wish list. The <a> tag is only for retro fanatics. Seriously, I was peeking at the docs for Qwik, one of the cool new supposedly-lighter-weight frameworks the other day, and I was delighted to discover that, in what is obviously intended to resemble ordinary multi-page HTML, the links aren’t links. The long press behavior is utterly, comically wrong. This isn’t even unusual any more. I guess Qwik is proud that the JavaScript needed to emulate links is only 1kb minified and doesn’t add time-to-interactive overhead that scales poorly with page size, but literally every browser has had complete, native, no-script needed support for <a> even if the entire browser was a terminal app! Check it out: https://qwik.dev/docs/getting-started/ | | | |
| ▲ | wiseowise 3 hours ago | parent | prev [-] | | Mobile experience. | | |
| ▲ | yurishimo 2 hours ago | parent [-] | | It makes sense in some places; buttons, mostly so quickly tapping a button doesn’t zoom or whatever. I agree that a lot of people are lazy and block text selection sitewide though because it’s easy and makes the PM go away. | | |
|
|
|
|
| ▲ | wiseowise 4 hours ago | parent | prev [-] |
| [flagged] |
