VonReposti

Maybe you should heed your own advice. If you're an ameteur, dont argue with experts. The experts are only correcting you so they can help you. They need to understand what you want below the garbled mess of tech words, otherwise you'll just get random advice that won't work for you. You don't go to the mechanic either and say "I need an asphalt on my car." That is what you're saying right now because you spend 5 seconds somewhere seeing the word "asphalt" when reading the docs about a wheel, completely ignoring everything around that word that said "the wheel is the part of the car touching the asphalt"

If you want advice, don't sound like a self-righteous bastard when it is offered or people are trying to understand what you mean.

• PHP: Programming language, not a file system
• Laravel: A web framework built on PHP, not a file system
• ASP.NET: A web framework built on .NET, not a file system.
• NodeJS: A JavaScript runtime, not a file system

Node:FS is a module for NodeJS which is the first time you have mentioned something that interacts with file systems. It is NOT a file system, but a way to work with a file system. All these programming languages and web frameworks you're mentioning has a way to interact with file systems. You shouldn't choose your tech stack based on this, you should choose it on all it's other properties where they actually differ.

With your less-than-rudimentary understanding of IT and programming I'd suggest you avoid looking like an idiot by arguing with experts and just accept the free help and corrections that are offered. If you keep being an asshole when people try to understand what you mean because your explanation is all over the place, no one will offer their time, especially not for free.

Then you just add a bit on the top.

There is a significant overlap between developers and gamers.

Completely agree, I forgot to mention that part. I am testing a few models ranging from 18b to 26b on my 7900xt. It is far from "make this complete system", but it can handle some smaller tasks. I think that will be the end goal anyway since cloud models fail a lot at maintainability, security, and other higher levels of thought that goes into coding. They can make a convincing prototype but I wouldn't hook it up to production.

Local models are already functioning well as a force multiplier. It can help explain logic, do minor refactoring, debugging etc. but with a bit of latency. I do think this is where we're headed since the frontier models required for generating a full prototype can't make production quality code and it is prohibitively expensive to do so. As far as I've heard, they're generally running spending ten times as much as they earn per token.

I have managed to lose track of time while reading about how we track time.

Already is, take a look at devstral, qwen3.6, deepseek coder. All can be run on a hugh end GPU and if you're a developer you likely have one.

I think it will be much less pronounced. The negative effects of plastic in the body are relatively unknown, but IMO I think it will mostly pose as neurodevelopmental-like symptoms which won't be able to compare with either lead or asbestos.

And the environmental consequences? The majority just doesn't worry about that.

It definitely won't be as bad as asbestos where inhaling just a single fiber can cause cancer. Lead, maybe, but lead is still widely used. Just not in normal fuel. We still use it in some aviation fuel though.

I speak gibberish.

It is a framework that allows different AI programs to coordinate their tasks, provide sources for their conclusions, and verify each other's work without relying on a single central server. It should help avoid drift when solving complex problems.

Is there a difference?

That's just straight out of Idiocracy.

You maniac! Now you'll be bombarded with detective ads from Tate galleries!