It means you’re compensating for the lack of optional/named parameters in your language.
It means you’re compensating for the lack of optional/named parameters in your language.
When you want to print something, you can’t just Printf.printf x
, you have to explicitly give it instructions on how to print a value of that specific type.
I’ve recently been trying to learn OCaml and find it really nice. The major pain points are
What does Rust improve over its predecessor? The only really new thing is the borrow checker, which is only useful in very low-level programming.
C is the first language I learned and I think it’s a terrible language full of inconsistencies, footguns and unnecessary complexity.
beer ~ piss
wine ~ rotten blood
coffee ~ diarrhea
raw meat (tartar steak, etc) ~ used chewing gum picked from a pavement
dark salami ~ rotting corpse
vinegar ~ battery acid
moldy cheese ~ moldy cheese
Not if the language is standardized from the start.
An alternative would be a language with a simpler syntax. Something like XML, but less verbose.
Have you read the CommonMark specification? It’s very complex for a language that’s supposed to be lightweight.
Markdown is terrible as a standard because every parser works differently and when you try to standardize it (CommonMark, etc.), you find out that there are a bajillion edge cases, leading to an extremely bloated specification.
The only mention of capitalism in the article is specifically venture capitalism.
I think “uniform function call syntax” is the established term for this particular feature.
That’s true, but if the transformations have more than one argument, they go after the name:
data.split(",").join(";")
as opposed to concatenative programming languages, where all arguments go before the name and there’s no visual indication of the structure:
data "," split ";" join
Also, there are more languages with this feature, for example D, VimScript or Koka.
Re the sidebar: How are Nim and Roc partially concatenative?
JavaScript is an example of how OOP can be done without classes (before they were added to appease Java enthusiasts).
Each request is a totally independent request that rebuilds the world. There’s no shared state (unless you want there to be).
I with there was a language with this model, but without the language itself being completely garbage.
Betteridge’s law of headlines…