zlacker

That website is ancient. The layout is done with tables and there are bits of code in there specifically for IE7.

That means it'll work on anything. The old desktop PCs that sit around in public offices for decades will display it with no problems. Compare that to a beautiful, modern website from a rival that plain won't load let alone render on that ancient computer.

The one with the working website wins the contract.

>>onion2+(OP)
What's wrong with making your landing page render for everyone? Mine also sort of works in ie7

>>yread+p2
Nothing, and you really should, but companies don't because they want to make all modern shiny stuff without putting the effort in to make something that does progressive enhancement properly. That's why contracts for police websites go to companies whose websites look like crap.

>>onion2+(OP)
What does table based HTML have to do with functional and web-accessible websites? Especially in the age of mobile which represents ~50% of traffic .

>>yread+p2
There is a difference between using CSS/HTML from 2005 and using server and network security from 2005.

>>dmix+Z5
What does table based HTML have to do with functional and web-accessible websites? Especially in the age of mobile which represents ~50% of traffic.

Lots of things.

- Screen readers expect HTML tables to be tables. If there aren't things like a caption the screen reader can inform the user of a problem.

- In a lot of cases the table won't inline in to a logical structure for reading out. A screen reader will read cells out from left to right, which interleaves content from one column with content from another when that isn't the intent. CSS layout will usually read better.

- Table-based layouts use a lot more code than CSS layouts, which is more to download and more to parse.

- In the case of that website in particular, there's a ton of inline styling which is more unnecessary data to download.

- Using tables for layout makes it much harder to develop truly responsive layouts for mobile; doing things like hiding download/battery intensive page elements is much harder (especially if those things span several cells). That site does have some media queries for controlling styles, but it could be doing more.

>>dmix+Z5
As the poster above hinted a lot of public offices have outdated hardware and software that is not a consideration for a lot of developers. Mobile represents ~50% of traffic among the public - not among the people who were selecting the developer using the "archaic" technology that they have in their offices.

>>onion2+(OP)
But there are many enterprise saas products out there with solid security, decent UX and support for older browsers.

I think that they won these contracts with more “who you know” advantages than technical.

>>hypewa+Hf
The trick for government procurement has always been to respond to the RFP with something that's like 98% a solid proposal, and then 2% stupid bullshit and gotcha style requirements that only you can fulfill. Then should they accept your proposal, and move to RFB, you've already won even before pricing comes into play.

>>onion2+(OP)
>The layout is done with tables

You'll be amazed to see how is layout done here on HN.

>>onion2+(OP)
If only we funded the police with trillions of dollars, then they could use that funding to update their computer systems. Awe well, guess it comes down to the old saying "you can't have your assault vehicles and system security too"

>>johnma+vE1
> then they could use that funding to update their computer systems

But why? It seems like a waste of money.

>>onion2+Oc
That missed the point of my comment. Wasn't arguing 'for' table designs.

>>Raidio+ca
Yeah it was kind of cool that the page loaded in like a couple hundred milliseconds.

>>depend+OF1
I interpreted your parent as pure sarcasm. The US government did throw hundreds of billions of USD at state and local police, anti-terrorism, and surveillance (including fusion centers for each state). They have no excuse for screwing up the security of their intelligence exchange (except we have come to live with low expectations for government organizations).

>>thephy+Ka2
I interpreted said post as sarcasm that implied that the US police should have gotten rid of their older computers and get new ones that can run fancy JS and electron. Nothing to do with security, only about wasting money.

>>depend+At2
If they current pcs cant run electron, they likely can't run latest office either. It's probably still the age of win7 there, might be 32bit as well. With ancient Acrobat reader as well.

This has everything to do with security. They are one click away from getting whole department pwned.

>>yread+p2
It actually doesn't render properly for everyone, and in fact renders incorrectly in chrome: the nav links (Home, Features, Support) overlap with and intersect behind the main content.

Of course, you probably won't notice this unless you're using a dark mode extension like me, because under normal circumstances, those links are invisible, since they render white-on-white.

Also, tables play poorly with mobile and are usually the opposite of responsive.

>>aj3+GV2
> If they current pcs cant run electron, they likely can't run latest office either

I honestly doubt that. Office is surprisingly much lighter when compared with any electron application.

Anyway, chances are that they are running more than one program at once. Plus they do not really need to use office.

> It's probably still the age of win7 there, might be 32bit as well

funfact: win10 also has a 32bit version, and it works just fine on computers with limited ram

> With ancient Acrobat reader as well

Should have used Zathura instead.