Why make it complicated?
-
Can we talk about PHP functions with typehints too?
public static function foo(): string {Practically every other language with similar syntax does this instead:
public static string foo() {JavaScript (Typescript for the type part) and python, the most popular scripting languages, use the same order as PHP.
It's usually compiled languages that do the other one.
-
That looks like rust ngl
It's also valid rust syntax.
But if it were rust, this meme would not make sense, since you would just type
let aand type inference would do its thing. Which is much more ergonomic. -
Made with KolourPaint and screenshots from Kate (with the GitHub theme).
Javascript gonna Javascript
-
Good, now invent a keyword for variables you don't want to declare the type. And now that you have a mix of keywords and identifiers on the same place, you can never update your language again.
Also, make the function declarations not use a keyword too, so you get the full C-style madness of code that changes meaning depending on what libraries you import.
I don't understand how not using a keyword to define a function causes the meaning to change depending on imports. I've never run into an issue like that before. Can you give an example?
-
So I think it's still probably unclear to people why "mix of keywords and identifiers" is bad: it means any new keyword could break backwards compatibility because someone could have already named a type the same thing as that new keyword.
This syntax puts type identifiers in the very prominent position of "generic fresh statement after semicolon or newline"
..though I've spent like 10 minutes thinking about this and now it's again not making sense to me. Isn't the very common plain "already_existing_variable = 5" also causing the same problem? We'd have to go back to cobol style "SET foo = 5" for everything to actually make it not an issue
Ah I was misunderstanding the problem. And learned something new about C#, seems in order to avoid breaking existing code they introduce "contextual keywords" var being added later, it is a contextual. You can create a class 'var' and the compiler will prefer it.
-
It's also valid rust syntax.
But if it were rust, this meme would not make sense, since you would just type
let aand type inference would do its thing. Which is much more ergonomic.let a = String::from(“Hello, world!”).into()I’ll see myself out.
-
JavaScript (Typescript for the type part) and python, the most popular scripting languages, use the same order as PHP.
It's usually compiled languages that do the other one.
TypeScript doesn't need the "function" keyword for a method in an object or on a class though.
const foo = { bar(): string { ... } }which I assume is doable because the syntax is unambiguous.
In PHP's case, the method syntax should also be unambiguous.
-
That looks like rust ngl
I was thinking the same thing. who would write typescript if they could just do Rust?
-
It enforces scalar types (string, int, etc) at runtime if you enable strict mode. There's also static analysis tools like PHPStan and Psalm that will flag issues at build time.
so, no. good catch OP!
-
And then assign an int to a string just to mess with the interpreter.
I wish the interpreter cared about assignment
-
Not to short-circuit the joke, but in this case, it's because the valid JavaScript version is...
let a...and one of TypeScript's main design goals is to be a superset of JavaScript, that only adds syntax, and doesn't re-write it.
Beyond that, it's probably a case of some new language just using what the designer is familiar with.
Who says this is JS? Might be Rust.
-
Made with KolourPaint and screenshots from Kate (with the GitHub theme).
String a: new String() -
I don't understand how not using a keyword to define a function causes the meaning to change depending on imports. I've never run into an issue like that before. Can you give an example?
Some declarations terminate on the name, other declarations go one requiring more tokens. In C, the only thing that differentiates them is the type.
Parenthesis in particular are completely ambiguous. But asterisks and square brackets also create problems.
-
Who says this is JS? Might be Rust.
Then the second part of my statement applies.
-
TypeScript doesn't need the "function" keyword for a method in an object or on a class though.
const foo = { bar(): string { ... } }which I assume is doable because the syntax is unambiguous.
PHP's object orientation is similar to languages like Java and C#, which is what I was comparing to.
Your example didn't mention the use of the function keyword. Instead, it seemed to be questioning the placement of the return type - placing it after the argument list seems pretty common in newer languages.
-
And Kotlin.
AND MY AXE!
-
python:
a: str = 1
That's just a comment
-
Made with KolourPaint and screenshots from Kate (with the GitHub theme).
let a: &'static str -
Some declarations terminate on the name, other declarations go one requiring more tokens. In C, the only thing that differentiates them is the type.
Parenthesis in particular are completely ambiguous. But asterisks and square brackets also create problems.
I have never heard of this problem for C. Can you elaborate or point to some articles?
-
You're encoding more information in the typescript one. You're saying it's a string that will get updated.
C# has const string a = "Hello, World";
var in js is legacy, and default should be let, but changing that would break everything
