Live data from Hacker News

OpenAI declares 'code red' as Google catches up in AI race

theverge.com

491–500 of 960 posts

Re: OpenAI declares 'code red' as Google catches up in AI race

#491
post #449

Earlier quoted context omitted.

What is a pre-training run?

Pre-training is just training, it got the name because most models have a post-training stage so to differentiate people call it pre-training. Pre-training: You train on a vast amount of data, as varied and high quality as possible, this will determine the distribution the model can operate with, so LLMs are usually trained on a curated dataset of the whole internet, the output of the pre-training is usually called t…

Want to also add that the model doesn’t know how to respond in a user-> assistant style conversation after it’s pretraining, and it’s a pure text predictor (look at the open source base models)

There’s also what is being called mid-training where the model is trained on high(er) quality traces and acts as a bridge between pre and post training

Re: OpenAI declares 'code red' as Google catches up in AI race

#492
post #415

Earlier quoted context omitted.

You think a company the size of OAI should have a single priority? That makes no sense, that’s putting all their eggs on one basket.

All their services depend on their models. Their main priority should be that. If they're too thin, it gets affected. What can openai do that, even if their models lag behind, will let them keep their competitive advantage?

> What can openai do that, even if their models lag behind, will let them keep their competitive advantage?

Regulatory capture. It's worth noting that an enormous amount of time and energy has already been allocated in this exact direction.

Re: OpenAI declares 'code red' as Google catches up in AI race

#493

IMHO Gemini surpassed ChatGPT by quite a bit - I switched. Gemini is faster, the thinking mode gives me reliably better answers and it has a more "business like" conversation attitude which is refreshing in comparison to the over-the-top informal ChatGPT default.

Ironically, the thing that annoys me most about Gemini is the Discord-esque loading messages in the CLI. Twee is one thing: mixing twee with serious hints is worse.

You can turn that off in /settings

Re: OpenAI declares 'code red' as Google catches up in AI race

#495

OpenAI is basically just Netscape at this point. An innovative product with no means of significant revenue generation. One one side it's up against large competitors with an already established user base and product line that can simply bundle their AI offerings into those products. Google will do just what Microsoft did with Internet Explorer and bundle Gemini in for 'Free' with their already other profitable produ…

> Google will do just what Microsoft did with Internet Explorer and bundle Gemini in for 'Free' with their already other profitable products and established ad-funded revenue streams. Just some numbers to show what OpenAI is against: GMail users: nearing 2 billion Youtube MAU: 2.5 billion active Android devices: 4 billion (!) Market cap: 3.8 trillion (at a P/E of 31) So on one side you've got this behemoth with, comp…

You just made it clear who needs to acquire openai.. it's going to be Apple! (Jonny Ive already there).

And great points on the Google history.. let's not forget they wrote the original Transformers paper after all

Re: OpenAI declares 'code red' as Google catches up in AI race

#496
post #461

Earlier quoted context omitted.

By learning to parallelize my work. This also solved my problem with slow Xcode builds.

Well you can’t edit files while Xcode is building or the compiler will throw up, so I‘m wondering what you mean here. You can’t even run swift test in 2 agents at the same time, because swift serializes access for some reason. Whenever I have more than 1 agent run Swift tests in a loop to fix things, and another one to build something, the latter will disturb the former and I need to cancel. And then there’s a lot of…

Yes these are horrible pain points. I can only hope Apple improves this stuff if it's true that they're adding MCP support throughout the OS which should require better multi-agent handling

You can use worktrees to have multiple copies building or testing at once

I'm a solo dev so I rarely use some git features like rebase. I work out of trunk only without branches (if I need a branch, I use a feature flag). So I can't help with that

What I did is build an Xcode MCP server that controls Xcode via AppleScript and the simulator via accessibility & idb. For running, it gives locks to the agent that the agent releases once it's done via another command (or by pattern matching on logs output or scripting via JS criteria for ending the lock "atomically" without requiring a follow-up command, for more typical use). For testing, it serializes the requests into a queue and blocks the MCP response.

This works well for me because I care more about autonomous parallelization than I do eliminating waiting states, as long as I myself am not ever waiting. (This is all very interesting to me as a former DevOps/Continuous Deployment specialist - dramatically different practices around optimizing delivery these days...)

Once I get this tool working better I will productize it. It runs fully inside the macOS sandbox so I will deploy it to the Mac App Store and have an iOS companion for monitoring & managing it that syncs via iCloud and TailScale (no server on my end, more privacy friendly). If this sounds useful to you please let me know!

In addition to this, I also just work on ~3 projects at the same time and rotate through them by having about 20 iTerm2 tabs open where I use the titles of each tab (cmd-i to update) as the task title for my sake.

I've also started building more with SwiftWASM (with SQLite WASM, and I am working on porting SQLiteData to WASM too so I can have a unified data layer that has iCloud sync on Apple platforms) and web deployment for some of my apps features so that I can iterate more quickly and reuse the work in the apps.

Re: OpenAI declares 'code red' as Google catches up in AI race

#497
post #489

Earlier quoted context omitted.

GPT4.5 was allegedly such a pre-train. It just didn’t perform good enough to announce and product it as such.

it wasn't economical to deploy but i expect it wasn't wasted, expect the openai team to pick that back up at some point

The scoop Dylan Patel got was that part way through the gpt4.5 pretraining run the results were very very good, but it leveled off and they ended up with a huge base model that really wasn't any better on their evals.

Re: OpenAI declares 'code red' as Google catches up in AI race

#498

OpenAI is basically just Netscape at this point. An innovative product with no means of significant revenue generation. One one side it's up against large competitors with an already established user base and product line that can simply bundle their AI offerings into those products. Google will do just what Microsoft did with Internet Explorer and bundle Gemini in for 'Free' with their already other profitable produ…

Gemini can't be bundled for free unless they figure out how to make gemini flash 3.0 significantly cheaper to inference than 2.5

Re: OpenAI declares 'code red' as Google catches up in AI race

#499

Last week there we had a customer request that landed in our support on a feature that I partially wrote and wrote a pile of public documentation on. Support engineer ran customer query through Claude (trained on our public and internal docs) and it very, very confidently made a bunch of stuff up in the response. It was quite plausible sounding and it would have been great if it worked that way, but it didn't. While…

I don't know man.

My code runs in 0.11s

Gemini's code runs in 0.5s.

Boss wants an explanation. ¯\_(ツ)_/¯

Re: OpenAI declares 'code red' as Google catches up in AI race

#500

Last week there we had a customer request that landed in our support on a feature that I partially wrote and wrote a pile of public documentation on. Support engineer ran customer query through Claude (trained on our public and internal docs) and it very, very confidently made a bunch of stuff up in the response. It was quite plausible sounding and it would have been great if it worked that way, but it didn't. While…

Yeah, LLMs are not really good about things that can't be done. At some point you'll be better off with implementing features they hallucinated. Some people with public APIs already took this approach.

They are trained with 100% true facts and sucessfull paths.

We humans grec our analysis/reasoning skills towards the 99.9999% failed attempts of everything we did, uncessfull trials and errors, wastefull times and frustrations.

So we know that behind a truth, there’s a bigger world of fantasy.

For LLM, everything is just a fantasy. Everything is as much true as it’s opposite. It will need a lot more than the truth to build intelligence, it will require controled malice and deceptions

Post reply on HN