>Yes, I believe US hospitals are legally required to maintain and test backup generators in case power goes out.
And even that only does so much, it was 45 years ago but my Grandmother had a stroke on the operating table because the power went out and generators didn't kick on until someone could run and manually start them because the autostart failed.
A bit ago a semi-retired guy came back to help with some stuff including debugging serial ports. It was very cool to see him fiddle with the knobs and be like "oh those squiggles look good" "no that doesn't look right" etc. https://i.imgur.com/R5aEXbq.jpeg
Meanwhile total mystery to everyone else how to operate/interpret the machine but a lot of fun
Jumping off the title and ignoring contents of post, as is customary:
look at this graph and guess which languages use each number of dependencies for their website: https://www.youtube.com/watch?v=E82ly38YEEQ&t=325s
I won't spoil the claim in the video about what the dependency number is correlated with, and I'm not even sure how true it is in general, but it's very interesting.
This comment by yurishimo should not be [dead], imo
>Just a heads up but datalist is not really a great solution if you need a strong contract. The user can still type whatever they want into the field and there is no fuzzy filtering or typo mitigation. Once you add those requirements, a library that gives you a more fully featured combobox is likely going to make a lot of sense in your project.
It is true! HTML can do a lot of cool stuff, it might get you 100% of the way depending on what you're doing. But if you have a lot of forms where users pick from a value set, and want to enforce no other strings and get a good search experience, datalist does not get you there.
Thanks for the vouch! The rest of the article was indeed good but I find a lot of value in hacker news comments precisely because someone comes back to the comments and lays out why what I just read might need a different perspective. If you just want to see cool stuff that a browser can technically do, we are all capable of reading the Chrome dev blog, but we come to HN for a wider perspective. Someone telling a war story about how some little tidbit came back to bite them is also valuable (imo).
(iirc if you have [showdead] on you can click on the timestamp to the comment and will get a [vouch] option as a reverse-flag, fwiw. i see it and don't have showdead enabled, so enough people have re-vouched it!)
I mildly disagree. You still have to validate what the browser gives you. The user could have edited the "strong contract" using browser dev tools.
So, let the user type, then validate in javascript if you want instant feedback (by changing colors, say, to red / orange), but ideally don't fully block it from being seen by the server. And do the real validation on the server side. This is what I found to be fairly robust, while allowing mitigations if a bad rollout breaks something (delivering to clients is slower than updating something on the server side, most often).
Where did I say to forgo backend validation? Of course you validate on the backend as well, but the better UX would be to prevent the user from entering a bad value to begin with, assuming it fits within your team’s performance budget.
I’m not advocating for willy-nilly package inclusion, just highlighting a current shortcoming of datalist that is often not mentioned in these sorts of articles.
I definitely remember seeing a post by a Chromium maintainer talking about starting development on a proof of concept implementation and surveying for semantics.
it is relatively new and untested irl, but interesting as gleam is very nice for fhir in some ways:
-fhir choice types imo were originally designed for some kind of object oriented polymorphism, but are nicer as sum types
-cardinality works nicely with Option for 0..1 and List for 0..*, the only ugly part is if you need primitive extensions and suddenly there are a ton of Option fields
-works with whatever http client you need for erlang or js target, meaning can use on server or in browser
hl7v2 is much uglier than fhir but commonly used eg by state immunization registries, so I am considering gleam types that have message/segment structure, but leave each field as String (as opposed to gleam fhir which uses Bool or whatever for primitive types)
after that not sure some kind of gpl toy emr probably a stripped down version of openemr that uses gleam/lustre and a fhir server instead of php, but this is definitely the mysterious step 3 ??? as there are a lot of features and integrations that take a lot of work or use different formats (hl7v2, ccda...)
Of course proof by analogy is silly anyways, my email going down is not nearly as bad as a patient's medical equipment going down.
reply