fbergen

EU should focus on making an attractive startup market and more European LLMs (and so many other things) will emerge

Cool, makes you wonder how many more of these oneliners are scattered across the codebase (in application and also OS etc).

Sidenote, I wonder how close we are to detect these automatically. From profiling many various applications, it feels like that should be a tractable problem.

Thanks for the reply

I see, thanks for adding colour here I can see the benefits of a guaranteed immutable and permanent profiling data!

Indeed even seemingly non complicated things do have a lot of devils in a lot of details :)

Kudos of getting this out

Shouldn't "long term snapshot for profiling and inverting call stacks" be table stakes by now?

I'm more curious on how much manual effort was required to find said line of code? Strikes me as moest of these optimizations are super easy to verify, very difficult to find

What part of the stack takes the majority of the time for spawning a new replica? Is it the time to boot a VM/environment or is it application doing bunch of init work setting up connections etc?

Looks great!

Would this work for hosting databases too? I found the biggest annoyance and expense on my "infrequently accessed" side projects are databases, which are almost always idle.

Yet still people are using it?

Otherwise it’s called an MVP and a promise of plugging the holes

But you still have clusters, why not everywhere… ?

Am I asking too much? =P

I would love to have what we were sold as a “truly” serverless (even though the name doesn’t mean no server)

- CloudRun did a good job, but the autoscaling is too slow to not pay for idle

- Lambda is great, but I want to run way more complex workloads than simple functions

If they were only building them in volume

True, it doesn't mean that the problem is solved, but it's a big milestone on the way. I fwiw something I thought was way further in the future

For a different take. Have a look at runme.dev

It's all a question of time

I'm sorry, does this article say which metals were discovered?

Wouldn't Price to Book (P/B) sort this out?

I don't believe market cap to sales is a good ratio to look at when the margins are so different.

A forward P/E of 25 for a company growing 50% YoY is not unheard of.

Since you picked VW as reference, i had to look them up they have forward P/E 4.84 > trailing P/E 4.66 meaning they are shrinking (?)

> I've discovered recently that tire wear actually creates about as many particles as exhaust fumes,

> And the worst part for the wire tear (and I think road tear), apparently it scales to the POWER OF 4 (!!!).

That's very interesting. I'm a default sceptic, but would love to learn more, because if true, that could nullify a lot of the local air arguments. Do you have any sources for these?

I very much agree with you, and think it will hurt the company in the long term

But to give some credit where it's due: reimbursing all Stadia purchases is a very customer friendly way to shut it down

they keep iterating that foreign exchange is a big part of the non-US decline, but I fail to find how much in the PDF

Also see `scp -l 200 bigfile.iso name@server.org:path/in/destination`

from man page:

-l limit

Limits the used bandwidth, specified in Kbit/s.

While is sounds shocking at first, I'm curious why finding more occurrences of Pareto or 80/20 rule is still making headlines? It's almost like rather any deviation from that would be more surprising

IMO using things like [likely] has more potential to shoot oneself in the foot than improve performance.

Using real execution statistic to determine branch prediction (at compile time) should be the new standard