Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror

Comment Re:Does this mean it'll stop sucking? (Score 1) 23

I found GP2.5 to be great at academic-style research and writing; it was absolutely awful at writing code. So; I would tell it to plan some thing for me and write it in a way that could be used by another agent (Claude Code) to build the code to do the thing. In this way, it has been great! I haven't yet attempted it with 3.

That said, I found GP3.0's page to be hilarious:

It demonstrates PhD-level reasoning with top scores on Humanityâ(TM)s Last Exam (37.5% without the usage of any tools) and GPQA Diamond (91.9%). It also sets a new standard for frontier models in mathematics, achieving a new state-of-the-art of 23.4% on MathArena Apex.

It then proceeds to show, lower down on the page, an example of what it can do, by showing off 'Our Family Recipes". If there's anything that touts PhD-level reasoning and writing, it's a recipe book.

Comment Re: It a guidebook... (Score 1) 238

my son's teacher told us that it helped with developing fine motor control, particularly in children that had below average motor control.

For one, is this based on research or speculation? Second there are different kinds of motor control. Following an existing pattern or shape is one type, while cursive is another because one tends to develop patterns based on personal preferences.

Comment Re:More than meets the eye (Score 1) 238

In 5th grade my teacher wanted to wring my neck because I was growing quite skillful in drawing and art, yet my cursive writing was worse than a drunk doctor's. I didn't see them as connected, but it was in the teacher's mind. I had a semi-impressionistic art style such that stroke precision mattered less.

Comment Re:Async bloat (Score 1) 91

I guess I'm not working on "typical CRUD apps" then?

Based on your description, no, you are not, other than maybe "data stores". Sounds like systems programming. And it's rare to need such for app-level database access (unless you did something wrong or bad).

other than async and await keywords here and there.

It tends to force the need to parts that have nothing to do with asynchronous programming other than being referenced by parts that do. It pollutes and spreads like prions in a brain.

Comment Re:C/C++ code covers more complex legacy code (Score 1) 33

Rust [...] makes it harder for you to work around the compiler when it comes to memory.

... which, to be clear, is a good thing. Working around the compiler is dangerous and a code smell, so it shouldn't be something that is easy to do. It usually indicates that either the compiler's capabilities aren't sufficient to meet your needs (in which case, a better solution would be either a better compiler, or to re-evaluate the wisdom of your approach), or that you are doing something the wrong way and should find a way to do it that works with the compiler, rather than around it, so that you get the benefits of the compiler's co-operation.

Slashdot Top Deals

The first rule of intelligent tinkering is to save all the parts. -- Paul Erlich

Working...