Hacker Newsnew | past | comments | ask | show | jobs | submit | taralx's commentslogin

Sadly, no. Both kernel and device drivers are in the HAL: https://blog.linuxplumbersconf.org/2017/ocw/system/presentat...


I saw this and was interested, but the link sadly only goes to a price chart with no discussion. It would be nice to know why it is dropping, or at least why people think it's dropping.


Because all bubbles eventually go pop.


I believe it is the case that no vote is considered a vote for the incumbent. So it's initially no vote, and then it is defaulted later.


If that's actually the case, then it seems very biased - it should just be a blank vote. Is that even legal?


PUSH is known as "weakening", one of the structural rules of logic.


Why is that a race? IIRC Promise.then is supposed to invoke the callback immediately (or on next loop) if the promise is already resolved.


It would be race-free if `.then()` was invoked synchronously when evaluating the `await` expression, just like in normal Promise-based code. Currently in V8, there's a delay between evaluating `await` and actually calling `.then()`. If the promise uses a sufficiently nimble scheduler (i.e. based on `process.nextTick`), its unhandled rejection handler may run _in between_, throwing an exception, polluting stderr and possibly killing the process.

Example with Posterus:

  async function main() {
    try {
      await Future.fromError('fail')
    }
    catch (err) {
      console.error('caught:', err)
    }
  }
In Node, this actually produces an unhandled rejection because Posterus's scheduler uses `process.nextTick` and squeezes into this unnecessary delay. Doesn't happen if you `.catch()` manually or just use Posterus coroutines instead of interoping with async/await, but it highlights the incorrect implementation of async/await in the first place. (Or is the spec at fault?)


Add this to the "Nature is Terrifying" list...


Sometimes nature fakes it.

https://cdn.ampproject.org/ii/w1200/s/img.rt.com/files/2016....

Pretty harmless, but they've been known to drag away mice.


This is the guy that wrote Google Interview University, previously on HN: https://news.ycombinator.com/item?id=12649740


One wonders how much more they'd save if they could use the more sophisticated version you developed. ;-)


24/40 - people are hard, weather is easy. I also have trouble associating names and faces.


Same here. Makes writing actually quite difficult -- I tell people it's like trying to put a whirlwind down the end of a pen.


This is actually one situation in which being able to touch type accurately and quickly is extremely useful. I can sit down with an empty buffer and my hands more or less keep up with my thoughts. Still wish I could go faster of course, but it's orders of magnitude less frustrating than trying to write by hand.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: