true + ("true" - 0) ?
"" && -0 ?
Like, can you tell me a language where it does make sense to "apply AND to an empty string and a (negative?) zero"?
If you write code like this, you have much bigger issues than whatever you choose to write your code in.
My code has bugs occasionally, because I'm a human. Which is why I would like my programming language to return errors when I make obvious mistakes.
> Like, can you tell me a language where it does make sense to "apply AND to an empty string and a (negative?) zero"?
No I cannot, which is why I can't imagine why JavaScript wouldn't return an error for this situation.
How does one enforce a strict subset with an easy setup? Why are people writing non-browser code in this horrible language, often without strict subsets or typescript?
Obviously there are solutions, but the solutions clearly aren't pervasive enough because the problem is still here (and growing, as more JS code is written), so we as an industry still need to keep talking about how problematic and poorly-designed JS is.
The old solution are the good books like the good part. The new solution would be typescript.
It's unlikely the API will get deprecated no matter how you talk about it. It's the windows of internet. Any sane shops would use typescript. U don't even need to write ts, and could just let the compiler do the hinting for you.
Deprecation isn't what I want. Equivalent alternatives are what I want.
I still can't do <script type='text/typescript'>. Why?
And look, Typescript is also hampered by some of JavaScripts bad choices. Actor-model concurrency would be a really good way to handle events and parallelism to boot, but we won't get that in any language that compiles to JS.
WASM isn't an alternative, because you can't use WASM without JS.
Because typescript is not javascript. Google already tried with dart, they failed. Typescript is still nice-to-have, it's not replacing javascript. MS is not trying to replace javascript anyway. If your goal is to having javascript replaced, that looks fine but I don't see how it succeed. If you u want to work on TS codebase in backend, there is deno
> Because typescript is not javascript. [...] Typescript is still nice-to-have, it's not replacing javascript.
+1. TypeScript compiles to JavaScript, so it can't replace something it compiles to. Besides, text/typescript isn't even a valid MIME type. The text type is meant for plain-text documents (.txt, .md, etc.), so TypeScript would have been in the application type, following JavaScript (application/javascript). Getting TypeScript in a web browser would be too much work. For starters, they would need to take the TypeScript compiler, slap it into a web browser, where it would compile the TypeScript code, pass the result onto the JavaScript compiler, which would finally pass the result to the browser. Whats wrong with this? The code has to undergo two compilation layers, and, most importantly, the TypeScript compiler in the web browser can be out-of-date with mainline TypeScript releases. Your best bet right now is using a web framework with TypeScript support.
it actually aids in writing faster (more JIT-friendly) code by alerting you to these implicit type mutations/coercions.
The point is that in lots of languages these statements would simply result in compile time errors. In JS, though, the type coercion rules are so loose (and in many cases extremely non-obvious) that you can see this head-scratching behavior.
It's the same underlying behavior that leads to very cool/very insane stuff like JSFuck: https://jsfuck.com/
This weak typing is unique to a few languages like JS and PHP. Python is just as dynamic, but will at least throw an error if you try to accidentally add a string and a number. Static languages catch this even earlier.
get_current_username: Returns a nonempty string iff user is logged in.
get_balance: Returns a user's "balance" of some sort of credit or currency. Negative balances are possible.
should_render_balance = bool(get_current_username() and get_balance())in js, Boolean('' && 0) will give you the same answer as bool('' and 0) in python.
if i code golf in python (like the article does in js), i'll also get weird-looking code and "unexpected" outputs.
valid python: 0*"string"or"other_string"
> Like, can you tell me a language where it does make sense to "apply AND to an empty string and a (negative?) zero"?
People do stuff like that in Python all the time. Personally, I don't do it in JS, though, because I find the conversion-to-bool rules much less predictable. In this case, though, I guess JS would behave the same.
typescript helps, but i have fired some of these footguns even with typescript.