test7777

do what chrome does, detect crash and fallback. what are sandboxes even for if you can't crash once in a while without whining too much about it...

you can scroll down to get the actual content. but get this, while that site is about UX, its UX is so bad you didn't figure that out right away.

oh my fridging gawd, i am so triggered by this. the site linked to is supposed to advertise a book on ux with some example content and yet literally every comment here is suggesting a way to improve on the UX of that with some even just downright reformatting the content as a comment.

i hope they don't sell a single book as this serves as an example of how to not do UX.

Tbh, it looks like they are ignoring the elephant in the room: intellectual property...

algorithms don't matter for shit to the person that controls the (mandatory) updates.

its the same issue with all modern e2e apps like whatsapp or signal, if there is a single client implementation its not secure at all to these kind of attacks.

Showing the deprecation message before the API that replaces it is actually out? Isn't that a bit of an a-hole move? I know everyone here is a developer and hates code older than a month, but really? Nobody gonna call them out on that?

you really think anyone cares how much of the corona you got in the particular blob of snot you gave for testing?

on a gel you see the size, something coming up with exactly the right size even at 35 cycles indicates that there was at least some of what you designed the primers on in the sample. if you want higher certainty, with three primers you can get two different sizes ruling out any doubt.

with the rtpcr machine readout which only gives you the signal corresponding to how much was amplified over time you need tricks like the dual labelling.

the issue is that the language arbitrarily decides those things should be treated as text with some arbitrary encoding when all of them are decidedly not text.

Python 2's "str" is a bytestring. All of those are bytestrings in Python 2 as they should be. Python 3 makes them text and suddenly i can not output data over stdout anymore without extra steps of switching the mode of stdout from some arbitrary text default.

unix pipes (stdin, stdout) are bytes, files are bytes, filenames are bytes. yet, for some reason python3 thinks al of those are text. its not the coders that are wrong, it is the language.