dsauerbrun

what is react responsible for? If you're referring to the explosion of SPAs, I think you should direct your blame to angularjs... React was just a better version of that revolution.

out of curiosity, how or what do you use codex/claude code for that beats opencode?

Am I going to have to find a shabbos goy to unblock my swarm? They already don't like when I ask them to turn on my lights.

That's a pretty narrow viewpoint. I could see many examples where it's better to work than focus on your kids... At least for society. Leader of a country comes to mind as one of those jobs

If you think about this in terms of systems... it's unsustainable. You'll eventually get to a point where the damage you've done requires a flow of wealth/energy that cannot be generated for everyone.

I'm assuming that we can drive our environment to that kind of state, maybe there's an upper limit on how bad the environment can get. I'm not a climate scientist and don't have the curiosity to look into if there's a limit to climate change.

They have the data but I wouldn't trust their analysis of it unless they release all the raw data which would be to the benefit of their competitors.

I'll give it a go next time! ty!

Yeah it's not scary but it can be frustrating...

Imagine bushwhacking your way through a bunch of conflicts while rebasing on main... Now you realized that you needed to do some other work before your pr is ready for review... Now you need to rebase on main again and get to relive conflict hell again.

Maybe I'm one of the stupid incompetent people referred to in this post but I haven't figured out a way to deal with the having to solve the same merge conflicts when I rebase again :(

Well that explains where my sessions went on my side project that I came back to after a few months... Thought I was going crazy

And here I am pooping out simple typescript... These articles always make me feel like I'm wasting my talents working on products that don't really have the need to leverage any understanding of what's happening under the hood at the CPU instructions level.

Hmm, if the caching layer doesn't change(I assume it was optimized for olap style queries), and the new parquet format is better for olap... I'm still not understanding how it performs well for oltp reads.

I'll give the article another read... Maybe I missed something. Thank you for the response! Really nice to be able to get info straight from people who work on the product

Maybe I'm too stupid to understand the article... How does this achieve performant querying for olap and oltp purposes?

Based on my understanding, olap queries will go to the parquet files which are stored in a columnar fashion and oltp style queries will go to a caching layer that sits on top of those parquet files?

What's the special sauce here? Seems like they're just caching the data which, for all intents and purposes, seems like the same solution of storing another copy of the data which is what they say they're avoiding.