A bit too broad to give a specific answer from my side.

Overall, I prefer web based over apps, because I can CSS hack and if necessary JS hack them.

Web also means it doesn’t litter my PC or mobile phone or tablet. And that it can’t fetch more data than it needs or I want it to have access to.

Bad software is bad software, no matter if it’s installed or on the web.

The git compatibility is necessary for adoption and connected use.

jj does significantly reduce the work interface, but the git compatibility increases complexity again.

I tried it out a little bit a few days ago, and found it interesting. But given my git knowledge and tooling, I can’t reasonably switch. First, I would miss my TortoiseGit Log view (entrypoint to everything). But also, the connection between jj and git seems complex and potentially error prone.

As a fresh and independent tool I can definitely see how it’s much easier and better, especially for people not familiar with Git.

from some time ago

It’s a fair statement and personal experience, but a question is, does this change with tool changes and user experience? Which makes studies like OP important.

Your >95% garbage claim may very well be an isolated issue due to tech or lib or llm usage patters or whatnot. And it may change over time, with different models or tooling.

It’s not a duplicate URL. You posted an image, they posted a link to the study.

I mainly wanted to give the additional context and discussion, more so than say “has already posted”.

I assume I must have compared a modified date or sth, dunno. Misled by it being shown further down in my feed.

(minutes) earlier post linking the study

So many words…

to

oh god please no

wth is all that coloring [in the design samples]

Stop allowing full unfettered access

There’s a decline button. At least privacy settings don’t repeatedly come up again (what this post is about).

Better flood them with interested users than ask for thumbs up on a ticket.

We want to move down to the next line (line feed) but also to the beginning of that line (carriage return) after all.

Unless you open it in Excel. In which case bad things will happen no matter what you have in the CSV…

They bought Java (not javascript)

They bought Sun, which “owned” Java and JavaScript.

The trademark was originally issued to Sun Microsystems on 6 May 1997, and was transferred to Oracle when they acquired Sun in 2009.

https://en.wikipedia.org/wiki/JavaScript#Trademark

A Python-specific question is better suited to the !python@programming.dev community instead of the general programming one.

I’ll use a gif with each frame being a different country flag. Then I can access them by frame index.

The link is broken. Looks like code was accidentally pasted there.

https://lukasatkinson.de/2025/net-negative-cursor/%20%20%20%20let%20mut%20bytes%20=%20vec![0u8;%20len%20as%20usize];%20%20%20%20buf.read_exact(&mut%20bytes)?%3B++++++++%2F%2F+Sanitize+control+characters+++++let+sanitized_bytes%3A+Vec%3Cu8%3E+=+bytes.into_iter%28%29+++++++++.filter%28%7C&b%7C+b+%3E=+32+%7C%7C+b+%3D%3D+9+%7C%7C+b+%3D%3D+10+%7C%7C+b+%3D%3D+13%29+%2F%2F+Allow+space%2C+tab%2C+newline%2C+carriage+return++++.collect%28%29%3B

404 Page Not Found
The page you have requested does not exist. Would you like to visit the start page?

Cleaned up link: https://lukasatkinson.de/2025/net-negative-cursor/

Marketing-speak, not saying much at all. Not even a hint in what they “discovered”, what they plan to change, or plan to do. No acknowledgement of previous issues, making me doubt the “working with the incredible global community” as pure marketing-speak.

I also want locally deleted files to be deleted on the server.

Sometimes I even move files around (I believe in directory structure) and again, git deals with this perfectly. If it weren’t for the lossless-to-lossy caveat.

It would be perfect if my script could recognize that just like git does, instead of deleting and reuploading the same file to a different location.

If you were to use Git, deleted files get deleted in the working copy, but not in history. It’s still there, taking up disk space, although no transmission.

I’d look at existing backup and file sync solutions. They may have what you want.

For an implementation, I would work with an index. If you store paths + file size + content checksum you can match files under different paths. If you compare local index and remote you could identify file moves and do the move on the remote site too.

Your git repo might get very big after some time. Especially if you move files.

Moving files does not noticeably increase git repo size. The files are stored as blob objects. Changing their path does not duplicate them.

Can you be more specific? What in what they present is bad use of AI?

What makes you think anyone blindly trusted it?

They pointed out how it was almost correct, and the two places they had to correct. Obviously, they verified it.

There and at other times, they talked about similar approaches of generating a starting point rather than “blindly trusting” or anything like that.