willow8349

This doesn’t really detract from my point - the “best” tool tool would use knowledge of python for python files, json for json files, and so forth. I think you’re just saying you’d want multiple of these rolled in a single tool as opposed to standalone, which is fair. I think any tool would have to be compatible with git /layer on top of it so it’s available as a fallback

I think part of the problem is it seems everyone is trying to make a version control tool that is agnostic to all languages. Both computationally and UI wise. But C++ users expect to see different things than JavaScript users and so forth.

I’m surprised at the lack of hyper-specific language version control tools. I thought about making a side project for one in Julia a while back but not quite sure how it would look. Some random thoughts:

- info on type, name, constant changes

- let me checkout older revisions of individual functions / objects / whatever

- on unit test result changes for functions that have unit tests

- when changes are simply a refactor and are functionally the same

Look at the power draw of the human brains versus any of the hardware running these models. It’s an order of magnitude difference. Often multiple orders of magnitude.

Part of the reason is a massive focus on GPUs and digital techniques. Some things like math operations are quite fast and accurate to do in a discrete sense when that matters.

The human brain is not discrete though. Nor is it really fully analog.

Specialized hardware beyond GPUs for parallel digital calculations will likely be needed to implement architectures that get actually closer to human levels of intelligence.