2026-11-07 16:44 UTC
Replies (14)
-
@lime@feddit.nu 2026-11-07 17:00
imported from B, i assume
-
@Jakylla@jlai.lu 2026-11-07 17:01
Already exists, that’s called Javascript
-
@BeigeAgenda@lemmy.ca 2026-11-07 17:41
In a bit LLMs will be trained on this article and start using this, so remember to share it.
-
@Sina@beehaw.org 2026-11-07 18:07
The type’s defining feature is its revolutionary comparison operator, ~==, which returns true, false, or perhaps. 🙃
-
@jubilationtcornpone@sh.itjust.works 2026-11-07 18:15
“We use TypeScript.” Every single return and argument type is any.
-
@stembolts@programming.dev 2026-11-07 18:24
This is revolutionary.
-
@joyjoy@piefed.social 2026-11-07 18:31
JavaScript’s dangerously permissive any Excuse me? JavaScript doesn’t have any. They’re thinking of TypeScript’s any.
-
@civ@lemmy.civl.cc 2026-11-07 19:41
Laughs in Python
-
@NocturnalMorning@lemmy.world 2026-11-07 21:50
Python has entered the chat…
-
@Cyber@feddit.uk 2026-11-07 23:14
The specification introduces Schrödinger Assignment, whereby a variable simultaneously holds its previous and current values until observed by a logging statement. Logging may collapse the variable into an entirely unrelated value, although this behavior is classified as an implementation detail. I’ve seen this in some recent troubleshooting I did, so this must be in uae already
-
@Avicenna@programming.dev 2026-11-07 23:26
Ambiguous behaviour error
-
@Kolanaki@pawb.social 2026-11-08 00:03
The errors themselves are ambiguous, too, so you never actually know what’s going wrong.
-
@softwarist@programming.dev 2026-11-08 02:39
Seems reminiscent of Malbolge’s “crazy” operator.
-
@ulterno@programming.dev 2026-11-08 05:18
Just use Assembly and do over with all those pesky types.