coddle-hark

23 ms·

211.
by coddle-hark 6y ago
Not sure what the author meant there but we do have a problem of offloading the ethical burden of our systems onto the algorithms themselves and it should be taken more seriously. Like when Google shipped an AI for moderating hate speech wh
212.
by coddle-hark 7y ago
That seems like it would be abused to the point of the semantic information being completely useless.
213.
by coddle-hark 7y ago
I’m interested to see how this plays out. I subscribed to LTT on Floatplane a couple of weeks ago but the lack of iOS app combined with the kind of unfinished feel of the website made the experience not very pleasant. I really like the idea
214.
by coddle-hark 7y ago
A level playing field is good for a challenge like this. Those that could solve it without these constraints are pushed to improve their existing approach. Those that don’t normally compete in these kind of challenges aren’t put off by a po
215.
by coddle-hark 7y ago
You’re focusing on single-threadedness like that’s a problem but it’s not. For example, you can run multiple processes on a single core system just fine — even if one of those processes hangs. AFAIK there’s nothing in the JS language that f
216.
by coddle-hark 7y ago
This only holds if they didn’t pour hours into the original solution. Setting up and managing 4000 node services doesn’t sound like a quick hack.
217.
by coddle-hark 7y ago
No it doesn’t. We’ve had good models for concurrency in single-threaded systems for a while now.
218.
by coddle-hark 7y ago
The whole point of async I/O is to be able to do something useful while waiting for tape to spin up. I don’t buy it.
219.
by coddle-hark 7y ago
He’s the CEO. It’s his job to represent the company. It’s his job to rehearse the slides.