It's not so much that we will prevent individuals from using the product, we are just focusing feature development on the needs of companies and teams. Startups are hard, and you have to focus, and so that's where we are focusing first.
Will you prevent individuals from using the product by requiring a sales call for onboarding? (aka: decisions that have nothing to do with individuals at all, but merely rule them out by intrinsically not being something they can achieve)
As we initially roll out we will be doing that, yes. The reason is that our initial offering is enterprise shaped, and so won't have a self-service onboarding. Eventually we will not require the white gloves, but you have to start somewhere.
I don't know how experienced you are with jj, but one thing I can say for sure is jj offers significant ux improvements over git and they plan to have a backend eventually. we might see the first implementation from ersc. and from their website I see they are already taking things like agents into account from day one. so we might be in the verge of getting something that scales better with modern day workload?
I like to compare Google and jj to Mozilla and Rust: Google employed Martin and some other maintainers, but it's always been an OSS project under the Apache 2.0 license.
That being said, there's a few things that lead to this perception: the first is that it used to be under Google's GitHub account, but is now under its own org. The second is that contributing to jj does require signing Google's CLA. That is something that is desired to change, but that's up to Google. Due to the license, the community could fork it, and still have the rights to use the code, but that would be pretty aggressive, and so everyone involved would rather work together on this than do so. The move to its own GitHub org was one example of movement in that direction, but I'm not aware of an actual timeline to remove the CLA just yet. The project will figure it out over time.
(I have a commit bit but am not a jj maintainer, so the above is my own impression from being involved in the community for the past few years.)
I like to say AI is like the super soldier serum from the MCU. Teams take it and either become Captain America or Red Skull, it depends on what you were to begin with.
I wish. The "captain Americas" are more like Tony Stark's jury rigged suit used in the desert (for now). It's not the suit truly doing innovation, it's the man inside who knows the suit (and its many limitations/flaws) inside out. Using the strengths long enough to escape before the hunk of metal inevitably fell apart.
Huge moment for the people behind duckdb. I've been using duckdb since the days of its preview releases and I knew they were gonna make it big. So, this one is well deserved. I hope duckdb's governance continues to stay under duckdb foundation.
These days all I see is, people on the sending side produce huge amount of AI generated text with zero understanding and the people on the recieveing side feed that same text into some other (or perhaps same) AI to scavenge meaning from it. And they do this so much so, that I some time wonder, if we could invent a high density wire/binary format for AI outputs and enable direct agent to agent communication to save some energy and bandwidth.
AI is just a good permutation/combination engine that tries to act smart with help of statistics. At best I only see AI as, 1. An autocomplete on steroid, 2. Good search/correlation engine
reply