Re:Why Are Cancer Guidelines Stuck in PDFs?
by hyhconito on Tuesday December 24, 2024 @06:19PM
(#42505676)
Because JSON is fucking horrible for humans?
If there's anything I want to read it's searchable paper.
Re:Why Are Cancer Guidelines Stuck in PDFs?
by shiroiushi on Tuesday December 24, 2024 @08:45PM
(#42506273)
>Because JSON is fucking horrible for humans?
It's better than XML at least.
Re:Why Are Cancer Guidelines Stuck in PDFs?
by hyhconito on Wednesday December 25, 2024 @03:23AM
(#42507664)
JSON has never been better than XML. People are just terrible at XML and don't want to learn.
Re:Why Are Cancer Guidelines Stuck in PDFs?
by jampekka on Wednesday December 25, 2024 @06:06AM
(#42508203)
"People are just terrible at C++ and don't want to learn."
Re:Why Are Cancer Guidelines Stuck in PDFs?
by hyhconito on Wednesday December 25, 2024 @06:27AM
(#42508272)
That too.
Re:Why Are Cancer Guidelines Stuck in PDFs?
by shiroiushi on Wednesday December 25, 2024 @07:01PM
(#42512091)
You could say the same thing about assembly language.
Now it'd be nice if these could be treated like source code on some sort of medical VCS, to be easily modded or even forked by sub-specialists. But wetware dependencies are way more complicated than silicon ones, and will remain harder to discretize for some time to come.
It's not that the author's aspirations misguided, they're great. But I believe progress in this area is most easily realized as part of a relevant team, because what looks conceptually simple from outside the system only seems that way because of a lack of resolution.