I think 3? I feel like that's often enough. Sometimes it's nice to do a quick dumb ass gag on a whim. If I am anything I am a man who loves a dumb ass gag.
Can't agree more. I was skeptical that Kagi could be that much better. I felt a little silly paying for a service that had always been free. After using it for a week I can't imagine going back.
Too many times I used to google my vet by name and the response would be some random other vet in next town over. I'd end up calling them and immediately hang up realizing google fed me bullshit again.
Kagi just focusing on a doing a good job. It's their singular focus and its worth ever cent.
That's a minor nitpick that probably worth making in this context. People often casually use free and open interchangeably, like the the person I responded to did. There are times when it does have a real semantic difference in meaning... but here? Not really. The thread is even about a free software project.
I agree with the rest of what you say. Politics, governance and identity are unavoidable in any kind of community. It's just part of it and unavoidable. It's about dealing with it fairly, clearly and with respect.
Oh my God. That's so exciting. I did a prototype a while back for writing UDFs in WASM for a query engine. The fact that everything needed to be copied in and out of the environment killed it. Excited to try it again if/when this lands
Not always. The calculations take its useful life expectancy as an input. If they estimate it correctly you have highly likelihood of it breaking, burning out or being woefully out of date by the end. At the 10 year window you are looking at losing support for security updates.
So if you are lucky you might end up with something that still runs but most folks won't find it particularly useful
GitHub has been basically the default for free public git hosting for a long time. I was curious what bitbucket has and it looks like the free tier is so limited, I can't imagine a lot of people hosting vibe coded open source there.
> It also contains LLM dishonesties like that the bundle size is KB
That one jumped out to me too. The phrasing is so wiggly but technically correct it feels intentional. When I saw it I didn't blame it on the LLM, which is worse.
It's pretty common if you have IT and finance teams that are paying attention. Sure a lot of shops let them waste away on a shelf, but that's what it is, waste. If you have fungible inventory that isn't likely to get used soon it is just a mistake it let it sit around unutilized. If it is cash, it is easier to utilize on other projects.
Except it's not counter to history for SaaS services. Many will ban unauthentic usage from non-human clients. Getting banned from a SaaS service for boting is nothing new
Enron had a system like this. They regularly worked on large, long term contracts that became profitable over years/decades. They wanted to push rewards forward so would estimate the total value of the contract and book the profit when it closed. Mark-to-market accounting wasn't unheard of the time but using it for assets without an active market was unique. Without the market to make against, the numbers were best guess projections.
The problem is everyone along the line is incentivized to be aggressive with estimate (commissions for sales are bigger, public financials looks better) and discouraged from correcting the estimates when they go wrong.
Estimating multi-year returns on frontier models looks harder than estimating returns on oil and gas projects in the 90s.
NYT recently did a fantastic calculator. It isn't simple flat one or the other is cheaper. It takes into account buy vs lease, milage, local energy cost, length of ownership etc
It isn't 1:1 since there probably won't be ansible provided configs, but I find writing nix devshells per project to be low effort and high reward. It'll only be a couple lines if all you need is a specific version of ansible