This is kind of what I already do with Claude which can employ a multitude of languages, libraries, and platforms. I write text files with detailed specs in English of what I want and Claude makes the plans which include testing regimes w datasets I have. Why do I need a less flexible tool for this?
When the IJ says it, they mean they have proof that they will stand behind of 14 examples. They decidedly aren't saying that it only happened 14 times.
It is a given that any power will be abused. However not giving power out is often worse that the abuse of power.
The real question is what do we do to detect and prevent that abuse so it is minimized. All too often people are "this person is mostly on my side so I will overlook their abuse" which is the wrong answer.
I agree but the combination giving power without doing anything to detect and prevent abuse in my opinion is worse than not giving power at all, in 100% of the situations - no exceptions. if 14 detected incidents here end up with 14 convictions and enough time in prison to deter anyone else from doing this ever again (5-10 years, per incident minimum), cool with me. it is no different than any other "law breaking" - people will people and law should be there to protect the citizens. but in our society it is obvious we cannot give power to people of authority cause whenever they abuse that power - there is either no law to charge them against or even if there is one they'd be immune to it
Yes. I don't know if this is exactly the recipe, but something akin to this could have .. no should have .. existed. Probably 1¢ is too much. Also, full public key encryption and digital signatures should be easily integrated by now as well. I know the whole trust problem ... yadda yadda ... I don't even read my email hardly at all anymore -- I want everyone that needs to get a hold of me don't rely on email.
I would be more likely to share this w others if the domain name didn't have an f-bomb in it. It doesn't bother me that much, but I really don't want to share it in certain circles...
Hey Wayne, I bought wheretheheckdidmytaxesgo.com and will make it live after work today. Sorry about the profanity! It’s just how I felt after seeing the stats firsthand :)
Anything new or special in jj that allows me to work with large binary files simply? To me, this is still unsolved in terms of providing an elegant solution (e.g. things like Git Large File Storage (Git LFS) are awkward).
I've heard that jj has support for non-git backends?
Can anyone comment on how difficult it would be to add support for another backend, any docs or examples?
I have a project[0] that does the large file thing well, but is missing most of the version control porcelain.
I've been looking for the path of least resistance to integrate it into something with a larger user base.
It looks like this treats files as blobs just like Git, and trees as single objects which fit in memory. Assuming that is a correct understanding, this core abstraction would need to change to handle large files and directories well.
All the well known version control systems do this though, and it simplifies the system significantly. It's the right model for source code, but it doesn't translate well to arbitrary data.
Yes, it will require work to do large files well. But there is general interest in upstream in having that, there's just nobody driving the work at the moment.
Folks talk about xv in the past tense. I still use it. On AWS it is still a great way for me to view images on headless ECS instances using an X11 server on my Mac. I still use on my local Linux boxes because it has image editing features I still can not find elsewhere.
reply