301 karma · joined October 14, 2008
@reconbot@toot.cafe
github.com/reconbot
roborooter.comI wish I knew about python's [itertools](https://docs.python.org/3/library/itertools.html) before I started making [streaming-iterables](https://www.npmjs.com/package/streaming-iterables#api) for example.
DragonFly belongs to the same class of operating systems
as other BSD-derived systems and Linux. It is based on the
same UNIX ideals and APIs and shares ancestor code with
other BSD operating systems. DragonFly provides an
opportunity for the BSD base to grow in an entirely
different direction from the one taken in the FreeBSD,
NetBSD, and OpenBSD series.
DragonFly includes many useful features that differentiate
it from other operating systems in the same class.In 2018 I'm using an app to take screenshots of QR codes to generate one time codes. It's a sad state of the art, we need to do better.
It sucks there was fake content in there, but the device was real and the fake actions removed.
I would love to, but not all node versions and not all streams support async iteration yet! Also theres is a lot of utility to some of the stream types in bluestream. Concurrency for one thing. I've been working on an async iterator version of this but haven't yet started using it in production yet.
const stats = await pipe(
Nodes.scan({ fields: true }),
map(generateStats),
tap(() => count++),
reduce(mergeGraphStats, {})
)
and have generateStats and mergeGraphStats be async functions and not have to worry about error handling and pushing more than one object at a time in a read stream. We use it to process billions of events and objects a day. It makes nodejs streams fun to use.Hope you find it as useful as we do.
The Bustle stack looks like Redis/Elasticsearch => NodeJS Lambda GraphQL API layer => (sometimes api gateway) => NodeJS lambda render layer => api gateway => CDN. We're working towards removing all the api gateway usage if possible with smarter CDNs like cloudflare workers and Lambda at edge, but it's not currently possible.
This setup gets us an average of 70ms api response time and less than 200ms worst case rendering time. Higher than 90% of cache misses never gets the worst case as we can serve stale content in those cases. Lots of room for improvement too. =)
From a local controlling agency, from unifying our commuter rails, from joining with the path. All these things would be good for the city and people who live here but I cry because I'll never see a sliver of it in my lifetime.
I think destroying competition is something wrong. "Trust us completely forever while we ruin your ability to function without us" isn't something anyone should everyone should have to do. The tax breaks offered to them for their new headquarters (that could "pay for themselves" in 10-20 years and will bring "lots of jobs") are insane, and they don't come close to completely controlling all the markets they operate in. I shudder to imagine what they'll look like when they do. But are they abusing anything now? Lets look into their lobbying, their warehouse temporary workers, their deals with the USPS, and what it's like to be one of their delivery drivers. It sucks to work for Amazon.
I know when trying to bring "Amazon Fresh" to NYC, they failed because the only terms they'd offer truck drivers were crazy high risk and low pay and NYC is a big enough market they could collectively resist. That's not going to last forever.
I'm not against innovation, I'm not against your margin being my opportunity, I'm against living in an Amazon controlled world.
I know some people on the team, they're great. But I also have a long history of working with microcontrollers in a semi educational setting (http://nodebots.io) and these are by far the least frustrating way to use wireless anything I've come across.
I'm thinking 200k nodes and 2 million edges? Graphviz segfaults graphs a fraction of the size and even at that scale a node by node representation isn't super helpful without being able to zoom out and look for patterns.