bberrry

If you are already in a reactive framework, why would you change to virtual threads? Those frameworks pool threads and have their own event loop so I would say they are not suitable for virtual thread migration.

> > Hiring on merit will be a permanent policy at Scale.

> Isn't this what everyone tries to do?

You seem to have missed that meritocracy has recently become a bad word and undesirable in some political circles.

You mean _invents_ details.

I like your custom prompt. I'll be trying it out for a while!

If you have speed you can generate multiple answers and have another model pick the best one.

I'm really happy they are reconsidering the syntax. Thanks for the link

I know it's silly but I sometimes feel anxiety at the prospect of that enormous bank of knowledge getting lost in some way or another (e.g. Google deciding it wants to do something else or some disaster).

It is truly invaluable to _humanity_

I used to have these complaints but the past 4-5 years have been smooth sailing for me. Perhaps I'm lucky. I use BT devices all day long (Bose QC35 II with Macbook, Pixel Buds Pro with Google Pixel 4 and more recently 7 Pro). Have to confess I rarely use BT in combination with Microsoft Windows though.

And how does that translate to lower pay in your mind?

What in the world do you mean exactly?

Could use minutes played instead of tracks played then.

> The company pays 70% of its total revenue to rights holders.

https://en.wikipedia.org/wiki/Spotify#Business_model

Ironically it's widely known that the labels get 70% of all music revenue and Spotify gets to keep 30% for itself (which famously hasn't been enough to even turn a profit). You couldn't be more wrong.

I don't think it's easy at all without access to the training data. I could ask about some information I find obscure in my native language but I can't be confident someone didn't write about it in English on e.g. reddit.

Do LLMs really encode knowledge regardless of language, and tap that knowledge irrespective of which language you query in?

My mental model of LLMs being next-word predictors with a long context window suggests they don't. Are there any papers on this?

Yeah we had ELK for the common logs. This file was a special case that we didn't want indexed and widely accessible because it contained sensitive data. I only occasionally needed to do some digging, so I was fine resorting to ripgrep.

What are you all doing that requires such a large context? Pasting in multiple articles of documentation?

If you grep GB+ sized files, you'll love it.

At my previous job I often ended up searching raw log files sized around 5-8GB. Regular grep would grind away for 50-60 seconds, while ripgrep returned the same results in 250ms.

I was shocked the first time I used it and have sung it's praises since.

I can't help but think if you're teetering on a knife's edge, only holding on thanks to hyper tuned GC params, then you should take a step back and consider getting out of that predicament.

The reactive patterns are now obsolete and will die. And good riddens I say.

As a Kotlin dev you should still be excited by virtual threads in Java 21. You'll never have to use coroutines again.

Gotta recommend this guy, building lots of fun projects https://www.youtube.com/@RcLifeOn

(though arguably not undiscovered, currently 870k subs)

Because _one_ person affiliated with DORA behaved badly we should dismiss their research findings? Does that still sound reasonable to you after being spelled out? I really detest this attitude.

Seconding this recommendation. Definitely one of my favorite games the last decade

Hilarious how you suggest someone use a technology that isn't even publicly available, showing how extremely shallow your knowledge is.

The industrial revolution replaced muscle power with machinery. AI is finally at the place where it can replace brain-power for many tasks, and will likely keep improving. I think you are underestimating the significance of this. I don't see too many horses with jobs these days.

Thank you for clarifying. It's seems my definition doesn't correspond to others'. Then do we lack a word for a monolithic application that handles everything and that can only have one instance running?

I don't see whats funny about my statement. Please elaborate on your definition of monoliths vs scalable microservices.

I wouldn't call it a monolith as the number of instances could be scaled up. Mono implies single instance. They just combined multiple microservices into a larger one.

I'd be surprised if this doesn't get taken down as it casts AWS lambda in an unfavorable light (and rightly so). That's the impression I have of Amazon's leadership but maybe I'm wrong.