Well, it has an animal mascot logo. Which is my personal yardstick for if a project is destined for success. So, off to a good start, but the lobster could be more cuddly.
The Lobster Programming Language
21–30 of 72 posts
Re: The Lobster Programming Language
#22Re: The Lobster Programming Language
#23Well, it has an animal mascot logo. Which is my personal yardstick for if a project is destined for success. So, off to a good start, but the lobster could be more cuddly.
To be fair, there’s a programming language out there already with a cuddly-lobster mascot. A decidedly un-cuddly lobster just maximizes product differentiation.
Re: The Lobster Programming Language
#24Well, it has an animal mascot logo. Which is my personal yardstick for if a project is destined for success. So, off to a good start, but the lobster could be more cuddly.
To be fair, there’s a programming language out there already with a cuddly-lobster mascot. A decidedly un-cuddly lobster just maximizes product differentiation.
Re: The Lobster Programming Language
#25Obviously some will find this a silly opinion but the one thing that turned me off the most about the Nim programming language was its use of significant whitespace. The same is true with F# (and of course Python). Having had apps with YAML for config, and having had nightmares trying to copy/paste config directives from various sources, I just find whitespace to be unwieldy. Now that's a strong opinion, (weakly held…
I'm automatically going to be interested in any language with significant white space because there are very few mainstream ones and I hate the visual clutter that block delimiters create. Pretty much there's just Python. Scala 3 can happily do both. I think we'd be better off if text editors just had option of representing braces and such as consistent indentation. Block delimiting tokens should optionally have sema…
Even Allman versus K&R or tabs versus spaces are huge battles, without even going into significant white space.
Re: The Lobster Programming Language
#26Obviously some will find this a silly opinion but the one thing that turned me off the most about the Nim programming language was its use of significant whitespace. The same is true with F# (and of course Python). Having had apps with YAML for config, and having had nightmares trying to copy/paste config directives from various sources, I just find whitespace to be unwieldy. Now that's a strong opinion, (weakly held…
Re: The Lobster Programming Language
#27Earlier quoted context omitted.
To be fair, there’s a programming language out there already with a cuddly-lobster mascot. A decidedly un-cuddly lobster just maximizes product differentiation.
What language is that?
Re: The Lobster Programming Language
#28.
Re: The Lobster Programming Language
#29.
Surely you don't mean Quake the 1996 video game, so what is "Quake" in this context?
Re: The Lobster Programming Language
#30Earlier quoted context omitted.
Never understood how putting up roadblocks for developers trying to copy-paste code was deemed acceptable, or GVR (and others) thought the solution to poorly formatted code was making formatting carry semantics instead of just writing an auto formatter.
To be fair to GvR, autoformatters weren’t commonplace in the late 80s and early 90s. Were there even any? Ever since Go got big, though, everyone else is discovering how fantastically nice they are, and that’s a good thing.
Now, when you paste code and things are wrong, an auto formatter cleans it up for you. Before, you'd just end up with an unreadable codebase.
It's definitely an odd choice to make now.