here is a random example to showcase how this can make sense (I'm not too familiar with the actual stacks in questions):
- stack A needs lots of tedious, not-quite boilerplate not-quite-copy-paste work whenever you implement something, but reduces cross-OS bugs, UX and accessibility issues down the line. Lots of dev frustration, slows down iteration (when humans actually have to do this).
- stack B has awesome DX and affords smooth operation of the design/UX/dev teams, very fast. More issues down the line, though. May be worth it if unaided humans need to work on it.
Though surely to say a system or process is 'retarded' means something is holding it back?
To equate this to a derogatory term for a learning disability (worthy of self-censorship!) is, frankly, bizarre and rather smacks of virtue signalling.
broadly speaking, it _is_ factually incorrect to say that. Censorship is the government controlling what information the public can access. No one on "the left" is trying to pass a law saying that people should get jail time for using the R-word.
Political correctness, woke/cancel culture, whatever you want to call it, is not censorship. And it's not splitting hairs to say this; words have meaning and though 'censorship' is particularly abused, it is still quite different from me looking down on someone who uses the R slur on X (as I do daily)
> Censorship is the government controlling what information the public can access
Wikipedia and the ACLU both use a more expansive definition, where your definition is only 1 type of censorship. The "Left" uses empathy to convince people to self-censor and less often uses "Cancel Culture" to pressure companies into private censorship.
There are more subtle forms of censorship, continuously employed by the government to prop up or push down various things. Covid had many such examples of pressure tactics from the government come to light but I'm sure it happens constantly.
For a specific recent example democrat-leaning states had much stricter and longer-lasting covid lockdowns - preventing free association is a form of censorship.
Google's business model is providing you services that are excellent, while also providing advertisers access to your willing eyeballs when you use those services.
Yes, the advertising targeting is incredibly invasive, but let's not pretend they aren't providing world class Search, Email, Docs, Maps, Video (YT), etc in exchange.
Not who you asked, but I was going to say Actions or CI/CD from when I tried out Gitea a few years ago (back when running a Jenkins instance was more normal) but looks like Gitea supports that kind of workflow now: https://about.gitea.com/products/runner/
Sure, but I would be incredibly shocked if the courts overturned these conclusions. These kinds of determinations are within the remit of the USCO, so a court does not need to come out and say it if the USCO has already done so. Obviously, as I said it would be better if congress weighed in and solved this problem, given that the USCO is free to publish a new NOI to change it's practices/policies, but we all know that congress is too gridlocked atm for that to happen
> Whether human contributions to AI-generated outputs are sufficient to constitute authorship must be analyzed on a case-by-case basis
It says a plain prompt is not enough but that is not the reality of real software development. People aren't one-shotting complex business apps. The vast majority of software development will trivially pass that bar and end up in the "requires case by case analysis".
I am trying really hard not to accuse you of not having read what you posted, because your conclusions are in strong tension with what it plainly says.
I've seen junior engineers be productive on their first day in the industry because of AI, so I don't think the article is the whole truth.
The example math is boundary-pushing and definitely not a solved problem. But most of us work on CRUD backends with a React frontend. Those are more or less solved problems that have well-documented solutions. For those kinds of tasks, LLMs just reward usage.
I can count on one hand the number of times in my career I've needed to solve a problem that's not described on Stack Overflow.
Again: this is NYC’s official website. It might (as a stretch) be a “lie by omission” on a national newspaper’s website, but this is a website that is solely dedicated to NYC itself.
Now I'm being super pedantic, but every town can't have the same "landmark" law. What makes a law a "landmark" is that other municipalities look to it for direction.
In a world where the California law exists, and the New York Times has been used as an example of the success of that law for years already, claiming some sort of moral victory with the "landmark" qualifier is objectively wrong.
Does any of this matter? No, but I like arguing about it.
If you want to be pedantic, NYC is a different “land” to have a “landmark” for :-)
(I like arguing too. Nothing wrong with that. I think in this case it suffices that they’re regulations in different states with relatively different political histories, even if the political valence of the two is somewhat similar. I would agree if this was a “landmark” change for Irvine, CA.)
The term MMO is about the game/server architecture more than the size of the game. MMOs are online games with a single (or sharded) persistent gamestate. That's it.
Most shooters have rounds that restart, breaking the persistence quality of the game. Other games like Minecraft emphasize individual / private servers and break the "single gamestate" proposition. The "Massively" word refers to that
single gamestate that many users can interact with, not how many do actually play.
To me, The "play offline" option is more against the MMO definition than the actual number of players.
If React Native worked well for human programmers, wouldn't it be just as good for AI?
reply