News for hackers. Stuff that matters.
Re:Some were meant for C [pdf] by steveklabnik on Wednesday June 21, 2023 @04:35PM (#36424036)
I do think you’ve identified a significant rift between those that prefer C and those who do not. I think you’re being downvoted for the value judgement you’re injecting, though.

> gets out of your hair and lets you ge on with programming

This is the divergence, I think. For me, the method in which c “gets out of my hair” means that more burden is placed on me, the developer. Which means I have to work more slowly, cautiously, and remember things that a good type system could have been checking for me. And the lack of features means I spend time working around that lack rather than getting real work done.

I suspect these preferences are irreconcilable.

Re:Some were meant for C [pdf] by quelsolaar on Wednesday June 21, 2023 @04:44PM (#36424150)
> I do think you’ve identified a significant rift between those that prefer C and those who do not.

I agree. I think the article is very right in identifying that C developers look at programming differently. I think that is a good thing. Even as a Die-Hard C programmer, I celebrate that people use other languages and especially that people are developing new languages like Rust, Odin, Zig and so on. I don't think it wrong for someone to reject C, if its not right for them. Do what works for you. I do think that given Cs massive success, people should perhaps be a bit more interested to figure out why, instead of just dismissing it so fast.

Re:Some were meant for C [pdf] by comfypotato on Wednesday June 21, 2023 @06:53PM (#36425821)
Your comments on this thread up to this point sound like a religious fanatic.

I greatly enjoyed reading.

Goes to show why it’s called “The C Religion”.

Re:Some were meant for C [pdf] by quelsolaar on Wednesday June 21, 2023 @07:10PM (#36426001)
I think, most designers of languages want abstractions, convenience, and clevernes. So for people who don't want that we have to cling on to C since there aren't other options ;-)
Re:Some were meant for C [pdf] by rewmie on Thursday June 22, 2023 @01:16AM (#36428236)
> I think, most designers of languages want abstractions, convenience, and clevernes.

You get that in C as well in the form of libraries and frameworks. Today you saw a post in HN on how to do object oriented programming with C. Some time ago people shared C frameworks to enforce memory safety. There are generic data structures libraries for C as well.

I think your jab on how C programmers don't want abstractions, convenience, or cleverness is a weak strawman. It's obviously not it. What I think C programmers value is expressiveness and speed, and avoid bloat and overall inefficiencies, and C detractors don't want to address that because it forces them to face the real world tradeoffs which expose the shortcomings of their personal choices. There's a pervasive fear of missing out on the latest and greatest, and an irrational need to jump onto bandwagons, and C is extreme opposite of it. And yet it still outperforms anything that came after.

Re:Some were meant for C [pdf] by melagonster on Wednesday June 21, 2023 @10:48PM (#36427459)
writing C like doing extreme sport, respect but I don't want to try it soon. thanks all developers of interpreter, because they wrote it with C, so I don't need to write C.
Re:Some were meant for C [pdf] by rramadass on Thursday June 22, 2023 @03:00AM (#36428854)
You have the wrong idea and doing yourself a disservice by not learning C. It is not as difficult as people make it out to be.
Re:Some were meant for C [pdf] by vba616 on Thursday June 22, 2023 @12:27AM (#36428008)
I learned C in the 1980s. At that time, for practical purposes, it seemed it was the same as Pascal, only with less verbose syntax - { } instead of begin/end.

But then I discovered Usenet and the - I don't know exactly how to describe it - the cult of undefined behavior, and the people who care only about standards and not reality.

A basic, straightforward language like what people say C is, is certainly useful. I don't know Rust, and I don't have any plans to learn it.

As I think we all are aware, C originated before computers were standardized on 8 bit bytes, ASCII, Unicode, and 32/64 bit words. So, I mean, no matter how much people say it's appealing because it's simple and reflects the nature of the hardware, it really doesn't.

Is it not true that the Linux kernel is compiled with GNU extensions and not standard C?

Re:Some were meant for C [pdf] by rewmie on Thursday June 22, 2023 @01:05AM (#36428183)
> But then I discovered Usenet and the - I don't know exactly how to describe it - the cult of undefined behavior, and the people who care only about standards and not reality.

I don't understand what you tried to say. The standard specifies how the language actually works, and therefore what developers can reliably do with it. How exactly do you see this as a break from reality?

Re:Some were meant for C [pdf] by vba616 on Thursday June 22, 2023 @01:22AM (#36428268)
If you stopped at that sentence, then the rest of my comment might clarify.

It's hard for me to elaborate further without any idea of your background. How long have you been programming in C? Have you encountered TAOCP and MIX/MMIX? Do you write strictly standards compliant C? Did you use to read or post on comp.lang.c?

For reference, here is a list of things that are/were off topic:

https://benpfaff.org/writings/clc/off-topic.html

Dennis Ritchie posted on clc in 1999 and was told he was off topic. It has passed into history as a "joke".

"DECtapes are highly platform specific, and are not covered by ANSI C, which is the subject of this newsgroup (comp.lang.c). Try a DEC-related newsgroup.

If you want us to comment on your source code, please post it in the body of your email.

What was your C question?"

https://groups.google.com/g/alt.folklore.computers/c/wbzzoyS...

Re:Some were meant for C [pdf] by rewmie on Thursday June 22, 2023 @07:29AM (#36430518)
> background. How long have you been programming in C?

Since the mid 90s.

> Have you encountered TAOCP and MIX/MMIX?

I fail to see the relevance.

> Do you write strictly standards compliant C?

There is no such thing as non-strictly standards compliant C. It's either C, as specified by one of the international standards, or K&R C for those who can't target a standard, or things that are not C.

> Did you use to read or post on comp.lang.c?

Yes.

What was your point?

Re:Some were meant for C [pdf] by vba616 on Friday June 23, 2023 @09:59PM (#36454708)
The relevance of MIX/MMIX is that to me, MIX is a lot like C in its aspirations and failures as time passed it by. Knuth described similar motivations in terms of portability, not wanting to choose a favorite architecture, and so on. But it ended up being an incredibly baroque, opaque, and obscure way to show algorithms, even though he meant it to be more concrete and relevant than pseudocode.

Then MMIX seems to me to sort of concede that sample code should be a little more like real life code, while still being far more difficult to follow than need be.

Some people just love complications for their own sake, like a medieval monk illuminating a manuscript. That's not wrong, but it's not right for everyone.

The issue I have is with people falsifying the reasons that C can be attractive. The IOCCC is the essence of what C is actually about. It is just not anything like an elegant "high level assembler" that reflects machine architecture. Maybe there is an alternative these days that fits the bill better, or maybe not.

>There is no such thing as non-strictly standards compliant C. It's either C, as specified by one of the international standards, or K&R C for those who can't target a standard, or things that are not C.

Well, here we go. First of all, the tone of this statement takes me back to clc. I could almost believe it's a direct quote.

Secondly, I haven't written a great deal of C code in the last 40 years, all told, but I was writing C code before C89 (and you, I infer, were not). It certainly wasn't K&R C, and it couldn't be standard C if that wasn't invented yet, right?

Everything meaningful "written in C", I think, falls into your category of "things that are not C". Like the Linux kernel.

That's just annoying to some people like it was when "kilobytes" were renamed "kibibytes" or "minor planets" were suddenly not "planets".

But shouldn't it bring with it a tiny bit of doubt that there might be something wrong with the ideals of the orthodox? There are many belief systems that have proved impossible for humans to follow, and just because many people are hypocrites doesn't mean that we should define ideals people strive for such that everyone becomes a hypocrite.

If people say undefined behavior allows your program to blow up the world, that is not debatable in isolation, as all definitions are arbitrary. But it is inconsistent with ever using or encouraging anyone else to ever use the language.

>What was your point?

I was pretty cautious. I think I read the FAQ as one was instructed to. I don't know if I ever posted any questions at all. I read it, and the arguments with newbies who over time increasingly seemed like trolls, as entertainment. Same as with the Ayn Rand worshipping Objectivists, the anarchists, or the Holocaust deniers in other groups.

I used to think, no matter how certain people are in their rectitude, can they not see it's leading to endless flamewars where people just wind them up for fun? What do they think the group is for? Do they make the connection that ultimately it is for whatever actually exists in that space? Do they really want what exists there?

Re:Some were meant for C [pdf] by hudon on Wednesday June 21, 2023 @05:04PM (#36424476)
How is the C type system slowing you down? I thought the complaints around C productivity were around memory management and low-level APIs (both of which can be mitigated using libraries: you can “abstract away” these problems and stay in C).
Re:Some were meant for C [pdf] by steveklabnik on Wednesday June 21, 2023 @05:40PM (#36425019)
Like Walter Bright, I would love to have some sort of “span” or “slice” primitive. I would love language level tagged unions rather than writing them out each time. Pattern matching isn’t exactly a type system feature, but relies on it to work, and would make those more useful. The lack of destructors means a lot of manual handling of errors. The lack of generics makes it difficult to write generic data structures without losing type safety. There’s no real const.

There are ways to do all of these things, but they’re more manual, more error prone, and get in the way of doing the actual work you’re trying to do.

Re:Some were meant for C [pdf] by ho_schi on Wednesday June 21, 2023 @06:03PM (#36425299)
That describes the basic feature set of C++ very well.

People complain about C++ that it can do much more. Yea. But there is no need to use template meta-programming, multiple inheritance and other special features. Actually I think programmers shouldn’t use them in productive code.

Recently some projects switched the compiler to ‘g++’ and use the basic subset of C++. Makes sense? Maybe Herb Sutters “C++2” will evolve, main features are safety and simplicity.

I’m fine with both C and C++. They do a good job. Address-Sanitizer is a game changer! But I want more.

Re:Some were meant for C [pdf] by steveklabnik on Wednesday June 21, 2023 @06:13PM (#36425411)
Yeah, kinda:

> I would love to have some sort of “span” or “slice” primitive.

This was recently added!

> I would love language level tagged unions rather than writing them out each time.

There is std::variant, but it’s not as nice as a language provided solution, both to use and the generated code.

> Pattern matching isn’t exactly a type system feature, but relies on it to work, and would make those more useful.

This is not in C++, and my understanding is that the proposals are nowhere near close.

> The lack of destructors means a lot of manual handling of errors.

The huge C++ feature. Yes, a clear win. I think a version of RAII closer to Rust than to C++ would make more sense for C, though.

> The lack of generics makes it difficult to write generic data structures without losing type safety.

Yep, absolutely.

> There’s no real const.

There isn’t in C++ either.

Re:Some were meant for C [pdf] by tialaramex on Wednesday June 21, 2023 @07:43PM (#36426309)
C++ 20 std::span is an example of how little WG21 actually cares about safety, correctness or other principles of software engineering.

The slice type you actually want has nice safety properties. The slice type proposed to WG21 about five years ago as std::span compromises a little bit, knowing they'd object to good engineering here, and it offers an unsafe way to access the slice as well as safe access. The committee voted to strip out safe access and specifically rejected efforts to ensure there was a sane way to use this type.

I assume Jarrad Waterloo's proposal to fix std::span in C++ 26 will get traction because it's now embarrassing for the project but there's no reason we should pretend this was some mere oversight. C++ is less safe than it should be on purpose.

Re:Some were meant for C [pdf] by MereInterest on Wednesday June 21, 2023 @07:56PM (#36426429)
I get similarly frustrated at the implementation of operator-> and operator* in std::optional. In what world would I want to provide accessors with no more safety than a raw pointer?

Edit: I was looking it up just to make sure I remembered it correctly, and there’s been a recent change that makes it worse. The operator-> and operator* on std::optional are now marked noexcept, so implementations are forbidden from making the accessors safe.

https://cplusplus.github.io/LWG/issue2762

Re:Some were meant for C [pdf] by steveklabnik on Wednesday June 21, 2023 @07:53PM (#36426402)
That's what I've heard, but since I'm not that in the weeds with that whole process, I didn't want to comment on it at that level.

It's struck me as being similar to operator* on Optional. I get why they did it. It makes sense. It's also unfortunate. I'm glad I'm not on that committee.

Re:Some were meant for C [pdf] by Hirrolot on Wednesday June 21, 2023 @05:37PM (#36424991)
The need to express polymorphism manually in C, the need to remember to check errors returned by functions (instead of the monadic style of computation), the need to define closure's environment structures (those that are passed via something like `void *arg`), etc.

All these things are pretty tedious. And all these things are what other languages are doing under the hood. The difference is that C gives you a choice of _how_ to do (more) things; other languages do not.

Re:Some were meant for C [pdf] by JohnFen on Thursday June 22, 2023 @10:49AM (#36432998)
> The need to express polymorphism manually in C

Or, don't do polymorphism in C. It's not a mandatory technique. I love C, but I'd argue that if you're doing advanced OOP, you should use a more appropriate language.

Re:Some were meant for C [pdf] by pornel on Wednesday June 21, 2023 @06:30PM (#36425583)
Inability to specify non-nullable pointers, or truly immutable data, or ownership, or thread-safety of objects on the type system level means I have to remember these unwritten invariants in every case, and/or code defensively.

Libraries can't specify these things in a compiler-enforced way either, so they remain "RTFM" problems for programmers to deal with manually.

Re:Some were meant for C [pdf] by retrac on Wednesday June 21, 2023 @06:44PM (#36425723)
Sum types. In C they can be constructed out of unions and structs with lots of checks (and possibility for error) but it's painful.

There's really no excuse for C not having them, other than C being designed before algebraic types became mainstream. They make certain programming errors impossible, particularly with null values and misusing a union with the wrong type. It is possible to compile them as a zero-cost abstraction, and essentially all recent languages aimed at the same domain as C (Rust, D, Go, Zig, Hare, etc.) include them.

Re:Some were meant for C [pdf] by anacrolix on Wednesday June 21, 2023 @06:55PM (#36425841)
Go goes NOT have sum types. I'm not sure Zig technically does, but is close enough.
Re:Some were meant for C [pdf] by antonvs on Wednesday June 21, 2023 @08:39PM (#36426706)
> the C type system

The what now?

C has a type system in the same sort of way that the United States has socialism.

Re:Some were meant for C [pdf] by tialaramex on Thursday June 22, 2023 @06:31AM (#36430114)
A strong type system, weakly checked.

I mean, the type system it isn't checking still isn't as strong or powerful as I'd like, but it is there. Unlike your CPU which doesn't care, C agrees that in principle an integer, a pointer and a floating point value are in fact different kinds of thing.

I think Option<!> is excellent, C thinks I should just write a comment in the program instead, these are big differences but they aren't so fundamental as the difference between US corporate welfare and socialism.

Re:Some were meant for C [pdf] by antonvs on Friday June 23, 2023 @05:20PM (#36452294)
> C agrees that in principle an integer, a pointer and a floating point value are in fact different kinds of thing.

Sure, but that's kiddie-pool, 1970s-level stuff compared to modern type systems.

No business in their right minds is saying, in 2023, let's develop a new system in C. If they are, it's because they have people stuck decades in the past who are arguing for it.

(Edit: or, of course, they need to integrate with a C system, the number of which "is too damn high".

Re:Some were meant for C [pdf] by JohnFen on Wednesday June 21, 2023 @07:04PM (#36425935)
> more burden is placed on me, the developer. Which means I have to work more slowly, cautiously, and remember things that a good type system could have been checking for me.

Very interesting. You cite these as drawbacks, and I consider them all to be advantages.

Which just proves the point!

> I suspect these preferences are irreconcilable.

I think you're right. Fortunately, they are only preferences and so aren't incredibly meaningful. I prefer C, but most of my professional work isn't in C. And I don't always choose C for any given project.

Every language has its own advantages and disadvantages, so I select the language for a project keeping in mind which one mesh best with the project at hand.

Re:Some were meant for C [pdf] by antonvs on Wednesday June 21, 2023 @08:37PM (#36426690)
> You cite these as drawbacks, and I consider them all to be advantages.

Why would they be advantages? Working more slowly and cautiously might be advantageous in some cases, but being forced to do so because otherwise your program might die a horrible death seems hard to justify as advantageous. Unless you're treating it as a sort of extreme sport, like rock climbing without a rope.

Re:Some were meant for C [pdf] by tourmalinetaco on Thursday June 22, 2023 @01:33AM (#36428337)
Because working slowly and rewriting code typically leads to better code. By taking it slowly you grow more familiar with what you want, it gives you more time to think, and its generally more enjoyable.

This culture of “fast coding” is a major reason software ends up so flawed. People are so enamored with quantity they completely forget quality along the way. And that means everyone suffers.

Re:Some were meant for C [pdf] by antonvs on Thursday June 22, 2023 @02:37AM (#36428695)
You didn’t actually address the point I raised about why C is hard to justify for that reason.

Besides, a strong type system also forces you to think about the design of your code, and demonstrably leads to more reliable results, on an industry-wide basis.

Re:Some were meant for C [pdf] by JohnFen on Thursday June 22, 2023 @10:43AM (#36432905)
> a strong type system also forces you to think about the design of your code

True. And so does using a language like C.

Re:Some were meant for C [pdf] by antonvs on Thursday June 22, 2023 @11:46AM (#36433972)
Except the forcing function in C occurs because if you make a mistake, you can have serious problems at runtime. With a strong type system, if you make a mistake, your program won't compile. It's a big difference, and it's hard to justify the C approach for reliable systems development in a modern context. No-one in this thread even seems to be trying.

If you want to use it for hobby projects because you enjoy it, knock yourself out. But advocating its use for anything important hasn't been viable for decades except for legacy reasons.

Re:Some were meant for C [pdf] by JohnFen on Thursday June 22, 2023 @12:39PM (#36434846)
> It's a big difference

It is! And there is absolutely a role for strongly typed languages.

> But advocating its use for anything important hasn't been viable for decades except for legacy reasons.

We entirely disagree here.

The big benefit of more stringent languages is that they require less effort on the part of the programmer to ensure safety and correctness. This is of great value -- perhaps even indispensable -- in certain contexts. For instance, if the programming team is large, or if the company wants to hire less experienced developers, or if the company wants to keep up a very high velocity.

But those are economic arguments. It's different than asserting that a given language is simple too dangerous to use under any circumstance. I think that assertion is entirely unsupportable.

Re:Some were meant for C [pdf] by jjgreen on Thursday June 22, 2023 @04:22AM (#36429381)
This is so true, I've pointedly never learnt to touch type since I don't want to be able to write faster than I can think.
Re:Some were meant for C [pdf] by JohnFen on Thursday June 22, 2023 @10:42AM (#36432880)
> being forced to do so because otherwise your program might die a horrible death seems hard to justify as advantageous.

The advantage is that it forces me to do the task properly, and prevents me from getting lazy and having important skills and habits atrophy.

Also, it doesn't feel like an extreme sport or anything. It's just programming, like in any other language. Not any more or less stressful.

Re:Some were meant for C [pdf] by antonvs on Thursday June 22, 2023 @11:52AM (#36434075)
It may not be stressful for you, but it ends up being stressful for anyone who has to rely on the resulting programs. When they have a security issue due to a buffer overflow, or a crash due to a null pointer error, etc.

The "just trust me bro" school of programming is not suitable for delivering serious systems.

Re:Some were meant for C [pdf] by JohnFen on Thursday June 22, 2023 @12:32PM (#36434695)
> it ends up being stressful for anyone who has to rely on the resulting programs.

Only if you're writing bad programs. The idea that it's impossible to write good, solid programs in any given language is ridiculous.

> The "just trust me bro" school of programming is not suitable for delivering serious systems.

No one is advocating that. Your choice of language doesn't change the need for processes that ensure quality.

Re:Some were meant for C [pdf] by antonvs on Friday June 23, 2023 @05:21PM (#36452315)
> The idea that it's impossible to write good, solid programs in any given language is ridiculous.

The data disagrees. There's plenty of evidence that the severity of bugs and the number and severity of security bugs is far higher in languages like C or C++ than in memory-safe languages.

> Only if you're writing bad programs.

This is precisely the "just trust me bro" mentality I was referring to.

"I write good programs, I swear!"

But you're human, and you really don't. You make mistakes. Empirically, you make roughly as many mistakes per line as programmers in other languages, but the consequences of those mistakes are worse.

You can argue with me all you want, but you're essentially arguing with reality. C has survived for legacy reasons, but almost everyone is desperate for a better, more robust alternative.

Just so you know where I'm coming from - I learned C in the early 80s, not long after learning Fortran. I later started using C++ because it seemed to offer some benefits. But now - more than forty years later, when there are so many better alternatives for any given problem except one which requires legacy integration - it's astonishing to me that people are still staunchly defending C.

It reminds me of what Max Planck said about physics:

> “A new scientific truth does not triumph by convincing its opponents and making them see the light, but rather because its opponents die, and a new generation grows up that is familiar with it.”

Re:Some were meant for C [pdf] by fsckboy on Friday June 23, 2023 @04:00AM (#36444080)
if you can't write code without buffer overflows, how are you going to write code that is accurate on any of a number of other dimensions? You need to do things the right number of times, if you don't, you get the wrong answer. I agree that security vulns are bad bad, but correctness is also a good thing, and getting things right is not a "nice to have" skill.
Re:Some were meant for C [pdf] by assimpleaspossi on Wednesday June 21, 2023 @07:23PM (#36426131)
>I have to work more slowly, cautiously, and remember things

I think that should be a good thing.

Re:Some were meant for C [pdf] by steveklabnik on Wednesday June 21, 2023 @07:50PM (#36426380)
Humans build tools to help us achieve things. No good comes from making me manually remember things a machine could easily check for me.

I doubt you crafted the HTTP call to post this comment by hand, even if you could. I could. I don't want to. That's why tools exist.

Re:Some were meant for C [pdf] by MereInterest on Wednesday June 21, 2023 @07:52PM (#36426401)
It depends on what I’m being slow and cautious about. Imagine a programming language that is identical to C, but every prime-numbered line is ignored. In such a language, I would be cautious to add or remove lines, slowly and cautiously remembering which line numbers to avoid. It wouldn’t provide any benefit, as I’d be paying attention to line numbers instead of paying attention to null checks, or integer overflow.

In the same way, C imposes an extra burden compared to other languages. If I declare a std::vector in C++, or a Vec in Rust, it will be deallocated when the scope is exited. But in C, every malloc() requires a call to free(). It requires extra effort for no benefit.

Re:Some were meant for C [pdf] by steveklabnik on Wednesday June 21, 2023 @07:54PM (#36426419)
This is a far better way of putting what I tried to say, thank you.
Re:Some were meant for C [pdf] by andrewmcwatters on Wednesday June 21, 2023 @08:21PM (#36426588)
There is absolutely a benefit, but it doesn't sound like one to you: it explicitly requires you to know that you're actually doing something with memory, which rapidly deteriorates as a concept for developers once they no longer have to be cognizant of the fact that they are indeed actually using it.

I prefer a world where people actually think about the resources they're using.

Re:Some were meant for C [pdf] by jcranmer on Wednesday June 21, 2023 @08:59PM (#36426829)
But does that benefit actually exist? The approach of languages like C++ or Rust isn't to hide memory in the way a GC'd environment like Java or Python does (although C++ does have historical baggage with its copy constructors)--this feels to me like it's the same problem I mentioned in my first comment, that you're focused on contrasting C with managed languages and ignoring the space of non-managed languages. And, anecdotally, from what I've seen perusing various Rust crates, my sense is that too many Rust programmers actually spend too much time worrying about their memory usage, designing extensive and cumbersome zero-copy interfaces when, no really, you should just copy that 5-byte string to your own storage.

I don't see how having to remember to always add in calls to free, with the cost of using more memory if you forget to do so, is really supposed to help you minimize your memory usage. That's the main difference we're talking about here...

Re:Some were meant for C [pdf] by torstenvl on Wednesday June 21, 2023 @10:32PM (#36427363)
Remembering to use free() is a lot easier than remembering the inner workings of each and every destructor of each and every object you use.

Will destroying this window free the memory for this font instance? Will destroying this DOCX processing object close the file? Who knows?

But when the rule is just to clean up after yourself, it's a lot easier to remember.

Re:Some were meant for C [pdf] by scoutt on Thursday June 22, 2023 @03:04AM (#36428889)
In C, declaration != heap allocation. And this is a very important detail because implementing something like "deallocation when the scope is exited" adds complexity to the language; more things and more rules you now have to remember.
Re:Some were meant for C [pdf] by JohnFen on Thursday June 22, 2023 @10:55AM (#36433088)
> It requires extra effort for no benefit.

There is a benefit, although it may not be useful for your use case. In that situation, I agree with you -- use a different language.

I find it interesting that so many comments here criticizing C (and a couple of other languages) seem to be taking the stance that "if it isn't good for every kind of task, it isn't good for any kind of task".

Every language both rocks and sucks, depending on what you're doing with it. There is no One Ring to Rule Them All. That's why we have so many different languages -- we should be choosing the one that fits the job at hand.

This is why I think holy wars over languages are always ridiculous. Any given language may be a terrible choice for a particular job. That's not a fault of the language, it's just a sign that language is the wrong tool. Use a different tool.

Re:Some were meant for C [pdf] by taylorius on Thursday June 22, 2023 @03:56AM (#36429205)
I think it's work either way. You either spend brain-time on memorizing the intricacies of a lot of prebuilt tools, and how / when one might apply them (modern c++) - or you dispense with the many tools, and spend your brain time on memorizing relatively few, but with more effort and detail required on their application. (C). I prefer the latter, but as you say - it's probably linked to personality to some extent, and quite "baked in".
Re:Some were meant for C [pdf] by JohnFen on Thursday June 22, 2023 @10:47AM (#36432961)
> You either spend brain-time on memorizing the intricacies of a lot of prebuilt tools

I suppose another piece of evidence about how this is a personality thing is that I hate having to learn specialty tools. They're limiting in that typically, they only exist on certain platforms, and they often specific to certain languages, so knowing those tools often doesn't help me generally. (Libraries and the equivalent count as tools here, too.)

So I make it a point to not grow a dependency on them even when I use them. I very much prefer to focus on skills that I can leverage widely.

Re:Some were meant for C [pdf] by taylorius on Sunday June 25, 2023 @04:43PM (#36472393)
Sounds a sensible policy to me!