Contracts aren't for handling errors. That blog post is extremely out of date, and doesn't reflect the current state of contracts
Modern C++ contracts are being sold as being purely for debugging. You can't rely on contracts like an assert to catch problems, which is an intentional part of the design of contracts
I definitely get this. The thing that gives me hope is that you only need to poison a very small % of content to damage AI models pretty significantly. It helps combat the mass scraping, because a significant chunk of the data they get will be useless, and its very difficult to filter it by hand
The asymmetry is what makes this very interesting. The cost to inject poison is basically zero for the site owner, but the cost to detect and filter it at scale is significant for the scraper. That math gets a lot worse for them as more sites adopt it. It doesn't solve the problem, but it changes the economics.
I'm not sure why the other reply here was flagged and killed. The US absolutely has NOT acknowledged that they killed school children. The DoW and other government officials have only publicly stated that an investigation is taking place.
This is incorrect. The US government (via Secretary Hegseth) has only confirmed that they are investigating the incident.
What the US has NOT confirmed:
- that they are responsible for the bombing
- who hit the school
- whether the school was an intended target of US strikes
- whether it was struck intentionally
- that it was mistaken for a military site
- any casualty count
- whether there were civilians or children in the casualty count
The US has explicitly DENIED:
- That they deliberately target civilian targets
These are the facts about what the US has actually confirmed. We are all entitled to our opinion of what happened. But we should be able to acknowledge that they are just that: opinions. We don't actually know what happened. And I find it scary and dangerous that so many people, on hacker news and elsewhere, are acting like they do.
Its always extremely funny reading wikipedia articles about a countries customs. For the UK:
>Bread is always served and can be placed on the table cloth itself
This is extremely rare, to the point where I can't remember the last time I saw it. Is bread really.. always served?
> In the United Kingdom, the fork tines face upward while sitting on the table.
Tines down isn't uncommon in the UK either
>if a knife is not needed – such as when eating pasta – the fork can be held in the right hand
I mean it can be, but its fairly uncommon
>it is permissible to place a small piece of bread at the end of the fork for dipping
Its also 100% fine to dip bread in a sauce with your fingers. Putting bread on a fork if you've licked the fork and then dipping the bread would cause everyone to hate you, so *don't do this*
At any kind of formal dining? Yes, absolutely, I would expect there to be a bread roll & a pat of butter served at the beginning of the meal. Both in restaurants & formal dinners in my experience.
It's not an absolute rule though & you generally wouldn't expect bread to be served like this at home in the UK. I think the French are more likely to serve bread at home as well.
> >if a knife is not needed – such as when eating pasta – the fork can be held in the right hand
> I mean it can be, but its fairly uncommon
So the norm is that if you're eating one-handed, you use your non-dominant hand? That seems really counterintuitive to me; is it because you're so used to having the fork in the non-dominant hand that it feels awkward the other way? Which hand do you use when eating with a spoon?
Spoons always go in the right hand (eg fork and spoon), but yes I'd say people usually use the fork in the non dominant hand. Fork in the right hand is slightly 'uncouth', possibly due to its american associations
Far too many people treat AI as a way to launder copyright, it seems likely that a lot of the current state of outright plagiarism won't stand up in court
These cases will be settled out of court long before they ever reach a jury. Anthropic has agreed to pay $1.5bn in a class action suit [0]. Others will follow.
Eh, that's a bit of bullshit; I've seen floss Mario/Puzzle Bubble/Pang and such since forever and no one was sued.
Heck, back in the day Rogue was propietary and commercial (and thanks to that we got both the roguelike genre and the Curses library) and yet Hack was born as a libre clone and from Hack we got the now uber known Nethack and forks like Slashem.
Cloning commercial games it's older than Windows 95 itself and probably as old as the NES.
The https://osgameclones.com has so many examples that you whole point gets invalidated since the first Hack release for Unix. And Tetris for Terminals, MSDOS and the like.
Hell, in the 90's everyone in Europe (children of blue collar workers) got a Russian Tetris clone -oh the irony- called Brick Game with often several micro low-res commercial game clones such as for Frogger and Battle Tank. No one sued that company ever, even if the Tetris concept itself was for sure patented and copyrighted.
And that game was probably sold by millions, maybe even more than the Game Boy if we count every clone sold with different plastic cases, because you could get one for the price of a book and today for less than a fast food ration.
At the same time, the open source community has absolutely no responsibility to make Atari profits here either. The outcome here is simply that open source is getting screwed over
It isn't kind hearted. Them trying to shut down openttd would lead to a gigantic clusterfuck that would hurt their sales. This is them trying to remove a direct competitor to them releasing a new game as much as possible, without generating community backlash - to maximise profits
It may have been "screwed over" if there was no access to the oss game. But you can still download the game from their website. They just do not want that these appear as competitors in steam/gog platforms, so they bundled the oss version. Both sides thought this was a reasonable resolution. Thus I don't see "screwing over" here.
Open source is a culture that includes its users. Open source is getting screwed over because at the first whiff of a capitalist losing a buck open source retreated and hid.
The game is still distributed freely through the internet, only restricted within the main commercial platforms. I think that commercial platforms and "open source culture" will sometimes inevitably clash. Open source culture requires de fact non-reliance on such platforms anyway.
It took a long time for python 3 to add the necessary backwards compatibility features to allow people to switch over. Once they did it was fine, but it was a massive fuck up until then. The migration took far longer than it should have done
Its widely regarded as a disaster for good reason, that forced some corrections in python to fix it. Just because its fine now, does not mean it was always fine
Fibers are primarily when you have a problem which is easily expressible as thread-per-unit-of-work, but you want N > large. They can be useful for eg a job system as well, and in that case the primary advantage is the extremely low context switch time, as well as the manual yielding
There are lots of problems where I wouldn't recommend fibers though
Modern C++ contracts are being sold as being purely for debugging. You can't rely on contracts like an assert to catch problems, which is an intentional part of the design of contracts
reply