https://l5lua.org/l5-for-processingp5/

Well, now I know what we should be pouring if anyone plans to use the expression "pour one out for…"

Jesus Christ, 80 hours?! I really hope the author seriously takes a proper break! I mean, they seem to be riding that incredible high that comes from having a breakthrough in deeply understanding a really tough problem after thinking about it for too long, so I kind of get it, but that is also all the more reason to take good care the precious brain that now stores all that knowledge, before it burns out!

There might be common scenarios where this had a real, significant performance impacts, E.G. use-cases where it's such a bottle-neck in the interpreter that it measurably affects warm-up time. Also, string manipulation seems like the kind of thing you see in small scripts that end before a JIT even kicks in but that are also called very often (although I don't know how many people would reach for Java in that case.

EDIT: also, if you're a commercial entity trying to get people to use your programming language, it's probably a good idea to make the language perform less bad with the most common terrible code. And accidentally quadratic or worse string manipulation involving excessive calls to trim() seems like a very likely scenario in that context.

However, I do have to give one bit of critique: it also makes my laptop fans spin like crazy even when nothing is happening at all.

Now, this is not intended as a critique of the author. I'm assuming that she used some framework to get the results out quickly, and that there is a bug in how that framework handles events and reactivity. But it would still be nice if whatever causes this issue could be fixed. It would be sad if the website had the same issue on mobile and caused my phone battery to drain quickly when 90% of the time is spent reading text and watching graphics that don't change.

And in turn each of those may also appear simple in isolation, but as a whole it can still be an overwhelming amount of knowledge to learn, integrate and connect the dots between (and then once you reach that level of mastery, there's meta-problem of applying outdated rules of thumb from a few decades ago to modern hardware). That's where the advantage of having the kind of lifelong experience like a former demoscener gamedev comes in.

Anyway, my earlier post might have been a bit tongue-in-cheek but I'm rooting for you to surpass this guy one day! :)

> By using only a single instruction and two tables, we only increase the interpreter by a size of 1 instruction, and also keep the base interpreter ultra fast. I affectionally call this mechanism dual dispatch.

I really do hope they'll write that better explanation one day because this sounds pretty intriguing all on its own.

https://www.voxagon.se/

Because it looks like your opponent is a Swedish former demoscener who started programming at age 12 on the C64 and Amiga computers in 1990, quickly moving on to writing games and demos in assembly, then professionally developing physics engines since 2001, specializing in game performance profiling and squeezing performance out of optimized mobile games.

As far as game dev stereotypes go you basically picked a Final Boss fight. Good luck, you'll need it :p

And speaking as a Dutch man, given the kind of humor we have I'm pretty certain Dijkstra appreciated a good roast like that too.

> From that apparent beginning, the Angzarr was swept up into the Monotype typeset catalog of arrow characters (...) It is unknown why Monotype added the character, or what purpose it was intended to serve

> In 1988, the International Organization for Standardization added the symbol to its Standard Generalized Markup Language (SGML) definition, apparently pulling it from the Monotype character set.

> In March 2000, the Angzarr symbol reached wide distribution when the Unicode Technical Committee, in collaboration with the STIX project, proposed adding it to ISO/IEC 10646, the ISO standard with which the Unicode Standard is synchronised. The Angzarr was proposed in the ISO working-group document Proposal for Encoding Additional Mathematical Symbols, although no specific purpose is listed for the symbol.

My guess is that the people proposing the addition of new maths symbols[1] weren't going to decide on inclusion or exclusion of a symbol on the basis of being familiar with it themselves or not, since that was likely true for many symbols that happened to only be used in fields of mathematics that they were not working in. Meaning they had to rely on some other kind of "authority" to infer that a symbol was used by the larger maths community. With that in mind "being part of the Monotype catalog and part of SGML" seems like a pretty sensible heuristic to go by.

Another consideration might have been that they simply wished to have complete coverage of the symbols that SGML encoded, regardless of familiarity with the symbols involved. And of course both could have been true.

[0] https://www.unicode.org/wg2/docs/n2191.pdf

[1] https://en.wikipedia.org/wiki/Angzarr

Tasteless joke, dude.

You're calling a direct quote of a testimony given by one of Epstein's victims "hearsay". ctrl+f "bit" in that PDF.

Pretending to be oblivious to the many complaints that the attacks in Iran are another attempted distraction from the Epstein files isn't fooling anyone either.

You may feel like it's "off-topic", but I don't see why people should be allowed to talk about and glorify military techology, but not voice their disgust at it, how it is used, or why.

https://www.justice.gov/epstein/files/DataSet%2010/EFTA01660...

https://observablehq.com/@jobleonard/variable-coefficient-di...

That's a statement that I expect to infuriate just about everyone who lived in Eastern Germany, how do they get away with that argument?