When you use Telnet, you're opening an almost raw TCP connection to the server. This means that you have to make HTTP requests like your browser does to get the information that you need.
Try this:
> telnet google.com 80
You should get an empty window with a blinking cursor at the top. Now type this in:
GET / HTTP/1.1
and press Enter twice to send the line and end the request with an empty line. You won't be able to see what you're typing, though, because the server is not echoing back what you're typing (but the Telnet client moves the cursor for you).
You should get your response in HTML. Extra points if you can save it to a file and open it in a browser.
So then, what's Lynx? Lynx does exactly what your browser does: send requests, get the response, parse the HTML, and show it to the user. But this is all done in a command-line interface, which makes it difficult to align objects and format them correctly.
Telnet, on the other hand, just handles the requesting and responding part, which is why only crazy people browse the Web with just Telnet.
2Unfair comparison. Lynx is a web browser; it communicates using HTTP to the web server. Telnet is a plain-text shell (command-line interface), and typically uses TCP. Apples versus oranges; the telnet client cannot communicate with the HTTP web server, and vice-versa due to incompatible IPs. – sawdust – 2015-06-27T02:24:34.547
1Lynx uses the HTTP protocol which is laid on top of TCP/IP (protocol for the communication/data transfer), telnet provides the means to use TCP/IP. When using telnet in this way YOU must provide the basics of the HTTP protocol in the same way as Lynx. – Hannu – 2015-06-27T08:09:43.000