On the contrary, I would say this is increasingly unusual nowadays. There are print restrictions on e.g. iStock content, but there's no attempt to "ration" the number of visitors that see a stock photo at a specific price point.
It's something that's generally put me off from licensing paid fonts - despite the work that has gone into them, because you're almost signing a blank cheque and it's not easy to know how many visitors are scraping content for LLMs.
Obviously not. Your strawman aside, I’m also not defending Nassau County ordinances either; just highlighting the context that was getting overlooked in the prior comments to this post.
With web, at small scale (which honestly is 95% of the world), you just version and back up everything. We push updates that break stuff from time to time. If it's bad enough, we just hit a button and roll back the change. The nerves are basically a sign that you need to have an easy rollback process in place, once you have it, you sleep easy and things are fun.
Clearly that's how they ended up with the current team. They hired for culture fit. Anyone who worries too much is out.
You bet they have an amazing perfect top-notch hiring pipeline, many rounds of interviews, and whatever you could wish for! (No, no ... the subcontractors writing code are not in scope for this, duh.)
For the aliens, the right image has much more realistic gradation. The one on the right looks like the grays have been crushed out of it. There's also a funky glow coming from the right edge of the alien.
I'd say the blur effects on the left images are much cleaner as well. There are some weird artifacts at the fringes of objects in the earlier version.
I feel like you could strip down a UI, stick a language model on a help menu and you'd be most of the way there with this already.
I have a minor hesitation here. The user inputs an endpoint, and the program is then supposed to connect a user with the tool to complete it. Solutions often have different ways of being reached with tradeoffs associated with each method.
Also, I wouldn't underestimate the ways in which, for some types of workers, the affordances of tools are part of the creative process. There's a way in which a product will be less thought through when the journey from conception to completion is cut short.
Amusingly, for a long time, emacs has effectively been this, but with a fuzzy search tool. Very common to just bring up the command minibar and start typing words looking for relevant things.
Going back, many old machines were like this. They all had some form of "apropos" command that we seem to have completely forgotten about as things got bigger. Indeed, the idea of man pages and the like seemed to get skipped out on with dos, such that windows also didn't really have it ingrained heavily. The docs were almost certainly there, but they were often specific in formatting to each program? (Or is my memory just off?)
I don't necessarily disagree, but I think there's another way of seeing this here that goes: if some of your time is already accounted for by certain tasks, trying to regiment them out further ends up reinforcing the idea that you're losing time constantly. Scheduling out personal time in the same manner as working time pushes you to think about them in relative terms.
As a disclaimer, this is something I go back and forth on and I do tend to use time blocking myself because otherwise I find it hard to maintain direction over long periods of time.
I think what's missing from this is the ROI calculation. They see AI as having degraded quality compared to human authors, but the difference in quality doesn't produce enough profit to offset the cost of hiring a human staff.
