maxpert

It’s an interesting choice for sure because I heard a lot of ifs and buts for loads of eventually consistent scenarios on why people wanted to not make any changes to their code and don’t really wanna load extensions. Loading extensions is definitely better in terms of transaction control. I did a lot of soul-searching before settling for sidecar approach. In order to not be an interface and stay away from binding complications for various platforms I opted for sidecar. Once done I was already able to scale out of box stuff like PocketBase.

So per-node there is an order of changes (read internals doc), and all of changes are sent to JS in that commit order. These changes when replayed will always eventually result in same values.

Since each write is logged into a JetStream. The last writer will win for conflicting changes.

Ideas in CRSQL are remarkably similar to Marmot (https://github.com/maxpert/marmot) except that it doesn't require an extension to be installed, and it can run as sidecar. I can see how having extension makes it simple to intercept writes, and transactions. Since marmot builds on top of NATS, and JetStreams work using Raft, it can easily scale and keep the libsqlite on disk guarantees intact.

Interesting approach, I use a very similar methodology in Marmot (https://github.com/maxpert/marmot) to do CDC for SQLite via triggers, and then these changes are published over NATS, replicated over to other nodes. So row-level replication powered by similar outbox except it uses NATS and JetStreams's quorum property to ensure reliable recovery.

While I love ingenuity of developers at Hasura (because I've been personally through these scaling challenges), I always get a gag reaction with GraphQL. I've honestly tried hard to digest it, and I can tell you at large scale where single DB won't cut it, you would either need to develop a large federation layer like [Netflix](https://netflixtechblog.com/how-netflix-scales-its-api-with-...), or just rip-it out. Streaming might elevate the problem a little, but I real problem still lurks under the hood. The fact that front-end community wants to fit everything under GraphQL bothers me, because every backend developer knows that a single tool/technology is usually not the best tool for solving all problems of your life. Remember the golden words, THERE IS NO SILVER BULLET!

A shameless plug here I've been working on a project of my own called [Marmot](https://maxpert.github.io/marmot/) with the intention of making SQLite replication masterless and eventually consistent. Project is in very early stages, and I've been using it for one of my site replicating a cache based off SQLite. It builds on top of NATS (I love NATS), and distributes itself over JetStreams.

This can potentially become very interesting where if all these pages are pushed to edge via CDN, then browsers can essentially have a GraphQL built on top of SQLite on the client side.

Novelty that wears of super quick. I know people who bought Oculus out of hype and then just after a week it’s sitting on table collecting dust.

AMD PRELIM 3Q REV. ABOUT $5.6B, EST. $6.71B

AMD CITES WEAKER CLIENT SEGMENT REVENUE

AMD: WEAKER THAN EXPECTED PC MARKET, INVENTORY CORRECTIONS

Yes for basic websites simple DB based session might be enough. And if you think about these sessions they are essentially opaque and stateful tokens pointing to a row in DB containing the information you need. But saying JWT sucks in plain generic terms is out of context statement, in large micro-service environment if every front-end service starts hitting an identity service the fan out is gonna kill you! You keep a basic set of information in token that is most often used, not every service will need user phone number, and all of his roles. 95% of your read traffic will need some basic ID, email, and basic roles that can be satisfied from JWT token. What OKTA is suggesting essentially is gonna push all the load onto a DB or some sort of datastore, so that it becomes SPOF, and now you have shifted problem to scaling that DB/Datastore. Answer IMO is it depends.

He and his round lead Atif Awan have been part of fraud rumors. According to their slide deck back in 2021 they were supposed to be profitable by end of 2021. Once you look at the numbers being quoted in the deck and avg Pakistani house hold, they don’t add up. So Gul can do all glorifications that he might want, it doesn’t change the fact that there have been some shaddy practices involved in the a whole group of people associated to this company.

I've been down this road multiple times with Arango DB, and Orient DB and IDK how many others. Doing too much of everything usually means not good at everything. I will stick to doing one job good, and battle tested tools.

I’ve seen a lot of movement in FX lately but lesser and lesser desktop apps coming out for Java specifically after electron apps picked up. Who here plans to use Java for their next consumer desktop app?

Also try LZ4 and Snappy. Depending on your use case they can save your extra CPU too.

Disclaimer: Final Cut user here, so I will be extremely biased.

While parts of UI are ripoff from Final Cut. I still found it to be pretty basic. Won’t be using it and I doubt other professionals will.

Nevertheless can be good tool for free usage and meme makers. It still unlocks a sizable market for Microsoft.

So we've come full circle. From the talk of author on how "NPM was a big mistake", to "Nobody is adopting it, we will die without the NPM ecosystem". I was hoping that Deno will spin off into something that can be compiled due to type system hints into something more optimized than JS, but seems like I was just living in dystopian utopia.

Agree! There should be option to have pluggable storage system for this. That way people can write + pick and choose what storage mechanism they need.

Not a single link to buy from official site? What am I supposed to do? Look at the how awesome your Go fund me project is?

I think you are 6 months into recession the readouts will just make it official.

Same here, wanna see some production usage testimonials. Plus has someone compared it to CockroachDB? I understand they are two different technologies with broader strokes of same idea of scaling Postgres horizontally but still would love to see some sort of comparison and differences.

// One last time remembering IE6

var request = new ActiveXObject("Microsoft.XMLHTTP");

Sad day! But VSCode ate it up. Whatever one might say this had a huge hand in making Electron mainstream.

How does this compare to other multithreaded redis protocol compatibles? KeyDB is one key player https://docs.keydb.dev/

I love it! Using this I’ve seen FB/Google having less and less information about my exact location. Seeing less relevant ads is assuring and relieving! The only wish I have is a more fluent way to enable/disable this and having an app for other platforms.

I wish someone can do a Rust/C based implementation for this so that I can use it in other languages.

Do you plan to opensource the implementation some time?

Isn’t this the company where some hedge fund published report on and they have a short position? Until there is no 3rd party testing and independent publications verifying their claims I am not buying anything. I know I sound skeptical but I’ve lost enough money on SPACs.

Goes to show how "red buttons" won't make a difference when it comes down to screwing up.

IDK if people have seen or tried H3. It has worked really well for me in past https://eng.uber.com/h3/