916 karma · joined February 22, 2016
When the first bugs come up you see that the velocity was not god sent and you end up hiring one of the many "LLM code fixer" companies that are poping up like mushrooms.
what you say is nice in theory but you already have the Microsoft backed Edge and Apple backed Safari that are not hamppered by the "need to find a support model" and "not be a loss leader"
And I am not looking forward again to a world where Microsoft disctates web development because for all privacy problems peaople have or think to have with Google, Microsoft ha proven that does way worse and doesn't even care for the image.
All in All Chrome being a loss leader backed by Google has been a good thing for all involved. Developers, Users and 3-rd parties. without it you woudn't have all those 3rd party chrome based browsers.
how you comunicate it does not alter the nature of the problem.
What's more, whatever you like to call the transoforming of information into thinked information by definition can not be a (mathematical) function, because it would require all people to process the same information in the same way and this is plainly false
This is a fallacy. Just because you need to serialize a concept to communicate it doesnt mean the concept itself is computable. This is established and well proven:
https://en.wikipedia.org/wiki/List_of_undecidable_problems
The fact that we can come up with this kind of uncumputable problems is a big plus in supprt of Penrose's Idea that consciousnes is not computable and goes way beyond compatability.
In general we have thousands of optimisations problems that are hard to solve but immediate to verify.
> Of course, as happened after we announced the first beyond-classical computation in 2019, we expect classical computers to keep improving on this benchmark
As IBM showed their estimate of classical computer time is taken out of their a**es.
Some people didn't like the "try" keyword it reminded them too much of exceptions, some people didn't like that they couldnt see a return inline (which was the purpose of the proposal in the first place).
it's not that there are no solutions. the main problem is the go team's insistence to have "one true way" (tm) of doing something and unfortunately this gap between people who want to see every return inline and people who want to see the clean solution separate from the error handling is not something that can be bridged by technical means. the only solution is to implement both ways and lets see which one wins.
on this point go's error handling is a massive fail. Notice that I'm not saying explicit error handling is bad. I'm saying the insistence that error handling needs to be implemented inline interleaved with the happy path is the problem. You can have explicit error handling in dedicated error handling sections
Saying that we wouldn't be here to ask the question is not an answer to anything because we are here and we need to understand how and why.
while it can be played as stateless, remembering previous moves gives you insight into potential strategy that is being build.
is it "learning" in a certain sense? sure, the same way like all indoctrinations are sold as "teaching". the model "learned" to be rapresentative but forgot what 1940 nazi soldier was like...
and fine tuning is not a scalable approach because it has human feeback in the loop. could they fix this error with more fine tuning? yes and they tried abut then the users simply asked "give me a picture a viking warriors" and the problems was again there, you can't fine-tune everything even if we assume the purpose is always noble.
notice that LLMs "context" chat is not learning, it's a temporary effect that gets lost as soon as the chat closes.