jaseemabid

I recently wrote an explainer for the sqlite file format with some helpful diagrams. This might help.

https://blog.jabid.in/2024/11/24/sqlite.html

Immutable append only persistent log doesn't imply store everything _forever_.

If you want to remove something you could add a tombstone record (like Cassandra) and eventually remove the original entry during routine maintenance operations like repacking into a more efficient format, archival into cold storage, TTL handling etc.

A notable example of a large-scale app built with a very similar architecture is ATproto/Bluesky[1].

"ATProto for Distributed Systems Engineers" describes how updates from the users end up in their own small databases (called PDS) and then a replicated log. What we traditionally think of as an API server (called a view server in ATProto) is simply one among the many materializations of this log.

I personally find this model of thinking about dataflow in large-scale apps pretty neat and easy to understand. The parallels are unsurprising since both the Restate blog and ATProto docs link to the same blog post by Martin Kleppmann.

This arch seems to be working really well for Bluesky, as they clearly aced through multiple 10x events very recently.

[1]: https://atproto.com/articles/atproto-for-distsys-engineers

Pkl was one of the best internal tools at Apple, and it’s so good to see it finally getting open sourced.

My team migrated several kloc k8s configuration to pkl with great success. Internally we used to write alert definitions in pkl and it would generate configuration for 2 different monitoring tools, a pretty static documentation site and link it all together nicely.

Would gladly recommend this to anyone and I’m excited to be able to use this again.

This is what I wanted Apple News to be.

I wish it would give me a good curated news feed from dozens of sources, and adapt based on feedback. I badly wanted to love it, but no matter how much I tried it ended up looking something like a mix of Buzzfeed and Murdoch propaganda.

Happy to see the idea is not dead and new companies are giving it a shot.

Knowing apple, its probably illegal for those 2 teams to talk to each other.

Great post! I find it interesting that all root servers are located in United States. Should some of them be elsewhere for redundancy?

There is a solarized version as well which I've used a few times in the past. https://thomasf.github.io/solarized-css

ASCII is English and limiting access to knowledge for the rest of humanity for a simpler encoding is just not an acceptable option. Someone needs to interpret those 7k words and write a (complicated?) program once so that billions can read in their own language? Sounds like an easy win to me.

Does Asian include Indians as well? Kind of amusing since Apple and Google are both lead by "asian" immigrant men.

You just described subreddits.

An Incremental Approach to Compiler Construction[1] by Abdulaziz Ghuloum.

The author presents a very approachable technique for building pedagogical compilers by starting with a tiny subset of the language - a language that can accept integers and print it and incrementally grows it into Scheme. Every step yields a fully working compiler for a progressively expanding subset of Scheme. Every compiler step produces real assembly code that can be assembled and executed directly by the hardware.

I've dabbled with compilers for a while now and in my experience I found this to be among the best ways to get people excited about compilers. There is some code available from Nada Amin[2] for the curious and I'm re implementing it from scratch again[3].

1. http://scheme2006.cs.uchicago.edu/11-ghuloum.pdf

2. https://github.com/namin/inc

3. https://github.com/jaseemabid/inc

RAFT is not BFT. You need nodes to cooperate. If the nodes lie, the system will collapse.

I did exactly the same last night and you don't need the echo $? hack anymore.

You read my mind :D

Just tinkering with the tools and writing some code helped me a lot more than the university course I had 6 years ago. There are several beginner friendly online resources now including

1. Write a scheme in 48hrs in Haskell

2. Kaleidoscope tutorial by LLVM developers

3. http://www.buildyourownlisp.com

4. http://createyourproglang.com

You are right, the compiler cannot handle much of higher order functions and closures yet. I have hinted how to do that with lambda lifting and closure conversion and I might get it working in the next few weeks. Maybe a part 2 for the blog post.

You are right and calling it quintessential might be too much. Local lexing seems interesting, but the approach I used is called combinatorial parsing and it does parsing and lexing in one go because they are so intertwined anyway. This also lets me get to the AST in just one pass over the input string with very little backtracking.

I'll update the post with this feedback.Thank you.

Author of the post here. AMA :)

Unless you have lived in the tropical humid heat, you wont be able to relate to this. Moving to NYC recently and living without an AC or even a fan feels so glorious. I bet 10% of my brain was constantly fighting the heat back when I was in south of India.

The only issue with the blog post is that most of those tools will be obsolete before you finish reading.

JavaScript as an ecosystem needs mature robust solutions rather than a new way to do things every other week.

Someone added all this into a goodreads list, so that you can mark them 'read later'.

https://www.goodreads.com/list/show/106375.YC_s_Winter_Readi...

For those who don't know, Andrew Wiles proved Fermat's last theorem.

Nokia? Really?

Click bait title?

Got there, and deleted all of it. ~10 years of search, browsing history and all other activity.

I feel good.

Refreshing to see something other than lorem ipsum.

Why they don't use SI even for scientific measurements?

I'm using latexmk right now. Thank you!

over http!