Hacker Newsnew | past | comments | ask | show | jobs | submit | stubish's commentslogin

While glyphosate may technically be considered safe, there are reports and I believe lawsuits about it reacting with hard water creating extremely unsafe compounds. ie. it poisons your ground water.

https://www.worldenergydata.org/roundup-herbicide-ingredient...


I'm not opposed to further studies, but basic critical thinking makes it unlikely that this is a danger outside of those specific areas.

First remember that glyphosate has been used around the world continuously for 52 years. If there is some kind of pattern of harm due to its use, it's already happened, so it should be possible to find those harms all over the place.

85% of the USA has hard water. If glyphosate being in hard water causes 10% of children to have early onset kidney disease, we would have been seeing that in the USA for at least the last 42 years. But we haven't. So it's likely that whatever is happening in Sri Lanka, is specific to Sri Lanka.

You can take this same basic logical premise and apply it to all of the concerns about glyphosate. None of them stand up to scrutiny, because we have been using it for so long, everywhere, and despite that, we have no concrete evidence of any significant harms caused by glyphosate itself.


And real farmers have bad days and have difficulty maintaining the prescribed application conditions.

For one, you can't control what the weather does in the afternoon after you've applied it in the morning (and it might take all morning because farms are huge and you have to tank up again)


Real farmers, all 3,500 of them in local coop, take careful measures to control everything on large farms- spraying is generaly done at night for the cooler temps, rates are watched as over spray costs $$'s etc. Seed volumes are manually run through air seeder calibrate seed weight per acre, etc.

The trend today is toward AgBot / SwarmBot type boom sprayers with onboard weather stations for wind speed and air temp, coupled with computer vision to limit spray to actual weeds rather than broad area even spray for weed / non weed alike.

Again, driven by $$ watching, etc.


Insider bets distort the probabilities, creating a conflict of interest and causing market manipulation. We don't let athletes bet on their own games, because some will deliberately lose. They will do this when the odds are good and they will make more money. So you don't get accurate predictions, because the more probable something is, the better the odds and the more money to be made by someone manipulating the odds.

End result is you place bets against things you want to happen. eg. USA invading Iran. If you win the bet, you make money. If you lose the bet, you still win because the USA invaded Iran. And maybe that happened because people in power took your bet and influenced the odds in their favor. A fully deniable market for bribes. Same reason you can't bet on unnatural death, because it crowdsources assassination.


Also dementia

It would be interesting to know if the problems simply moved elsewhere. Why pay to vandalize when you can vandalize somewhere else for free?

It will need to be very, very different from the book unless they go retro-futurist. Like Foundation, as they mentioned.

I hope it fairs better than Gibson's other adaption, The Peripheral. Like many things I liked, cancelled after one season.


We should be more worried about who placed the losing bets then. Russia, Israel and China having a market for government and military officials to accept their bribes is kind of a bigger story than insiders fleecing gamblers.

A bet against an event is win/win if you want that event to occur. If you are a country that wanted the US to strike Iran, placing a large number of bets that they won't either gets you what you want or earns you money. It is one reason why you can't bet on someone being murdered, as it creates a deniable market to crowd source assassination. Strange that you can crowd source war, but not assassination.

Not sure how you can say that about upstart. It was pretty much the accepted successor to shell scripts for an init system, for a few years until Redhat started pushing systemd. You would probably be using it now if Debian hadn't gone with the Redhat systemd over OpenRC and upstart.


Similarly upstart, from 2006, widely deployed before Redhat brought in systemd. And got dropped when Debian decided to go with systemd. Surprising how this gets misremembered given the hate systemd initially received.


I remember it well. At least Canonical also jumped on the systemd bandwagon when upstream (Debian) made a choice, instead of dragging upstart on, like it has done with countless other projects that are past their time (juju looking at you)


People also forget or don't realize that before systemd Redhat shipped and supported upstart in RHEL too.


https://www.rusi.org/explore-our-research/publications/comme... goes into a lot more detail on many more of the munitions and the supply and manufacturing chains.


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: