I do NOT want search to become any fuzzier than it already is.
See the great decline of Google's search results, which often don't even have all the words you're asking about and likely omits the one that's most important, for a great example.
It might be that it's worth it to bifurcate soon. Search indexes and AI engines, doing different roles. The index would have to be sorted with AI though - to focus on original and first-party material and to downrank ad-driving slop.
> I do NOT want search to become any fuzzier than it already is.
For a specialized shop site you may want it. Search term: "something 150", the client is looking for a 1.5m something, if you're doing an exact text search your search engine will give you a lot of noise. Or you'll have to fiddle with synonyms, dictionaries and how you index your products with a huge chance to break other types of search queries.
Gemini 2.5 pro is basically free.
Also watsonx, but that's b2b.
And depending on the client vertical they tend to not use the same vocabulary when looking for products.
But contrary to some other comments I know LLM are not magical tools and anything we use will require data to fine tune whatever base model we choose. And it will be used on top of standard text search not as a full replacement. I'm sure many companies are currently doing the exact same thing or will be soon enough.
Humans are not the most reliable. If you're ok giving the task to a human then you're ok with a lower level of relisbility than a traditional computer program gives.
Simple example: Notify me when a web page meaningfully changes and specify what the change is in big picture terms.
We have programs to do the first part: Detecting visual changes. But filtering out only meaningful changes and providing a verbal description? Takes a ton of expertise.
With MCP I expect that by the end of this year a nonprogrammer will be able to have an LLM do it using just plugins in a SW.
And as was pointed out, if you use something like MCP, you can control what it spends on. You can limit the amount, and limit to a whitelist. It may still occasionally buy the wrong thing, but the wrong thing will be something you preapproved.
I just want to center the damn content. I don't much care about the intricacies of using auto-margin, flexbox, css grid, align-content, etc.
* "Has only been that way so far because that's how computers are" and
* "I just want to center the damn content.
I don't much care about the intricacies of using
auto-margin, flexbox, css grid, align-content, etc."
Centering a div is seen as difficult because complexities that boil down to "that's just how computers are", and they find (imo rightful) frustration in that.yes I think we're okay with divs not being centered some of the time.
many millions have been spilled to adjust pixels (while failing to handle loads of more common issues), but most humans just care if they can eventually get what they want to happen if they press the button harder next time.
(I am not an LLM-optimist, but visual layout is absolutely somewhere that people aren't all that picky about edge cases, because the success rate is abysmally low already. it's like good translations: it can definitely help, and definitely be worth the money, but it is definitely not a hard requirement - as evidence I point to the vast majority of translated software.)
I think there's overwhelming evidence that it's not truly necessary.
Maybe in an alternate universe where every user-agent enabled browser had this type of thing enabled by default, most companies would skip site design all together and just publish raw ad copy, info, and images.
You do / did care, e.g. browser support.
If you're assuming the user knows nothing then all tasks are hard. Ever try putting an image in a page if you don't know HTML? It's pretty tricky.
To imagine otherwise reminds me of The Infamous Dropbox Comment.
Addendum: to wit, whole companies, like SquareSpace and Wix, exist because web dev is a pain and WYSWIG editors help a lot
But these companies DO care (or at least that's the point) and don't "just want to do a simple thing".
The point of outsourcing is to give it to a professional with expertise like seeing a doctor. Dropbox isn't "just a simple thing" either, so no not the same.
You can't just want. It always backfires. It's called being ignorant. There are always consequences. I just want to cross the road without caring too. Oh the cars might just hit me. Doesn't matter?
> This sounds like a front-end dev that understands the intricacies of all of this
That's the person that's supposed to do this job? Sounds bog standard. What's the problem?
15 years ago it was just a google away, im sure AI can handle it fine.
Edit: I've been in the AI CSS BS loop just a few days ago, not sure how you guys miss it. I start screaming f-'s and "are you an idiot" when it cycles through "doesn't work", "ignored prereqs" and "doesn't make sense at all".
Your reply is correct, but it's exactly that "just do this specific configuration" sort of correct, which punctures component isolation all the way through and makes these layers leak into each other, creating a non-refactorable mess.
I suppose AI can provide a heuristic useful in some cases.
Then I handed it the employee directory.
Then I searched by country to find native speakers of languages who can review our GUI translation.
Some people said they don't speak that language (e.g. they moved country when they were young, or the AI guessed wrong). Perhaps that was a little awkward, but people didn't usually mind being asked, and overall have been very helpful in this translation reviewing project.
If you really, really wanted help with a translation project and you didn't want to pay, professional translators (which you should do since translation-by-meaning requires fluency or beyond in both languages), then there are more polite ways of asking this information than cold-calling every person with a "regional" sounding name and saying "hey, you know [presumed mother tongue]?"