TFA mentions 20-year contracts between Del Monte and farmers. That seems to have worked so well that we have too many peach trees. Like, to me the present situation itself should assuage your fears. Are you thinking another processor/distributor won’t come along in the future with long-term contracts? Where will they get their peaches?
> Are you thinking another processor/distributor won’t come along in the future with long-term contracts?
That's exactly what I'm thinking. There are few crops where someone might want to lock in a 20 year contract. It's a major gamble for all involved. It's a gamble for the distributor because tastes might shift in 20 years (almost certainly a big part of why Del Monte went bankrupt) and it's a risk for the farmer because it's not clear that another distributor will look at these farms and think "You know what, I can pick up where that company went bankrupt".
> Where will they get their peaches?
Will they get peaches? That's really the question. They might just decide it's too unpopular and the price would have to be too high to support selling peaches.
Del Monte was a big reason why peaches are available. Similar to how Dole is a big reason we have bananas year round. If Dole goes bankrupt, we likely won't see bananas on the shelves. And we know this because there's more than just 1 variety of banana in the world. We have access to only 1 because there's only one distributor of bananas in the US.
We are moving into an era of private equity doing fast turn around profits on everything. The old way of business thinking that you can have a 20 year contract is likely dying. 1 year contracts are going to be much more likely because that's where a lot of the investment is going. And Del Monte is the poster child for why a business would shy away from doing a 20 year contract.
2. things where it otherwise would get stuck iterating on hacky workarounds doomed to fail
“Reverse engineer this app/site so we can do $common_task in one click”, “by the way, I’m logged in to $developer_portal, so try @Browser Use if you’re stuck”, etc.
I just had Codex pull user flows out of a site I’m working on and organize them on a single page. It found 116. I went in and annotated where I wanted changes, and now it’s crunching away fixing them all. Then it’ll give me an updated contact sheet and I can do a second pass.
I’d never do this sort of quality pass manually and instead would’ve just fixed issues as they came up, but this just runs in the background and requires 15 minutes of my time for a lot of polish.
I guess the problem I see here is that if the use case is "things I otherwise wouldn't bother doing", that's fine, but it's pretty niche. I dunno, if you're talking about a human "Agent" (like say in sports or entertainment), they'd be a trusted person to handle business matters outside of your competency (contract negotiations, etc.). I don't see AI "agents" being at all like that, they're more like an intern you need to supervise constantly.
The law has a lot more stuff. I wonder what this part is all about:
> if a person suffers damages from a minor committing the same offense repeatedly on school grounds … the person may bring a cause of action against a parent or guardian with legal custody of the minor to recover costs and damages caused by the repeated offense … the court may waive part or all of the parent's or guardian's liability for costs or damages if the court finds … that the parent or guardian reported the minor's wrongful conduct to law enforcement after the parent or guardian knew of the minor's wrongful conduct.
And of course
> A person may not bring a cause of action against the state, an agency of the state, or a contracted provider of an agency of the state, under this section
Hah, I tried when BA had to cancel my flight due to a computer system outage. Coincidentally, some “activists” handcuffed themselves to a fence on the runway at the exact same time, which was an act of terror or whatever and thus not covered, so I did not receive my money back.
I think especially given TFA and our inferred history with them that they were terrifying apex predators who occasionally raped human women.
I don’t much believe the friendly smiling museum depictions that have lately become fashionable. Their eyes alone would have made them something you didn’t want to run into at night.
And lets not forget that all hominins fight amongst themselves, rape each other, etc... The assumption that Neanderthals were particularly brutish is just that, an assumption.
> According to Svante Pääbo, it is not clear that modern humans were socially dominant over Neanderthals, which may explain why the interbreeding occurred primarily between Neanderthal males and modern human females.
Unless read as suggesting "Neanderthal males were hugely charismatic"?
Are there any good illustrations showing how much bigger their eyes were compared to modern humans? Is it really significant? I'm having trouble finding anything that makes it clear.
Joined because I loved yc, sv, and it’s my home. There’s a guy running around my neighborhood beating people with a pipe. I hope something like Flock can deal with it. I don’t know why people get on here and post agitprop.
I’ve been told explicitly to do what GP said, so it’s perhaps becoming word-of-mouth career advice at this point. In my case it told a different career story that is maybe more easily digestible.
OSS has gone off the rails recently. There’s a project under the Apache Software Foundation—I forget which—that is essentially a byproduct of the operations of a Chinese beverage company. That’s more like what I remember.
We’re talking about code that users can modify themselves to solve their own problems. That’s it. I don’t need to hear about the struggle.
> We're talking about code that users can modify themselves to solve their own problems. That's it. I don't need to hear about the struggle.
That's exactly the kind of attitude that this discusses.
You create something that solves your problems, you put it up on GitHub, free, and open... Suddenly it turns out others have the same problems you did, your software solves them.
It starts ok. People are nice. But as it gains traction, a certain kind of toxic person becomes more and more common. The "YOU FIX IT NOW! I DONT KNOW" Kind of person.
You wake in the morning, look at your email, and it's a stream of being screamed at. That takes a toll.
All because you had an idea one time to build something that solved your problem you thought "hey I might just open source this".
> That's it. I don't need to hear about the struggle.
Let me tell you a solution for the "FIX IT NOW" types:
> This is an Open Source project that gets developed at the author's discretion. We provide paid work services for urgent fixes, cost is $500 per day with a minimum of 4 days.
Put that in the README, under a header that can be linked to in bug reports from entitled people. Worst thing that could happen is that the maintainer ends up earning a couple grand.
Is this written down anywhere? All I can find is an announcement from the group and a follow-up message threatening Canonical if they do not negotiate.
What does a DDoS accomplish if the contracts are signed and a team embedded?
Why take down security.ubuntu.com? Surely even cyber jihadis need security updates?
reply