CobaltC – The Successor to C? • Hacker News Board

Re: CobaltC – The Successor to C?

#11

Post by ethin » Mon, Aug 31, 2026, 3:49 AM UTC

This is so obviously written by ChatGPT from what I can tell. Not even an attempt to copyedit it unless I missed something.

Re: CobaltC – The Successor to C?

#12

Post by strenholme » Mon, Aug 31, 2026, 3:55 AM UTC

jjtheblunt wrote: post #8

ronsor wrote: post #3

Before I read this, what is there about C3 [0] you don't like? [0] https://c3-lang.org

C3 is an embarrassing mess regarding integer types and sizes, missing C99's stdint.h defs, for example.

To clarify: C3 has fixed sized ints. Maybe the parent poster doesn’t like their names, but they are fixed sized, as follows:

  Name    Size    Signed
  bool    1       no
  ichar   8       yes
  char    8       no
  short   16      yes
  ushort  16      no
  int     32      yes
  uint    32      no
  long    64      yes
  ulong   64      no
  int128  128     yes
  uint128 128     no

Source: https://c3-lang.org/language-overview/types/#integer-types

Re: CobaltC – The Successor to C?

#13

Post by thinkafter » Mon, Aug 31, 2026, 3:57 AM UTC

ethin wrote: post #11

This is so obviously written by ChatGPT from what I can tell. Not even an attempt to copyedit it unless I missed something.

I’m not sure about copy but the UI seems designed to look like an AI response which is certainly a choice

Re: CobaltC – The Successor to C?

#14

Post by ternaryoperator » Mon, Aug 31, 2026, 4:04 AM UTC

It's great to have it all spec'd out. However, I think specs like this suffer the same fate as war plans: they get modified quickly as soon as implementation begins. Nonetheless, it's good to have a clear idea of where you're headed. I just wouldn't call it "Final."

Re: CobaltC – The Successor to C?

#15

Post by hyperhello » Mon, Aug 31, 2026, 4:28 AM UTC

ethin wrote: post #11

This is so obviously written by ChatGPT from what I can tell. Not even an attempt to copyedit it unless I missed something.

[flagged]

Re: CobaltC – The Successor to C?

#16

Post by woodruffw » Mon, Aug 31, 2026, 4:33 AM UTC

Another one?

Re: CobaltC – The Successor to C?

#17

Post by katdork » Mon, Aug 31, 2026, 4:39 AM UTC

irishcoffee wrote: post #10

Fordec wrote: post #7

Earlier quoted context omitted.

Who copied off Haskells homework, so here we are.

And cloudflare still somehow shipped a rust binary that crashed half the internet.

and I've had Haskell binaries attempt to use infinite quantities of RAM (looking at an old version of dconf2nix here) and thus crash

Re: CobaltC – The Successor to C?

#18

Post by rurban » Mon, Aug 31, 2026, 4:43 AM UTC

Unsafe identifiers, prone to homoglyph attacks. No TR39 provisions. Worse than rust or Java. https://strawberry9.github.io/the-wrong-memory/Appendix_06.h...

Re: CobaltC – The Successor to C?

#19

Post by SilentLambda » Mon, Aug 31, 2026, 5:14 AM UTC

woodruffw wrote: post #16

Another one?

Yes, but remember is the last appendix to a book, and book provides the context for this appendix. So yes, in that sense, it's just another one attempting to address the memory-safety issues of C. At least this one uses C like syntax and doesn't require C programmers to learn some alien syntax. Of course, this is just a spec, Rust is well and truly live in the environment. The book is more interesting than the spec.

Re: CobaltC – The Successor to C?

#20

Post by Gualdrapo » Mon, Aug 31, 2026, 5:14 AM UTC

woodruffw wrote: post #16

Another one?

Odin's turn to be "the sucessor of C" is due this month