I love go, but I find it did little to make concurrency management easier to reason about. Race conditions are easy to write. Go routines have all the same concurrency problems of threads.
In the parallel HTTP fetcher, the error is discarded. This will likely result in a panic when the response is nil. Also, what if it a server locks up? Or the underlying socket never connects and never times out?
I know it’s a toy example, but one must consider all these things in a real system. Go does have good pathways for these concerns, but it’s also easy to do it wrong. I still have to manually reason about access to variables/struct fields from multiple go routines.
The documentation reference a “decode” function, and it’s imported to the example code, but it’s never called. I’m not sure what the API is after reading the examples.
The output of the transformation layers are a collection of embeddings in the latent concept space. Those can be fed into an addition model to extract semantic segments, bounding boxes etc. IIUC this is how dinov3 works.
It’s the same assumption is required for any hole punching handshake (including STUN).
> This is a property called “equal delta mapping”
FWIW I’ve worked in computer networking for 20 years and have never heard it called this. This blog is the only source that comes up when I search for that exact term. I wonder where the author got it from.
The foundation models themselves will be cheap to deploy, but we’ll still need general purpose inferencing hardware to work along side them, converting latent intermediate layers to useful, application-specific concerns. This may level off the demand for “gpu/tpu” hardware, though, by letting the biggest and most expensive layers move to silicon.
> Quality of code has never had anything to do with which products are successful. I bet both youtube and facebook's codebase is a tangled mess.
The code’s value is measured in its usefulness to control and extend the Facebook system. Without the system, the code is worthless. On the flip side, the system’s value is also tied to its ability to change… which is easier to do if the code is well organized, verified, and testable.
Undercut competition.
Use borrowed money to sell rides under cost.
Wait for all competitors to die.
Jack up prices.
AFAIK they’re still living on borrowed money.
It reminds me of the airline deregulation of the 90s. New airlines would use borrowed money to sell seats at below cost to attract customers, driving established carriers out of business.
The funny thing is that this smells a lot like “the tragedy of the commons”. Everyone wants to use this amazing infrastructure for flying, but no one wants to pay for it. New firms undermine the stability of the system by charging less than cost in order to starve established competitors whose business model is focused on being profitable.