Static pages are fine if you don’t want to interact with them. Books have been around since the 1400s.
But they won’t let you search a whole book for particular name, place, term. Or take your input and calculate answers for you? Or let you create music or art? etc. etc.
You don’t need that to search. In fact, you send the search query and get the response back.
Yes, they let you search the term, it’s called asking the librarian to tell you which page.
Forms that send a post request to the server and the server serves you the page with the answer is how it works. Ajax is cool, sure, but don’t tell us lies, or don’t talk with confidence without knowing.
My whole comment was that I’m not sure what the point is, because that’s not how it works in reality. So if you actually want to know, you’ll have to ask the author of the comment above me.
I was trying to make the best of what I could with the bad example they provided…
But as they already responded you, before Ajax was a thing term searches were done via forms. I still state that it has it’s uses, but let’s not pretend like the universe was born with javascript.
But if the best of what you can do with it doesn’t make sense, then why do it? It’s not like it’s helping, just distracting from the parts that DO work.
And kind of the same thing again: The universe wasn’t born with forms, either.
When we did a project for a redesign of our web app at work, when I showed stuff to the UXer he said “I see this is designed by a programmer. Because a programmer says: But it works.”
And indeed, that is how all of the comments I read here feel; that things like a denounced search are just irrelevant toys, instead of a solid part of the toolkit of a professional modern developer.
Static pages are fine if you don’t want to interact with them. Books have been around since the 1400s.
But they won’t let you search a whole book for particular name, place, term. Or take your input and calculate answers for you? Or let you create music or art? etc. etc.
Y’all forget about forms? And, uh, programs?
I remember doing indexes in html with hyperlinks
You don’t need that to search. In fact, you send the search query and get the response back.
Yes, they let you search the term, it’s called asking the librarian to tell you which page.
Forms that send a post request to the server and the server serves you the page with the answer is how it works. Ajax is cool, sure, but don’t tell us lies, or don’t talk with confidence without knowing.
You ask the librarian how often the word “arrow” is in Lord of the Rings, and they have to tell you?
Not sure what your point is, but that functionality could be built into a website without running any code clientside.
My whole comment was that I’m not sure what the point is, because that’s not how it works in reality. So if you actually want to know, you’ll have to ask the author of the comment above me.
I was trying to make the best of what I could with the bad example they provided…
But as they already responded you, before Ajax was a thing term searches were done via forms. I still state that it has it’s uses, but let’s not pretend like the universe was born with javascript.
But if the best of what you can do with it doesn’t make sense, then why do it? It’s not like it’s helping, just distracting from the parts that DO work.
And kind of the same thing again: The universe wasn’t born with forms, either.
When we did a project for a redesign of our web app at work, when I showed stuff to the UXer he said “I see this is designed by a programmer. Because a programmer says: But it works.”
And indeed, that is how all of the comments I read here feel; that things like a denounced search are just irrelevant toys, instead of a solid part of the toolkit of a professional modern developer.