funny_falcon

systems, upstart or even simple primitive script wrapper.

Built-in is also possible: just fork once after start, and you have parent as watchdog and restarter.

I believe, it was pro-military, but not pro-war. The book idealizes the state and social system, and uses war only as a backdrop.

Compilers still prefer LEA to multiply on 3,5 and 9, which performs shift+add I believe.

First SmallTalk versions were built with Lisp. “Live environment” and “world image” were just inherited.

And looks like Helix editor uses it together with ropey.

OMG!

returns_struct looks actually correct to me, ie it is expected (by me). Golang's defer works this way.

Do both examples follow standard? Or is it common misinterpretation by all compilers?

Do you use stanza?

There is the trick: use enum for const. It works most of the time.

It seems meson is gaining traction and will overpass cmake in near future.

Another quite similar technique from OpenSmalltalk: https://clementbera.wordpress.com/2018/11/09/64-bits-immedia...

In fact, CRuby successfully combined “Self Tagging” with pointer tagging. Here's the commit:

https://github.com/ruby/ruby/commit/b3b5e626ad69bf22be3228f8...

I mean, CRuby does “Float Self Tagging” for years. Paper just has the mistake about CRuby.

CRuby uses this technique on 64bit platforms for years.

Edit: the commit https://github.com/ruby/ruby/commit/b3b5e626ad69bf22be3228f8...

Just correction: CRuby uses “Float Self-Tagging” for years.

But commits exists even this year: https://sourceforge.net/p/lush/activity/

Readability, reproducibility, and simple LRU.

Reproducibility matters for tests, they become simpler. Some other algorithms become simpler as well.

LRU is just a dict with preserving order: on access just delete and insert again.

Unfortunately, pocketpy moved to global reference to vm recently while changing implementation from C++ to C. Weird decision.

AFAIK, Signal doesn’t provide any way to prove its application were built from non-modified audited free open source code. Indeed there are evidences it behaves “a bit” differently.

So unless you’ve built application by yourself, you have no guarantee of it’s sequrity.

What “Statically typed” would mean for SQL DB with extensible type system?

As a PostgreSQL smallish contributor I just can say: NO, DON'T DO THIS!!!!

Extensible type system is a worst thing that could happend with database end-user performance. Then one may not short-cut no single thing in query parsing and optimization: you must check type of any single operand, find correct operator implemenation, find correct index operator family/class and many more all through querying system catalog. And input/output of values are also goes through the functions, stored in system catalog. You may not even answer to "select 1" without consulting with system catalog.

There should be sane set of builtin types + struct/json like way of composition. That is like most DBs do except PostgreSQL. And I strongly believe it is right way.

First three are clearly documented in language reference, which could be read in several hours (at least before generics were introduced).

Most weird thing: PostgreSQL's checksum algorithm is almost free on modern processors. It uses SIMD instructions extremely well in optimized builds. I've never seen him in CPU profile despite I always enable it.

There are no any reasons to not enable it (except pg_upgrade).

Lemire uses your found but corrects its biases.

There was one: https://github.com/grumpyhome/grumpy

Looks like abandoned though.

`git gui` and `gitk` my Swiss-knife tools for every day git-ting. They are maintained by git core team.

Sun bought whole team of Self [1] language to make its HotSpot JIT.

[1] https://en.wikipedia.org/wiki/Self_(programming_language)