1saadcodes

I really like the idea of someone building a GitHub alternative, but these are some horrid terms hahaha

If you're asking people to build something as ambitious as a GitHub replacement, $25k of your own infrastructure credits isn't really the same thing as paying someone $25k

It's nice that the tool is open source tool. You can actually see what it's doing and not end up downloading something sketchy

What worries me is that Apple might to be heading in a bit of a bloatware direction with this stuff. Having to give up tens of GB of storage for an AI model that I may not even use feels pretty far from the old Apple approach of keeping the OS lean

I'm surprised by the crazy pace at which these models have been coming out over the past few weeks. The cheaper cache here is really nice, but I think it depends entirely on your workflow. If you're constantly compacting or burning through your context, you're probably going to have a bad experience regardless of which model you're using

The irony is that search used to give you the sources and let you decide. Now we're getting an answer first and have to verify it ourselves

The technology isn't anything new but, it's the context that makes it so uncomfortable.

People have very different "expectations" of privacy when they're having a conversation with an AI VS when they're browsing something like Facebook

Not to mention Facebook is free whereas you pay for a GPT subscription

I think the problem is less "AI agents are ruining the internet" and more that nobody wants to receive a thousand automated requests from other people's agents. The internet was already full of spam, this just makes it cheap to produce a lot more of it

The 370 years thing is doing a lot of work in the headline imo. If people had already figured out it was probably a book cipher, this is impressive, but it's not quite the same as solving something that hundreds of experts had been actively working on

I'm struggling to see the upside of replacing working coreutils when the replacement still has bugs that the old implementation doesn't. Rust being safer is nice, but that doesn't help much if the new rm segfaults