3 ms·
> If someone has screwed up the regulations so badly that this information intended for the public is not actually public, then of course that's where the probl
by mkr-hn 13y ago
> If someone has screwed up the regulations so badly that this information intended for the public is not actually public, then of course that's where the problem is, but that seems unlikely to me. It would make for a very interesting news story, if true.
Healthcare.gov is covered in HN-popular libraries, software, and toolkits (like Bootstrap, jquery, and Drupal[1]), so the problem is apparently not that they just don't know any better.
It appears they went as far as they could with the latest and greatest tech. Someone somewhere along the chain of command failed to include a "provide any kind of useful information on the plans" provision in the design document. All signs point to this being either politics or negligence, not technology.
[1]I'm assuming on this one since WhiteHouse.gov has been covered in Drupal in the HTML and JS since the Obama administration took it over.
- DennisP 13y agoDrupal generates pages dynamically, usually from a database, which is the exact opposite of what I just suggested. Static pages are the way to go for very high volume. (And as dynamic frameworks go, PHP didn't actually do that well in the techempower benchmarks, though Drupal wasn't one they tested.) Certainly the design is the root of the problem. You have to "apply" before you get any information. When I say that the team screwed up, I definitely include the people who designed it, not just the programmers who implemented it.
- deleted 13y ago[deleted]
- mkr-hn 13y agoI was right: https://news.ycombinator.com/item?id=6514775 https://news.ycombinator.com/item?id=6514775 Poorly-implemented technology was at the core, but it happened because of a flawed and entirely political process.