HackerTrans
TopNewTrendsCommentsPastAskShowJobs

NorthTheRock

no profile record

comments

NorthTheRock
·3 เดือนที่ผ่านมา·discuss
> C’mon. Stop wishing for a future that feels convenient. This is not the world in which we live. Everything will change. Let’s help people accept and react to that.Let’s stop with the comfort talking and false hope.

This is honestly how I feel about the opposite, it sure would be convenient for capital holders if everything changed and they no longer need to pay employees. They really, really want this to be true, and are pushing it as hard as they can despite reality.
NorthTheRock
·2 ปีที่แล้ว·discuss
But in a world of subscription based services, it has to ship more than once. And as soon as that's a requirement, all of the above applies, and the LLM model breaks down.
NorthTheRock
·2 ปีที่แล้ว·discuss
> is getting progressively better

Is it still getting better? My understanding is that we're already training them on all of the publicly available code in existence, and we're running in to scaling walls with bigger models.
NorthTheRock
·2 ปีที่แล้ว·discuss
> When you consider LLMs to be building blocks in bigger, more complex systems, their potential increases dramatically.

Do you have any examples of where/how that would work? It has seemed for me like lot of the hype is "they'll be good" with no further explanation.
NorthTheRock
·2 ปีที่แล้ว·discuss
> Talk to people, not studies.

So literally calling for anecdotes over data?
NorthTheRock
·2 ปีที่แล้ว·discuss
> DA refuses to prosecute crime

Have there been any actual documented instances of this? I see it cited a lot, but rarely any specific names of DAs or cases attached to it, and it feels like an easy excuse for police to not even attempt to do their jobs.
NorthTheRock
·2 ปีที่แล้ว·discuss
In the US, there's no evidence that this happens - just a bunch of media narratives and failed lawsuits after the 2020 election that couldn't provide an ounce of proof when push came to shove.
NorthTheRock
·2 ปีที่แล้ว·discuss
I've always seen this as the exact opposite view - from go's concurrency model, every function is "synchronous" so the caller is not given a choice, if they want to run it asynchronously they have to create a new thread, then if they care about the result deal with inter-thread communication.

With async/await, you're explicitly giving control to the caller to decide, you can await this promise now and have the thread treat it as synchronous, you can spawn a new task to run it in the background, or you can join it with other promises where you don't care about order and await for the results of the group.