I don't want to attack the OP specifically (please don't go after them), and I won't argue directly with the C++ part, but C is a terrible C. Later on the OP bemoans fragmentation, but Go is a way better C than C ever was, and Rust is a way better C++.https://twitter.com/landley/status/983060536714780672 …
-
Show this thread
-
Replying to @UINT_MIN
I really don’t think Go brings anything to the table, FWIW.
4 replies 0 retweets 4 likes -
Replying to @stephentyrone @UINT_MIN
Things I actually want from a “better C”: - support for manipulating alignment in the language. - idiomatic bitcast. - vectors in the language. - machine model with twos-comp, CHAR_BIT=8, IEEE 754, flat memory. - restrict-by-default. ...
2 replies 0 retweets 10 likes -
Replying to @stephentyrone @UINT_MIN
I think adding a conservative, sensible compilation model (flat modules, acyclic deps, visibility control), a typesafe fat void* you can punch in and out of, fat bounded pointers / arrays, and ARC (with weak pointers) would be a good stopping point too.
3 replies 0 retweets 8 likes -
(But again, I think it's worth noting that a lot of the nice things one might want from such a Demi-Go is actually just ObjC. It reads funny, but it's not a bad language!)
2 replies 2 retweets 6 likes -
Pervasive atomic reference counting and hash table based method dispatch is such a bummer though.
4 replies 0 retweets 0 likes -
C calls are part of Obj-C. Use them as needed.
2 replies 1 retweet 1 like
I agree. I just think we could do better if designing from scratch.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.