73 karma · joined January 15, 2017
In the end we have stable developer velocity metric and a really close estimate for each new version.
UX matters, and user does not care if the native wrapper or 500kB of js is there or not, as long as the job is done conveniently and fast.
Enforcing choice of the backup solution would solve the problem of rogue countries like the UK meddling with privacy and security.
Like the browser choice, backup provider choice can end up being enforced, likely by the EU as they have a good history of breaking up vendor lock-ins.
Possibly an information/lobby campaign can be started and endorsed by some major online storage providers?
Another one is I could not find a benchmark with io_uring - this would confirm the benefit of going from epoll.
Apologies but it had to be said.
https://bugs.webkit.org/buglist.cgi?order=changeddate%2Cbug_...
But...
The actual main problem of ORM is not just ORM but a multi-layered translation of target language query code
- to internal target language database schema modeled from/to a db schema
- then to SQL syntax
- then to wire request to db
- then to SQL validator in db
- then to internal database query planner targeting relevant schema elements
- then to raw index/hash/scan executors
You see the picture?
If the database schema wire protocol could only be converted to the target language objects without SQL translation sitting in the middle, query would run optimally and with up-to-date statistics to query planner.Think of WASM-like protocol (as opposed to JS) to which queries are compiled in the client and passed to the db.
It has been done before on a basic key-value wire protocols and to an extent on graph databases with json requests. Structured relational data is making this hard to do as one would need to have up-to-date db stats in the client along with all index details to run an optimal query.
On the other hand, compiling this:
db.Posts.Get(p => (p.Authors.Includes(a => a.IsBoss))
? { Date: p.Date, Bosses: p.Authors = p.Authors.Filter(a => a.IsBoss), Groups: p.Groups.OrderBy(x => x.Name).Top(5) }
: { Date: p.ModifyDate, Bosses: null, Groups: p.EmployeeGroups.First() }
)
Into SQL would be close to impossible in an optimal way.
Alternatively, with schema access in the client it, one could write internal db "assembly language" procedure for looking up using indexes, conditional querying and spitting out binary result for minimal effort hydration.Just an idea, I am not aware of similar client query planner solutions available.
Bonnie Robertson is a thriving 10X support high earner
Obviously from our observed laws perspective we can find (we did not yet) reasons for such preferences yet changing conditions (time, matter density, energy, velocity, gravity) can potentially influence preferred laws and states of matter. Think of superconductivity, how is it even possible that there is no resistance in electron flow, we only make use of this phenomena without understanding the theory behind it.
I am looking forward for the book, just a tiny glympse of different perspective can influence a series of new inventions.