missblit

Rationalism doesn't involve doing math, but _role-playing_ like you're doing math. There's lots of talk about updating priors and bayes; but in practice a lot of stuff isn't that quantifiable without running scientific studies, so this comes down to #yolo-ing it.

Of course thinking about stuff without always using formal statistics is fine and how people work, but if you trick yourself into thinking that you do use statistics for everything it may become harder to evaluate or second guess your own thinking.

See this is why I once used moon-viewing-ceremony-seperated-values (MVCSV). The Moon Viewing Ceremony emoji was unlikely to show up in my dataset, and not only is the emoji visible, it's quite visually pleasing.

Bugs:

#1 if you spam the "add a new source" button you eventually get a JavaScript exception logged to the screen due to an array with a fixed max size of 128 elements overflowing.

#2 this could be graphics card or driver specific (I have an AMD card), but scrolling just right can can break the simulation due the the text boxes; for example by quickly paging up and down, or scrolling all the way to the bottom and then wiggling the scroll position up and down. Once this happens the bad data propagates until the entire thing is filled with noise, solid black, or solid white. If you then scroll up to 3D mode the screen will be filled with a mess of polygons.

Steam has supported native Linux games for a decade.

C++ is a very slow moving language. There are various rumblings about making it memory safe, but if we get a proper memory safe C++ it'll probably be in the '30s.

Hello,

Your example paper has omitted non-English characters in the names of anyone who gets cited. Look especially at citation [5], where a lot of the authors have European characters in their names which get omitted.

There is also possibly a missing × or ⋅ in "1.81 10^5" on page 3.

Encodings I have used or been exposed to in my career: ASCII, Latin1, Windows-1252, UTF-8, UTF-16, UTF-32, GBK, Zawgyi, Shift-JIS

I used a similar technique in a university class. We were doing a Connect 4 bot tournament, and I wanted mine to be as optimized as possible.

But in the end I spent all my time playing around with bitwise operations, so had no time left to add in multiple threads (so couldn't was slowed down by a factor of 4 or so) timing (so had to cut off the search early to not accidentally go over the limit), or to tweak the score heuristic.

Which meant my program only got second place. Still, I think the teacher enjoyed it, and there were some oohs and aahs when my program output moves basically instantly during the tournament.

> I sometimes wonder how many of its 149,813 ‘characters’ any one human is likely to use, and suspect for most that’s in the low hundreds or less.

Chinese sends it's regards.

But also text interchange is useful even if most people only use a fraction of it most of the time. How else is an English document supposed to quote Chinese characters for instance (this happens all the time on wikipedia pages which share the original name of something next to the translation).

The days before unicode were dark days, nowadays besides the ocassional oddity text pretty much just works without users thinking about it -- thanks to unicode.

He's using the word as meaning "insert", not the JS function. He is saying he inserted a new row into a database to get admin access to a dashboard.

'splice" means to join two things as if by weaving them together. If used as "splice into" or "splice in" there is a sense of breaking something apart, inserting something into the gap, and joining it back together.

This all makes a bit more sense if you look up the etymology which was about ropes (despite splicing being about uniting, it's closely related to the word 'split').

So this is pure speculation, but more people should be aware of parser differentials (same thing as that email thing the other day) so let me say what I mean...

Hypothetically say a website has an internal service to index posts for keywords for search, that just so happens to unescape HTML entities during keyword normalization due to a seemingly harmless bug.

Plus a second internal service to identify keyword spam that _doesn't_ do any HTML entity unescaping (because why would you?)

Then you could end up in a situation where a spammer uses HTML entities to avoid spam detection while still showing up in search results. They hope that the user ignores the nonsense text and just clicks their link based on the image (a list of big shopping brands in the middle east) instead.