4,035 karma · joined May 20, 2019
But with a worse UX?
GitHub is the de facto standard.
It's the best time.
I don't think that's a bad thing, or that it's necessarily plagiarism - unless the LLM spews out the other project's code from its training...
I'm happy to see multiple takes on the same idea. There are lots of tiny aesthetic and functional decisions that make apps different from one another. Now that implementation is cheaper we should celebrate that.
I'm sure there are scenarios where the cop can confiscate the surfboard and the car. The distinction is probably somewhat vague even for highly educated lawyers, and cops cannot expected to be that.
He should have stood up for his rights, sure, but laughing in the cop's face and telling them they're full of shit is disrespectful, and at least where I live is a misdemeanor even if the original case is wrong.
There's nothing shady here. The disclosure is front and center on his About page on his website.
He's not spamming you. It's one short link, sometimes a link to a first-impressions post. It's interesting and useful for me and the other commenters who keep upvoting his comments. Why are you so antagonistic?
It's a decent heuristic because the better models generate better pelicans. That's all. Nobody sane is going to make a bet on a model based on a pelican. But it's cool, it's tradition by now, and it's a semblance of a good first impression for new models.
I feel like doctors and physiology researchers have known this for some time.
There's a pretty good reason for that - the base assumption is that training in fundamentals, methods and ways of thinking is something you won't get anywhere else.
You are paying for the extra power draw.
I don't - I did large scale web, embedded, data, and security, but no graphics or games. I wouldn't know where to begin.
At the very least, he photographed and built models of logs and his own yard.
Who signed up for what?
There are many scenarios, especially in embedded systems, where it can happen and you want to handle it robustly, e.g. by evicting a cache or flushing a buffer to disk.