AlphaSite

Forward P/E.

You can always tell it your preferences and ask it to remember them if you need it to.

GPUs/XPUs are small and solid state so it’s only really price that’s a huge liking factor.

And the disinclination of these companies to push the weights of their cutting edge models into people’s cars where they can be dumped.

Yeah. Every major self driving model that I’m aware of is fully e2e at this point. Going from fused sensor output to control+debug vectors.

This is more generalised.

But also since there’s a huge volume of data it’s too expensive to just keep scaling compute up (per car overhead) so there are necessary tricks involved.

I do think having a large model that can do this means that a small specialised model could be distilled form it though. Which is probably the most feasible path to production IMO.

There’s an opt out so I’m blade for now.

I know it sa toy, but if someone gets the bright idea to do this for real: please learn from npm and dont duplicate packages for every clone of a project. Share them between projects like every sane package manager.

My beef with etcd is that its neither performant nor reliable.

Its very much {reliable, performant, flexible} pick none.

I mean its capex vs opex, assuming a 5 year deprecation period thats 1.2 million isnt too bad, its 10% of their aws spend.

If you architect properly it doesn’t necessarily follow that more features means more attacks, or certainly not more system wide attacks.

If you layer and segment correctly you can build atop a secure core and have some decent security.

AMD had an interesting take on this around a decade ago. Never went anywhere but very cool tech.

Reddit doesnt work because subreddits crosspolinate and float to the top so theyre rather prone to brigading and intermingling. We don't really get distinct subreddits anymore.

I think models will be a commodity sooner rather than later. This whole race doesnt matter. First mover advantage is real, but over enough time it wont matter.

It probably means they’re close enough that there’s no observable difference. Or better at every different things.

Yes. Make sure you’re not using the Gemma sparse models since they don’t have a small model to use. Also I removed all the image models from the workspace.

I knew a guy who worked on it tell me actions is just literally a fork from Azure Devops. Which is why it never really fit into GitHub.

I think for the same model wall time is probably a more intuitive metric; at the end of the day what you’re doing is renting GPU time slices.

Large outputs dominate compute time so are more expensive.

IMO input and output token counts are actually still a bad metric since they linearise non linear cost increases and I suspect we’ll see another change in the future where they bucket by context length. XL output contexts may be 20x more expensive instead of 10x.

its mostly because MCPs handle auth in a standardised way and give you a framework you can layer things like auth, etc on top of.

Without it youre stuck with the basic http firewall, etc which is extremely dangerous and this is maybe the 1 opportunity we have to do this.

The cool thing is you can host your own node with its own rules; you should host an anonymous server and you can set the rules.

I think if people had a use case for it they’d buy more of the damn things. Right now I’d never need a device separate from my spouse since I just don’t need one.

Make is useful and buyers will come. The never had issues selling multiple macs frankly.

Probably some custom model built for their hardware.

Speed would be nice, but more than that I want it to also manage Ruby installs. I’m infuriated at the mess of Rubys and version managers.

i assume therye trying to build some community before trying to standardise it.

Voting can be coordinated between the N cpus rather than an external arbiter (even making that redundant eventually required the CPUs to decide what to do if they disagree so may as well handle it internally).

Honestly. We used dex. It worked pretty well.

Ruby is a language that optimizes for the local maxima at the cost of the global maxima.

Now every library, company or code base has its own pattern and you have to learn its pit falls. Better to learn once, cry once and just deal with it imo.

As they say, good enough is the enemy of perfection.

eh. Ruby makes it easy to do the wrong thing. imo.

It’s another step in the right direction. These things take time.

Connection pooling has its own severe downsides in Postgres. Considering how limited we are by connection counts.

That was the whole concept behind KCP iirc. It was designed to provide tenancy atop 1 or more clusters.

Types don’t explain intent or gotchas. They’re also useful, but you need both.