Obviously not. You know how you can tell? Police will stop you from doing it.
I walked into a paint store recently and there was some genuinely interesting music playing on the PA. It was some sort of spanish-language 80s new wave I'd never heard before. It had a nice groove. I asked the guy at the counter about it and I was genuinely surprised to find out it was AI.
So... was it as good as great music? No. But it beat the hell out of muzak. And it was genuinely novel in a way that pop music isn't. I will sacrifice a lot of pride for novelty.
Matt Levine has gone into great detail about the legal chicanery that brought us here, but it summarizes as "it's not gambling, it's futures trading".
This seems like nonsense to you and me (and Matt Levine), but our opinions are irrelevant here. The courts' opinions are, and so far they've been coming down on the side of the prediction markets. Mostly.
So by definition - as weird as it is - it's legal. So far.
As long as the business is legal to operate, there is no justification for criminally prosecuting the people engaged in that business.
This is a bad take. What they are doing is quite obviously legal right now. Federal law trumps state law and the feds have an opinion, despite being weird and controversial.
There are a number of ongoing legal battles about the federal laws but until they work their way through the courts, it's "legal". Also, it could all get resolved with a new presidential administration in two years. This is the correct solution.
We shouldn't cheer for personal prosecutions over definitionally legal activity. Nothing good will come of it. See also: Sending mifepristone across state lines, or traveling out of state for abortions.
When I'm working on my own, I scrutinize every line of backend code and frequently send the LLM back for rework. Frontend code I keep an eye on just to make sure the LLM isn't getting stupid (which it occasionally does, even at the frontier), but mostly defer. The CSS I don't even look at.
This isn't too different from having employees. How much do I review other people's work? Depends on the employee, depends on how critical the work is.
We built up all these UI conventions from decades of desktop development, then abandoned them for the web (and worse, electron). It's annoying learning a new convention for every website. We could do a lot worse than bringing back menus.
If it not Facebook, it would be some other medium. What's the alternative, prevent people from talking to each other unsupervised?
When you look at someone else's profile, Similarity shows you the questions that you both feel strongly about (answered at the edges of the range) and either agree about or disagree about. The idea is that these would be conversation starters - if you both are passionate about skiing, it should be front and center.
This is a side project I've been working on on-and-off (mostly off) since the 1990s. I guess you would call it an experimental "dating site" though it's designed to be fun/interesting to people who aren't single (like me).You don't need to sign in to see how it works, so try it out. There is no swiping.The original inspiration was a 90s-era website called moviecritic.com that let you rate...
My guess is that the initial response by MisterTea was an attempt at language policing, and this whole thread is a waste of time.
What, you don't enjoy having your opinions dismissed because someone famous shares them?
If you can work remotely (or not at all), Spain has a lot going for it.
The factory of the future will have only two employees, a man and a dog. The man will be there to feed the dog. The dog will be there to keep the man from touching the equipment.
Seems like the dog failed here.
Ignoring robots.txt is not wrong. That's my opinion, just as valid as yours.
It also happens that the legal system agrees with my opinion of the wrongness of this act.
Also, you did say this:
> where website owners can legally dictate
Which is, as I pointed out, false.
This is a side project I've been working on on-and-off (mostly off) since the 1990s. It should be pretty self-explanatory.It's not vibe coded, though I lean pretty heavily on codex (mostly the $20/mo plan - not a lot of tokens burnt here). The stack is java, aws eb, neon postgres, and few cloudflare doodads. Basically designed to run by itself hands-off.I'm working on some ideas to help with...
A website can block Xyz user agent, put Xyz in robots.txt, or even put "No using Xyz!" in a popup and you cannot be prosecuted for using Xyz. It might be hard for you to evade their requirements, but it's not illegal.
Whether or not it's wrong is a matter of opinion. Yours differs from mine, that's fine.
JS has a completely different threat model. And PHP has just been a basketcase from inception.
They do:
Not every optimization requires a JEP, but certainly something as big as "add or remove a JIT" would 100% require a JEP.
It's not nice. It is, however, not illegal.
And before you agitate against that, think deeply about the consequences. A world where website owners can legally dictate exactly what software you use to access their content.
I pay attention to frontend code just to keep code quality up. Frontend work is relatively low stakes from a security perspective and I've never seen the robots do anything problematic. I don't vibe code React but I think you could get away with it today.
Backend is a totally different story.
That's still a lot of engineering getting displaced.
Also... employment in some parts of the stack is genuinely going away. I don't even look at CSS anymore.
Compared to laptop quality, I suspect model quality will be a much bigger competitive advantage in the tournament of the marketplace. High-quality laptops are still limited by the quality of the software developer.