Live data from Hacker News

A single-page app is almost always worse than a multi-page app

151–152 of 152 posts

Re: A single-page app is almost always worse than a multi-page app

#151

Post by davvolun » Thu, Nov 01, 2018, 2:09 AM UTC

Isofarro wrote: post #130

bunderbunder wrote: post #88

Earlier quoted context omitted.

If it's public facing, that's a huge concern. If it's intended for business users, particularly if on an intranet site, it's often very easy to limit the number of browsers and versions you need to support to just a handful.

The Web has been collecting dates from users in forms long before date-pickers existed.

The Web has been doing lots of things poorly for a long time as well. I know I've seen some implementations of date-pickers I don't like, and more old school implementations without date pickers that were just clumsy.

Re: A single-page app is almost always worse than a multi-page app

#152

Post by davvolun » Thu, Nov 01, 2018, 2:10 AM UTC

thrower123 wrote: post #125

rovek wrote: post #77

Earlier quoted context omitted.

If you didn't use JS for date pickers, you didn't have very inclusive browser support - especially for something like a healthcare website. [1] Were the designs and layout of these SPA and HTML5/CSS3 website also identical? [1] https://caniuse.com/#search=input%20date

It's more than a little absurd that there isn't a passable date picker implemented across the major browsers. I have wasted far, far too much of my life fighting with different half-baked JS datepicker components already in my life.

Still better than supporting IE6.

Post reply on HN