* Posts by daveyeager@gmail.com

7 publicly visible posts • joined 3 Jan 2018

It's time to reveal all recommendation algorithms – by law if necessary

daveyeager@gmail.com

This article is fake news

“ an algorithm that promoted owner Elon Musk’s tweets above all others, promoted specific political interests - and that specifically will not promote tweets directly pointing to LGBTIQ+ words, concerns, or themes”

Can the author of this article provide any solid references to these serious accusations?

Tesla ordered to pay worker $3M-plus over racist treatment

daveyeager@gmail.com

Bad incentives

It’s terrible that the first trial resulted in a $100M+ payout. That creates the wrong incentives for employees and their lawyers to scheme and blackmail companies. If you want a meaningful way to punish a large corporation then issue a large fine and a smaller more reasonable settlement to the individual.

Google says its artificial intelligence is faster and better than humans at laying out chips for artificial intelligence

daveyeager@gmail.com

Some key info missing from article. Placement is done using traditional algorithms and always has been automated. I guess the key here is that floorplanning & layout are different and up until now have been best done manually. Would be great if article elaborated as to why these two steps in the design process are different where the latter doesn’t lend well to traditional algorithms.

FYI: Today's computer chips are so advanced, they are more 'mercurial' than precise – and here's the proof

daveyeager@gmail.com

Isn’t this just another one of those things IBM knew about decades ago? I’m pretty sure they built in all these redundancies into their mainframes to catch exactly these types of very rare hardware malfunctions. And now the new kids on the block are like “look what we’ve discovered”

Things I want to know: are they becoming more common because more cores means a higher odds one will go haywire? Or is it because the latest manufacturing nodes are less reliable? Are per transistor defect rates actually increasing? How much more prevalent are these errors compared to the past for the same number of cores or servers? Lots of unanswered questions in this article.

Kernel-memory-leaking Intel processor design flaw forces Linux, Windows redesign

daveyeager@gmail.com

Why not just use memory fences?

I don't know the details about this bug, but if speculative execution from user to kernel mode is triggering the issue as described in this article, then wouldn't memory barriers fix the problem? Couldn't they just insert them at the start of system calls, interrupts, and context switches? There must be more to it.