weitendorf

60 ms·

421.
by weitendorf 3y ago
https://gnet.host/docs/about/overview/ - This is a very similar threading model to envoy [0] and lmax disruptor [1]. Unfortunately IIUC writing this in Go still prevents the spin-locked acceptor thread from a
422.
by weitendorf 3y ago
I think "OS" has too much baggage as a term for what Karpathy was describing. As a term, it implies a specific kind of implementation that doesn't necessarily reflect the high-level properties he laid out - all the user journ
423.
by weitendorf 3y ago
I'm biased having worked on GCP, but I think GCP actually has a very good track record of not sunsetting entire products or removing core functionality. When I worked on AppEngine, I would often see apps written 10+ years ago still chu
424.
by weitendorf 3y ago
I worked on AppEngine (well, Serverless Compute) at Google for over 4 years and left on Friday. Did something happen to AppEngine in the last week?
425.
by weitendorf 3y ago
An inherent problem with data engineering dag frameworks is that they are not directly integrated with the nodes, they live above the nodes. The nodes don’t know about the DAG and depending on the software they’re running they’ll have diffe
426.
by weitendorf 3y ago
In terms of the theory covered here it doesn’t really matter whether the edge is a cloud region, CDN, server in your building, or personal device. I don’t think any of these havent been tried as nodes in a distributed transactional databa
427.
by weitendorf 3y ago
Regarding cost, it can depend a lot on your traffic structure. If traffic is bursty, or substantially different between intraday peaks and troughs, it can be more cost effective. Solving this yourself costs dev time. >reduced time spent