hhdhdbdb's comments

Already 8 years and being non profitable is forgivable for a hardware startup creating something new, especially a new silicon.

Depends why they are losing money. But losing money alone is not bad. This ain't an ice cream truck.

Agree groq implodes if demand for intellegent automation tanks (i.e. bubble burst), or competitors disrupt the disruptor. Another Z is all you need paper means my old laptop is running models fast or something means groq is not something you need.

They can probably pivot.

BTW OpenAI is 9 years old and they are a SaaS/PaaS running on Azure.

They never say that.

They say: Tesla shares up as revealations surface that the wind is blowing east.

AMD, Groq in the future, TMSC?

Edit: I will add Apple.

Yes I forgot to mention the implied: Homes, that meet code, with connected utilities in places people want to live that are not being landbanked.

Hard to know that unless you got some inside to what they were thinking during hire.

If it worked I wonder if it worked as a shibboleth.

Friendly would be win win. We'll pay you so you dont worry about money, and we win because you are great. Batna (looks better as a word) is there but in the distance.

Thanks for putting meat on the (speculitive) bone I threw out! Very interesting.

Yeah I am not saying all the time, but I am saying when it happens it can br less bounded than "human population growth in the early 21st century."

BATNA is kind of a dog whistle that this is a slighty hostile business deal. Hostile under the hood. Smiles and handshakes on the surface.

1. Tell them you have one other offer (or late stage interview).

2. Ask for more money and/or more shares (if you think the shares are any good).

Yeah. Nah that makes you sound silly (at least for software jobs) unless there is a good reason for it, like currency conversions or peverse tax incentives.

There is a tiny chance that asking for 133700 might get a smile at a smaller tech focused company though.

Why is fertility declining? I posit we are hitting non-food constraints. Political ones. Land use constraints. If you build millions of homes fertility will go up.

Bitcoin is a pure exanple thay shows the limit to energy consumption is how much money people have to throw at it. And if that money is thrown into generating more energy it is a cycle. There is no stomach size and human reproduction constraints. We can waste power as quickly as we can generate more.

The only hope is to generate this power greenly.

How is this a narrow niche?

Chain of thought type operations is in this "niche".

Also anything where the value is in the follow up chat not the one shot.

A gravitational wave requires an event like a black hole merger, or basicially somerhing to move and change the field, right?

In this case, how does the fact that a big object is still influencing space/time around it communicate that fact when it is not moving. Is that still gravitrons?

I think I said a lot more than TFA on those points.

Google can't please all of the sites all of the time, or all the visitors.

It is too big to evem worry about that 4k a day clicks for one site. It is like us optimizing the expense of 0.01c. It makes a difference when that 0.01c is an API call that you call a million times. But it only surfaces if you do aggregate it.

Therefore this problem can only even be seem by Google if it can be surfaced in aggregate overy say a billion queries.

I wonder how that can be done.

Probably only can be done using data. Which means spying on people in various ways. And making assumptions about length of time on site equals quality.

They probably use machine learning too. There may be no reason for the lost rankings other than a wind change caused by some updated parameters in an OKR chasing model.

I must be the exception! A big survey on this would be interesting to go from anecdotes to data.

Any timing attacks possible on a virtualized system using dedupe?

Eg find out what my neighbours have installed.

Or if the data before an SSH key is predictable, keep writing that out to disk guessing the next byte or something like that.

Thanks for the reply. These are compelling points.

I agree not to fail on insert too by the way. The insert is sort of an enqueuing action.

I was debating if a microservice should process that queue.

Since you are a PaaS the distinction might be almost moot. An implementation detail. (It would affect the api though).

However if Postgres added this feature generally it would seem odd to me because it feels like the DB doing app stuff. The DB is fetching data for itself from an external source.

The advantage is it is one less thing for the app to do and maybe deals with errands many teams have to roll their own code for.

A downside is if I want to change how this is done I probably can't. Say I have data residency or securiry requirements that affect the data I want to encode.

I think there is much to consider. Probably the why not both meme applies though. Use the built in feature if you can, and roll your own where you can't.