[deleted]
Learning C3
21–30 of 163 posts
Re: Learning C3
#22Has anyone tried both C3 and Hare[1]. How do they fare? There seems to be quite the overlap between the two. [1] https://harelang.org/
There's also Zig in the C-alternatives space.
Re: Learning C3
#23Has anyone tried both C3 and Hare[1]. How do they fare? There seems to be quite the overlap between the two. [1] https://harelang.org/
There's also Zig in the C-alternatives space. https://ziglang.org/
There is also Odin: https://odin-lang.org/
Would be nice to have a list of these and comparisons
Re: Learning C3
#24Earlier quoted context omitted.
Rust is way more complex to say the least, in fact it's the sole reason why it still has the same market share as COBOL( https://www.tiobe.com/tiobe-index/ ). Rust 1.0 was released 10 years ago by the way.
Tiobe really?
I hate on Tiobe as well but it is a good benchmark for world wide adoption commercially.
Re: Learning C3
#25Re: Learning C3
#26After using Rust on a couple of projects, I understand the appeal of simpler languages like C3, Zig, and Odin. As one commenter very aptly put on the Zig subreddit ... "I used Zig for (internal tool) because I wanted to quickly write my tool and debug it, and not spend all my time debugging my knowledge of Rust."
Re: Learning C3
#27After using Rust on a couple of projects, I understand the appeal of simpler languages like C3, Zig, and Odin. As one commenter very aptly put on the Zig subreddit ... "I used Zig for (internal tool) because I wanted to quickly write my tool and debug it, and not spend all my time debugging my knowledge of Rust."
Is Zig really that common at this point that you'd feel comfortable using it for a work project? Its not just going to piss off the next person and have them need to rewrite it? I guess Rust has the same problem to some extent but there is a lot of resources for writing Rust out there now
Re: Learning C3
#28Earlier quoted context omitted.
Rust is way more complex to say the least, in fact it's the sole reason why it still has the same market share as COBOL( https://www.tiobe.com/tiobe-index/ ). Rust 1.0 was released 10 years ago by the way.
Tiobe really?
I don't 100% understand. Do they really just look at search engine stats?
https://www.tiobe.com/tiobe-index/programminglanguages_defin...
That seems like it's a potentially interesting signal, but the index implies that it is about adoption.
Looking at the index, it seems like Python has a 2.5x higher rating than C and Java. While I assume that Python is a widely adopted language, this feels wrong in many ways.
But given that they just look at search engine stats, one can explain the higher rating, because Python is often used by novice programmers and tech workers who are not primarily programmers/SWEs.
Re: Learning C3
#29C3 looks promising, but any language that supports nulls needs null-restricted types, not whatever those contract comments are. If I wanted to have to null-check everything, or YOLO it, I would just write Java... and even Java is seeking to fix this: https://openjdk.org/jeps/8303099
I'm on the fence about function contracts like this. I've seen them for a decade in other languages, but never really used them, so I can't say how I feel about them. But having them be inside comments is just weird.
It's a directive that happens to be placed at the tail end of a comment. Reading the documentation the doc comment stops being a comment-proper with the first @-directive, after that it's a list of directives. SPARK started in comments, ACSL is placed in specially marked comments. SPARK 2014 moved into Ada proper using Ada 2012 features (aspects). The difference between SPARK 2014's annotation and this is basically, are the annotations above the function or after the function declaration?
Re: Learning C3
#30Earlier quoted context omitted.
Tiobe really?
I hate on Tiobe as well but it is a good benchmark for world wide adoption commercially.
TIOBE is an especially poor benchmark if the programming language community is not highly reliant on general-purpose search engines like Google.
Take into consideration that most Rust programmers rely on https://docs.rs etc rather than Googling something.