devnull3

For folks who do did not get the reference, here is THAT runout:

https://www.youtube.com/watch?v=XxiyKWBPshg

Not that watching this will greatly increase the understanding of the game who do not know cricket.. but still.

(Basically the the guy in greens who was not batting simply did not run ... his is Alan Donald)

I think 12k is just the start. The overall number will higher.

How so? I don't know much about Dubai (from emmigration pov) other than the fact that its a low-tax destination.

As a high-earning & tax paying immigrant in UK, it seems it is much easier to come to UK illegally than by legal means. It is getting harder to get a PR.

Cost of living, rise in taxes and degradation in Govt services (e.g NHS) really has got me thinking whether staying in UK is really worth it.

> is combined with oxygen to form carbon dioxide

Isn't that some mass will be get converted to energy while burning? So the weight of the resultant CO2 will be less than the fuel burnt.

I have a naive question:

   When we use/burn non-renewable fuels (crude, wood, coal, etc) it will reduce the mass of earth over the period of time. At which point (if at all) it will affect gravitational force between earth & sun as per the formula [1]

By "affect" I mean in a noticeable way.

[1] https://www.google.com/search?q=gravitational+force+formula

I don't think so. Govt of India has been promoting Sanskrit (without much success) since many decades. There is/was even Sanskrit news. Now-a-days I can see "Weekly Sanskrit Magazine: Vaartavali" from national news Doordarshan [1]

[1] https://www.youtube.com/watch?v=ELmU3GXcuuo

> Brahmos

Nitpick: It is actually amalgamation of Indian & Russian rivers. Brahmaputra (India) and Moskva (Russia)

There is a requirement where I need data which existed at timestamp T or version V. So even a WAL needs to be versioned.

This is a part of a larger system which requires versioning of data. So there is a requirement of reading the data as of timestamp T. The sqlite is supposed to be metadata of that large data. Since the larger data itself is versioned I need metadata to be versioned.

Some of the use-cases are mentioned at: https://news.ycombinator.com/item?id=32629548

In git, each version of the database will be a full copy. The git has to perform diff i.e. scan the database file. Imagine doing commits & creating snapshots very frequently.

Have a look at https://github.com/sudeep9/mojo/blob/main/design.md#index

Yes. But you need to have such a filesystem installed at the first place.

Mojo can run on any filesystem which does not support snapshots/versions. This makes it portable not only across different fs but also across OS.

Noted.

I have changed the license to MIT.

I have changed the license to MIT. Sorry for the wrong impression.

(I am the author) Some of the use-cases of mojo I could think of:

1. Rollbacking DDL changes (like create table, adding columns, etc)

2. (My use-case) Multiple readers-single writer. Readers read old versions. Writers do not block readers and vice-versa. Note: this is different than reading+writing in the same version can still happen but with database-level locking.

3. Extension of #2: The older versions read from S3 so that lamda can read.

4. Extension of #3: Readers reading from old immutable snapshots makes the database as a queue of complex changes with indexes and all the benefits of SQL.

5. Backups and replication.

Oh: I have change the license to MIT

From what I know of litestream, it should be decoupled from VFS implementation. The versions/snapshots are not known to the database.

I think you can read the code. I knowingly made the repo public. You do not even have to login to github. I think it should be ok.

Not sure I understood your question fully, but if there are multiple versions, then read will be over multiple files but writes go to a single active version.

I am the author. Mojo is both an extension and a VFS implementation.

> AFAIK only one VFS can be active at a time.

You can specify VFS as a part of connect URI.

> is it some kind of a tease

(I am the author). It's definitely not a tease. The license will change within a week (max 2). This is my first open source project. The purpose is to validate the approach.

This has been a private project for a very long time. It can be argued that I should have figured out the license but the delay from my side reached a tipping point. I just thought "make it public, figure the rest later".

Only modified pages go into a version data file [1]

[1] https://github.com/sudeep9/mojo/blob/main/design.md

I can confirm that it does. I am working on it as I write this :).

Technically, an extension and VFS are separate things.

An extension when loads, allows you to register the VFS with the Sqlite. It can also register virtual tables as well.

It just so happens that I am working on a versioned file system for sqlite based on its VFS interface. Planning to release it in a week's time. It will be in pre-alpha stage and its more of a proof-of-concept.

Having worked with FUSE in the past, there is always some performance penalty, but the advantage is that there is no change in the application.

The VFS will need change in the application but less overhead. Trade-offs!

> What would be a good use case of Rust than Golang

If you can afford GC in your project go for Golang else Rust.

I don't know how much nuclear reactors have advanced. But I can understand the fear in the someone's back of their mind: What if something goes wrong?

I see this risk = Fallout x Probability. Even though the proponents argue that the tech is much more safer, the fallout is so huge and generational that its it neutralises the low probability of any accidents.

PS: I am neither for or against the nuclear tech.

India consistently disappoints the most optimists and the pessimists about its potential.

Until last year I too use to dream working in Google. But increasingly the attractiveness is decreasing. I cannot put a finger on one specific thing. It has gone too large from a career pov.

Nice! Now this would be expected algo from candidates in google/meta interviews, especially for senior IC roles.

Update your leetcode answers folks.

Small piece of wisdom I received when I was an intern:

"Never get sentimental with your code"