Their is a huge conflict of ingerest of giving this power to a major economical actor that vastly depends on public investment and under public scrutinity.

Executive should have the audit right and in some measure probably it should be widespread to all citizens up to sensitive data not being leaked. But what good is there to give this power solely to one of the richest and more powerful man in the world? This is crazy.

It seems completely random but in a coherent way. It is wonderful.

Anyway, you are right and not pedantic at all.

https://link.springer.com/chapter/10.1007/978-3-030-51074-9_...

The proof is 200Gb large. I am quiet sure now even larger proof exists, in particular thet exhaust some combinatorial property on graphs.

I have read that you write some of your own parser for perf boost.

(I am one of the author of https://github.com/V0ldek/rsonpath)

In Python, I often use the following constructions:

https://pastebin.com/pmnxg0Ji

Translating in js we got:

https://pastebin.com/WpfDnVFX

Reading the doc, I understood that JS is initializing fields after the super is called. Hence, fields and methods behave differently with respect to inheritance.

The "correct" way to translate the Python code seems then to wrap the fields into a getter which gives actually the following:

https://pastebin.com/8ZYT6vDe

I wonder why JS is implementing such a semantic for fields. It sounds hacky to and feels like field shouldn't be mixed with inheritance at all but maybe I have overlooked something?

Comments URL: https://news.ycombinator.com/item?id=39447453

Points: 1

# Comments: 0

Shameless promotion of my beta engine

https://github.com/V0ldek/rsonpath

It is not a mystery why all webscale companies endup designing their own DB technology.

That being said, most of the DB in the wild are not remotely at those scale. I have seen my share of Postgresql/ElasticSearch combo to handle below TB data and just collapsing because of the overeng of administrating two DB in one app.

I am happy that my queue inherit ACID properties.

SQLite simply doesn't allow concurrent write so it is a no go for a queue.

I don't know much about SQL Server and MySQL but I wouldn't favor a lockin closed source software or anything remotely connected to Oracle.

At the end, only Postgresql remains I guess. Also, Postgresql is super solid and the closest to SQL standard.

This would allow easier reporting within a very active db without too much bother.

The code isn't magically solving NP vs P but it does simulate non deterministic run through a potentially exponential exploration.

The cool stuff here is the simplicity of the interface to it and its integration thanks to high order functional constructs (decorator).