Forgot your password?
typodupeerror

Comment Re:Fun (Score 1) 101

I have fun programming in Rust... I like building type systems that prevent errors and automate drudgery. Both C++ and Rust let me do that, C does not...you spend a fair amount of time thinking about low-level details of what the compiler is generating. That's true, and I like thinking about memory layouts, cache lines, what the optimizer is going to do

You very convincingly make it sound so fun.

My point is that if that low-level stuff is what makes C fun to you, then Rust and C++ will be fun, too... but without all of the drudgery and error-prone crap C makes you do.

If that's not what makes C fun to you, then what is? It's certainly not being able to accomplish a lot quickly; higher-level languages are much better for that.

Comment Re:AI (Score 1) 101

If all the "problems" are stupid little things then why not just have AI clean it up? Insist that developers use AI defensively rather than tying their hands with a language that limits them.

I have to push back against your assumption that Rust is a language that limits developers. It absolutely does not. As for the AI bit... I use AI to write code all day. It's great, but it makes the same sort of mistakes humans do. I find Rust is a great language for AI to write (under appropriate supervision).

Comment Re:Fun (Score 1) 101

If you have fun programming in Rust, you will have fun programming in C.

I have fun programming in Rust. I don't like programming in C. I do like programming in C++. I like building type systems that prevent errors and automate drudgery. Both C++ and Rust let me do that, C does not.

I think the point of your "you will have fun programming in C" is that in both languages (and C++) you spend a fair amount of time thinking about low-level details of what the compiler is generating. That's true, and I like thinking about memory layouts, cache lines, what the optimizer is going to do, etc. But I don't like all of the tedium C forces on me.

On balance, I prefer Rust over every other language I've used.

Comment Re:Honesty (Score 1) 102

I have a repo in a sandbox with no remote. Claude is quite good at pushing commits to this repo during its own milestones during development, and it will use it to hunt down bugs when tests fail after a commit, stepping back to a commit before this session's work to see if this is a new bug , or a new way to expose an existing bug. If it sees that it is a new way to exercise an existing bug, it will binary search its way through the commits until it narrows down what changed, and then looks at how to fix it.

My overall strategy is very different. I don't think Claude's code is remotely good enough yet, so I don't trust it to go off and do "development" semi-unsupervised. I direct and review everything it writes, and I control the scope and content of every commit. To be a little more precise, Claude's code is generally fine (if a bit over-commented), but Claude rarely produces code structure that is clear, clean and correctly-mapped to the problem domain, to my (very picky) eyes. So I never just turn it loose on a large, multi-commit development task.

Comment Re:Honesty (Score 1) 102

The fact that LLMs are tripping over themselves trying to be "Honest"

I think this is the result of their trainers trying to reduce hallucination. And hallucination *has* been reduced, so it's probably been largely successful, but it has produced this era of versions that are concerned about honesty, that claims of honesty or apologies for lack or honesty, are pervasive in their output.

But this is basic, basic, basic stuff. It's been committing things to git ever since it was built, and yet, it keeps tripping over itself.

My iron rule is that Claude is not allowed to modify git state, not even to stage or unstage, and definitely not to commit. As long as that rule is followed, any mistakes can be cleaned up easily.

Submission + - A Visual Catalog of Retro Macintosh Software (the icon-ic collection!)

marciot writes: A picture might be worth a thousand words, but scrolling through 75,052 icons is a fun and nostalgic way to explore retro apps! The Visual Catalog of Retro Macintosh Software showcases an (almost) endless wall of icons culled from Macintosh CD-ROMs from the 80s and 90s, from the days before megapixels, when 32x32 pixels were enough for everybody!

Comment Re:Stick driving requires some discipline (Score 1) 238

Paying attention to stick shifts is something done by people who only very rarely drive them. For people who drive stick shifts daily they don't think about them at all, it's just a natural reaction.

And even people who don't drive stick regularly (but know how) quickly stop having to pay attention. I haven't owned a stick shift since the mid 90's, but I often get them when renting cars overseas. It takes a day or two of paying attention, and then it just becomes automatic and effortless.

there was no clutch. I just kicked the footwell for no reason.

BTDT when coming home from a trip where I'd been driving a manual for a couple of weeks.

Comment Re:60%? (Score 1) 238

Just about every motorcycle rider has intimate knowledge of manual shifting. If they are included, 60 percent could be about right.

About 3% of registered road vehicles are motorcycles. When you include dirt bikes the number of riders is higher, but it's still very low compared to the number of automobile drivers. I don't think motorcycle riders are likely to shift the overall numbers very much.

Comment Re:Can I pay him not to post? (Score 1) 213

I wish it were that simple.

It is.

The problem is that you, the brave and the free of today are like the putin subjects - whining all the time that 'it ain't my job to watch over democracy' - so your politics gets more and more corrupted. And you get fucked.

Deservedly.

Reading comprehension is not your strong suit, I see.

Slashdot Top Deals

"Yes, and I feel bad about rendering their useless carci into dogfood..." -- Badger comics

Working...