News for hackers. Stuff that matters.
Re:Always Bet on Text (2014) by numlock86 on Wednesday February 17, 2021 @07:16AM (#26165523)
Apples and oranges. The post states that the used Twitter logo PNG is 4000 bytes, while it's only 723. Try to express that logo in text, English language and in all its details with 723 characters, so you are able to reproduce a pixel perfect representation. Not even possible with 4000 characters anyway. Don't bother. Text will be ambiguous, unless you describe every single detail. If the target is to communicate "Twitter logo" then sure, just write that. But if you compare 723 bytes of "data" with just a few specific information pieces contained within that data ... sure, text might be better.

> text is the most powerful, useful, effective communication technology ever, period.

Nothing of this is actually true, period.

> I do not post to this blog with the intention of entertaining Hacker News Debate Club and I frequently disable comments or friend-lock posts in order to avoid this sort of nonsense. I'm not interested in further discussion.

Ah yes, the true seal of quality. (sarcasm)

Re:Always Bet on Text (2014) by willtim on Wednesday February 17, 2021 @08:17AM (#26165945)
Plain text is simple, elegant and has open-standards - it traces its origins back to telegraph codes that we have been using for hundreds of years - and still forms the basis of most of the internet now. So I am inclined to agree with the statement "text is the most powerful, useful, effective communication technology ever, period".
Re:Always Bet on Text (2014) by numlock86 on Wednesday February 17, 2021 @09:44AM (#26166797)
By that same argument/logic you might as well argue cave paintings are superior over text. It traces back probably over 50000 years and is still universal today and doesn't even require understanding of a specific language - and it still forms the basis of most of society now. (art, painting, photographs, graffiti, ...)
Re:Always Bet on Text (2014) by SubjectToChange on Wednesday February 17, 2021 @10:58AM (#26167825)
Your reply is in text. Would you care to link a set of paintings to express your argument instead?
Re:Always Bet on Text (2014) by rhn_mk1 on Wednesday February 17, 2021 @11:14AM (#26168028)
That's the point: take an arbitrary criterion, end up with an arbitrary answer.
Re:Always Bet on Text (2014) by mattnewton on Wednesday February 17, 2021 @11:14AM (#26168029)
It’s also in ascii, is that superior to all other character sets, or an accident of history?
Re:Always Bet on Text (2014) by sellyme on Wednesday February 17, 2021 @07:19PM (#26173755)
> It’s also in ascii

No it isn't:

> 10:48:55.380 document.location.href

> 10:48:55.384 "https://news.ycombinator.com/item?id=26166797"

> 10:48:57.723 document.characterSet

> 10:48:57.726 "UTF-8"

Re:Always Bet on Text (2014) by mattnewton on Thursday February 18, 2021 @11:40AM (#26182025)
If it was really Unicode I could use an eye roll emoji to reply with a succinct image, instead of all these words to describe my reaction.
Re:Always Bet on Text (2014) by sellyme on Sunday February 21, 2021 @12:40PM (#26215389)
That's HN filtering your input, nothing to do with the actual encoding.

Plenty of non-ASCII symbols show up perfectly fine. For example, '£'.

Re:Always Bet on Text (2014) by numlock86 on Wednesday February 17, 2021 @08:54AM (#26166259)
Please elaborate how text is most powerful (in which aspect anyway? define powerful) and most effective (surely it isn't or text wouldn't be the prime example for stuff that's good to compress).
Re:Always Bet on Text (2014) by woliveirajr on Wednesday February 17, 2021 @09:23AM (#26166552)
He would have to use words for that... Could you help him showing some image of "powerful" and "effective"?
Re:Always Bet on Text (2014) by Koshkin on Wednesday February 17, 2021 @12:22PM (#26168843)
強大的 and 有效的, respectively? (I can see some powerful person in the middle of the first image.)
Re:Always Bet on Text (2014) by msla on Wednesday February 17, 2021 @09:35AM (#26166674)
Right after you provide an image that's as effective as the text of the First Amendment.
Re:Always Bet on Text (2014) by numlock86 on Wednesday February 17, 2021 @10:00AM (#26166974)
Think of all the non-text technologies involved right now for me being able to read your strawman.
Re:Always Bet on Text (2014) by jshevek on Wednesday February 17, 2021 @10:07AM (#26167089)
Can you explain the strawman you believe the parent is presenting? What is the original argument, and what is the misrepresentation?
Re:Always Bet on Text (2014) by willtim on Wednesday February 17, 2021 @09:19AM (#26166515)
I am not the source of the original statement, but my own interpretation of "powerful" aligns with simplicity and flexibility. Plain text has only slightly more structure than a stream of bytes, meaning it retains a lot of simplicity and flexibility. Yes plain text can be inefficient and is overused (a proprietary unpublished wire-format does not need to use JSON). However, 50 years from now, the only data I feel comfortable knowing I'll be able to read is plain text (and possibly also JPEG and a few other well-specified and simple binary formats). Many binary formats are effectively defined by large complex and transient code bases that target particular tool chains and APIs. A new binary format needs to justify itself, less so plain text.
Re:Always Bet on Text (2014) by aembleton on Wednesday February 17, 2021 @09:49AM (#26166852)
The Twitter logo in SVG format is only 687 bytes and can be as large as you like: https://upload.wikimedia.org/wikipedia/en/9/9f/Twitter_bird_...
Re:Always Bet on Text (2014) by mrec on Wednesday February 17, 2021 @09:58AM (#26166943)
My SVG is extremely rusty, but it doesn't look as if that

     xmlns:v="https://vecta.io/nano"
serves any purpose besides advertising.
Re:Always Bet on Text (2014) by boogies on Wednesday February 17, 2021 @11:08AM (#26167952)
It's probably not the only removable part, the icon can be 414 bytes: https://github.com/edent/SuperTinyIcons#how-small
Re:Always Bet on Text (2014) by DarkWiiPlayer on Wednesday February 17, 2021 @10:05AM (#26167057)
SVG is XML, which I'd say counts as text.
Re:Always Bet on Text (2014) by duckerude on Wednesday February 17, 2021 @10:24AM (#26167326)
I don't think it counts for the purposes of this blog post.

You can't translate the Wikipedia quote in the article into an SVG except by just rendering the bare text.

Checking programmatically that text is about "bird" or "Twitter" is very easy. Checking that an SVG is about "bird" or "Twitter" is very hard.

It's not even efficient. It conveys the same message as the word "Twitter" in a hundred times the size. And it wouldn't be less efficient if it were a binary format.

It's maybe more suitable for carving into granite than a binary format, but you'd be better off carving the logo itself.

Re:Always Bet on Text (2014) by DarkWiiPlayer on Thursday February 18, 2021 @02:12AM (#26176906)
> Checking programmatically that text is about "bird" or "Twitter" is very easy. Checking that an SVG is about "bird" or "Twitter" is very hard.

That depends on what you want:

If you know what twitter is, then yes, just saying "twitter" is more efficient than a whole SVG file describing the twitter logo.

But if you don't know what twitter is, nor what its logo looks like, SVG is a very efficient way to describe the logo exactly. If you can have it rendered to your screen that's optimal, but if not, you can take it as instructions to redraw the logo yourself and still get an accurate impression of what the twitter logo looks like.

I that sense, "twitter" and the SVG of the twitter logo are both text, but they don't have the same meaning.

As for the granite, it is indeed one situation where just drawing the plain SVG logo is more effective, but SVG would still be viable. Over telephone, on the other hand, you just can't transmit an image. You can only attempt to describe it, and the more detailed you get with that, the closer you come to just using a code very similar to SVG.

Re:Always Bet on Text (2014) by JoyrexJ9 on Wednesday February 17, 2021 @11:24AM (#26168146)
How far do you take that line of reasoning? Base64 is text?
Re:Always Bet on Text (2014) by imhoguy on Wednesday February 17, 2021 @11:34AM (#26168265)
00101010010100110101001... is text too, but I agree SVG is just machine description, human sees the rendered result in that context.
Re:Always Bet on Text (2014) by whateveracct on Wednesday February 17, 2021 @11:35AM (#26168278)
it's not consumed as text
Re:Always Bet on Text (2014) by fuzzfactor on Wednesday February 17, 2021 @08:44AM (#26166176)
>Nothing of this is actually true, period.

Could you kindly verify that by repeating your post using something other than what amounts to a text file?

If not maybe that's an even truer seal of irony.

Re:Always Bet on Text (2014) by hardlianotion on Wednesday February 17, 2021 @09:11AM (#26166424)
I read from parent's point that what you are trying to communicate matters. I take from that, that text works sometimes, and sometimes something else is a better form of communication.
Re:Always Bet on Text (2014) by fuzzfactor on Wednesday February 17, 2021 @04:09PM (#26171824)
Yes, it does help when you can read between the lines . . .
Re:Always Bet on Text (2014) by numlock86 on Wednesday February 17, 2021 @09:39AM (#26166728)
> Could you kindly verify that by repeating your post using something other than what amounts to a text file?

Could you kindly present me your comment without using all these inferior non-text technologies involved on my side to read it off my screen? That's the irony, if anything.

Re:Always Bet on Text (2014) by drewzero1 on Wednesday February 17, 2021 @09:58AM (#26166947)
That sounds like a you problem. This site is one of a dwindling number that work flawlessly with a text-only browser, so if you view it in Links or similar (as I am right now) you can have a pure text experience without any of those pesky non-text technologies getting in the way!
Re:Always Bet on Text (2014) by numlock86 on Wednesday February 17, 2021 @10:06AM (#26167075)
> the "text-only browser"-argument

That's a bit short-minded, don't you think? Or is this some kind of troll meme at this point? Anyway, I don't expect you to have some off-spec working TLS/TCP/IP/ARP/ETH implementation purely based on text, yet alone are connected to the internet via some text-only telegraphy station utilizing those things. Pretty sure your output device (read as: screen) has some sort of analog/digital signaling as well that's not ASCII encoded. There are sure some pesky non-text technologies involved ...

Re:Always Bet on Text (2014) by drewzero1 on Wednesday February 17, 2021 @11:10AM (#26167983)
~I'm not sure where you're going with this or how seriously you're taking it~, but if I have to I will dig out a couple of DECwriters and we can continue this discussion as a pure ASCII text conversation. (Just as soon as I find a null modem cable long enough to reach wherever you are.)

Edit: upon some rereading, I get that there was maybe more sarcasm in gp comment than I perceived at the time.

Re:Always Bet on Text (2014) by fuzzfactor on Wednesday February 17, 2021 @12:21PM (#26168826)
Wasn't that why they called it hyper-text?
Re:Always Bet on Text (2014) by fuzzfactor on Wednesday February 17, 2021 @12:15PM (#26168753)
In the USA the USPS usually does not fail to deliver a text document, no superior nor inferior technology required.

And they still reach places having no other form of comunication.

If it was not a post card, you would need to open the envelope please.

If you would like to read that kind of text off your screen, you might just need to scan it yourself or find someone who can.

Re:Always Bet on Text (2014) by Al-Khwarizmi on Wednesday February 17, 2021 @10:53AM (#26167761)
What does the display (or TTS) technology used to read it matter in this discussion?

Obviously you need ways to display text in the physical world, be it a screen or a piece of handwritten paper. It's still text.

Re:Always Bet on Text (2014) by numlock86 on Wednesday February 17, 2021 @11:04AM (#26167909)
> What does the display (or TTS) technology used to read it matter in this discussion?

> Obviously you need ways to display text in the physical world, be it a screen or a piece of handwritten paper. It's still text.

And what about transfer? People keep claiming text is superior for transferring information, yet the majority my network stack or anything involved with the transport isn't text based.

The premise of the whole "text is the best technology" argument is based on cherry picking and strawman arguments anyway.

Re:Always Bet on Text (2014) by fuzzfactor on Wednesday February 17, 2021 @12:26PM (#26168886)
>The premise of the whole "text is the best technology" argument is based on cherry picking

I agree with that so naturally cherry-pick the thing expected to be the most universal and the last one standing.

Aren't everyone else's network stack usually sending packets of text when it's a plain text file? Even if it is hypertext.

Re:Always Bet on Text (2014) by falcolas on Wednesday February 17, 2021 @09:22AM (#26166539)
> The post states that the used Twitter logo PNG is 4000 bytes, while it's only 723.

The article was written in 2014. Worth remembering when nitpicking the text of an article.

Re:Always Bet on Text (2014) by aembleton on Wednesday February 17, 2021 @09:45AM (#26166810)
Do PNG files reduce in size over time?
Re:Always Bet on Text (2014) by orra on Wednesday February 17, 2021 @09:51AM (#26166865)
Not by themselves, but maybe they didn't use an optimiser before. Or used a far better optimiser now. Or tweaked the logo, and now it's more amenable.to optimisation.
Re:Always Bet on Text (2014) by kyle-rb on Wednesday February 17, 2021 @11:41AM (#26168351)
The author says in the post that it's a 20x20 image. That's only 400 pixels, and 4 bytes per pixel (RGBA) would only make it 1600 bytes with no compression at all.
Re:Always Bet on Text (2014) by orra on Wednesday February 17, 2021 @12:12PM (#26168726)
Then that's quite some impressive, uh, decompression.
Re:Always Bet on Text (2014) by DarkWiiPlayer on Wednesday February 17, 2021 @10:27AM (#26167369)
I don't know, but if they do, they seem to have a half-life of about 2.431184 years. That's interesting news.
Re:Always Bet on Text (2014) by d0mine on Wednesday February 17, 2021 @11:15AM (#26168047)
Compare a book (a few megs) with a picture of the same size. What do you think can communicate more info? Do you have a single counter-example?
Re:Always Bet on Text (2014) by andagainagain on Wednesday February 17, 2021 @11:57AM (#26168558)
The beauty of both mediums is in the compression.

Text is that it's highly compressible while also being highly compressed (and lossy) info already. To make text we have to filter our own ideas, and then to interpret text we have to add a bunch of info back from context.

Pictures have the same tricks up their sleeve. Bitmaps are great but inefficient. If we put it through a lossy compression, it's a lot better. If we make it semi procedurally with a vector file, it's even better. How far can we take a compressed procedural file though? Well.. .kkreiger was about 97 KB, and stores a full 3d shooter. For a meg, you could store 100 such full games. https://en.wikipedia.org/wiki/.kkrieger

Text isn't best in every way. With clever design we can use all the same principles that make text efficient, and make other types of data more efficient. It is a very good default though.

Re:Always Bet on Text (2014) by axaxs on Wednesday February 17, 2021 @01:52PM (#26170000)
There are single pictures you couldn't describe with terabytes of text(to a human, that is). Imagine for example trying to describe the milky way and northern lights. Yeah you could convey their looks in words but nobody is going to end up with the correct visual no matter how hard you try. Now add in other things, like emotion on people's faces. Some things just aren't possible to describe in full.
Re:Always Bet on Text (2014) by d0mine on Wednesday February 17, 2021 @03:22PM (#26171188)
you somehow managed to describe the pictures without showing them
Re:Always Bet on Text (2014) by dmingod666 on Wednesday February 17, 2021 @07:56AM (#26165792)
well, svg is text. The jpg/png icon will pixelate when zoomed, but svg will retain its quality no matter how much you zoom in... :)
Re:Always Bet on Text (2014) by dkersten on Wednesday February 17, 2021 @08:12AM (#26165911)
> svg is text.

If SVG counts as text, then text is just binary. The encoding is not important, the final result (an image you see on a screen, in the case of SVG) is.

Besides, try reading out the actual SVG source text to someone and see if they can tell you what the image you are describing is. I dunno about you, but I find thinking in terms of paths and strokes to be rather meaningless.

Or another example, do you consider Wavefront .obj files text? They're ascii files, but I don't consider a series of "v 0.123 0.234 0.345 1.0" as something I would ever read in text form and have even the slightest idea of what the final 3D model actually is. I have to view it visually. Its "technically" text, but its no more useful as text (for a human text reader) than if it were binary data. Encoding isn't what makes text what it is, so non-text things encoded as text aren't really text.

Re:Always Bet on Text (2014) by Valgrim on Wednesday February 17, 2021 @08:46AM (#26166192)
SVG is definitely human-readable. It's just drawing instructions, draw a line from there to there, then another one from there to there, etc. I can read it to someone over the phone with a pen and graph paper, and he can draw it exactly like it should be represented, with zero loss of quality. It's no different than someone looking at list of cash transactions. Numbers are text too.

Of course, to extract meaning from this text (what is it?) requires drawing it. But you don't have to, you can just name it. You could just say "I'm sending you the stylised image of a blue bird, with the instructions on how to draw it using the SVG text standard". Or just, more clearly even, the following string of characters: "twitter_logo.svg"

Re:Always Bet on Text (2014) by danShumway on Wednesday February 17, 2021 @10:56AM (#26167794)
> SVG is definitely human-readable.

No. A path tag with a 500-600 element `d` attribute is not human readable. It is not human understandable or parsable until it's converted into a visual format.

Ask a blind person whether they think SVG charts are accessible on their own without any additional markup or alternate explanations or controls. Ask them if they can read SVG line charts by stepping through the path property. Figuring out how to communicate complicated graphs/charts with lots of data without relying on any visual medium is a complicated problem that we are still trying to solve.

> You could just say "I'm sending you the stylised image of a blue bird, with the instructions on how to draw it using the SVG text standard". Or just, more clearly even, the following string of characters: "twitter_logo.svg"

By that logic, a PNG is also text, because I can do the same thing. All images can have alt tags. Even Javascript Canvas can have fallback text for when it doesn't render. My Twitter png can be transmitted as "twitter_logo.png".

What do people mean when they say text is preferable if not that the textual representation is more useful than the image representation? If you didn't feel like the SVG format was adding any useful information in its rendered form, you wouldn't waste the time sending information to render it. You would just send the alt text.

> I can read it to someone over the phone with a pen and graph paper, and he can draw it exactly like it should be represented, with zero loss of quality

Right, and when that person draws it, they will have converted it from a textual format into a visual one. I can send you the individual pixels of a small raster image over the wire in a textual format and you can sit down on a piece of grid paper and ink in squares until you come up with the final image. At which point you will no longer be looking at a piece of text.

To argue that the fact that we can encode a format over a UTF-8 stream or physically replicate your computer's drawing algorithm makes a thing text seems to me to be a misreading of the original article's point. The original article is not complimentary of Twitter's SVG, it explicitly brings it up as an example of a non-text medium.

If you expand the definition of text to include basically any storeable information that can be theoretically encoded into UTF-8, then sure, I would agree that text in that system is tremendously powerful. But that's not a useful category to talk about, it's so broad that it becomes meaningless.

Re:Always Bet on Text (2014) by dkersten on Thursday February 18, 2021 @09:25AM (#26180095)
> It's just drawing instructions, draw a line from there to there

That doesn't make it human-readable. I challenge you to tell me what (even the basic shape) this SVG is without loading it in a viewer (taken from a real SVG, not something handcrafted to prove you wrong, but the first thing I found online while searching for public domain SVG files):

https://gist.github.com/danielytics/90446a2314c1ad87017233eb...

Good luck figuring out what that is, even with graph paper. And that's a single layer, single (even if a bit complex) shape, single colour SVG. They only get more incomprehensible from here.

Re:Always Bet on Text (2014) by dmingod666 on Wednesday February 17, 2021 @08:55AM (#26166269)
Is math that you not understand, really text?

Is human comprehensibility a pre-requisive to be called text? What if there was a written language no one understood, would that be text? What if someone broke the code for it? Would it suddenly become text?

Re:Always Bet on Text (2014) by criddell on Wednesday February 17, 2021 @08:44AM (#26166175)
If SVG is text, then so is StarWars.mpg.b64.
Re:Always Bet on Text (2014) by wvenable on Wednesday February 17, 2021 @12:01PM (#26168594)
Some SVG is very readable and easy to modify. I'm no designer but I've opened up SVG files and made modifications to get what I want (remove elements, change colors, etc).

Not all SVG authoring tools make SVG's easy to read/modify. Tools in the 90's used to the same thing with HTML. Are you going to argue HTML isn't text?

Re:Always Bet on Text (2014) by criddell on Wednesday February 17, 2021 @07:21PM (#26173774)
> Are you going to argue HTML isn't text?

Go to google.com and view source. That's text, right?

Re:Always Bet on Text (2014) by dmingod666 on Wednesday February 17, 2021 @08:03PM (#26174123)
Compression is part of human communication also. Sometimes it's used to keep the communication short, sometime to hide the meaning behind what is said.

lol, brb, PFA, W.H.O., IMHO, IANAL, GPA, GTA.. word soup for a different audience..

Re:Always Bet on Text (2014) by wvenable on Wednesday February 17, 2021 @08:29PM (#26174328)
So because google.com is hard to read, HTML is not text?
Re:Always Bet on Text (2014) by numlock86 on Wednesday February 17, 2021 @08:07AM (#26165867)
> svg is text

Actually I thought about talking about SVG, which would be the natural result of taking a text representation of shapes ... and then use abbreviations until you are at some expert level language (SVG for example), which would then break the argument again. You might as well use some binary representation then, because most people don't speak fluent SVG.

Re:Always Bet on Text (2014) by DarkWiiPlayer on Wednesday February 17, 2021 @10:29AM (#26167398)
Most people don't speak fluid tok pisin either; does that make it less of a language?

Also, you'd be surprised by the amount of people that write SVG by hand, which I doubt you'll see with PNG anytime soon.

Re:Always Bet on Text (2014) by fotad on Wednesday February 17, 2021 @08:07AM (#26165877)
Different SVG engines may show different result, that may not acceptable for logo.
Re:Always Bet on Text (2014) by mcherm on Wednesday February 17, 2021 @08:13AM (#26165917)
Can you elaborate?

Outside of bugs, I was under the impression that SVG was actually pretty well specified and that (except perhaps for pathological examples created intentionally) the rendering of an SVG was quite consistent.

What am I not aware of?

Re:Always Bet on Text (2014) by admax88q on Wednesday February 17, 2021 @10:44AM (#26167625)
That's a biased comparison. Obviously an image is better at communicating an image. By setting the goalposts at "pixel perfect recreation" you've already selected a winner.
Re:Always Bet on Text (2014) by teknopaul on Wednesday February 17, 2021 @09:32AM (#26166648)
re:Try to express that logo in text

"Twitter"

carries the same weight

Re:Always Bet on Text (2014) by numlock86 on Wednesday February 17, 2021 @09:47AM (#26166834)
Tell me in 723 characters or less what this "Twitter" looks like so I can make an exact copy of it. Text is ambiguous.
Re:Always Bet on Text (2014) by wizzwizz4 on Wednesday February 17, 2021 @11:01AM (#26167868)
Images are the best way to describe images. Many ideas are better expressed in text than anything else we have.
Re:Always Bet on Text (2014) by doublerabbit on Wednesday February 17, 2021 @10:55AM (#26167774)
HN doesn't render ASCII or ANSI art correctly however both methods can serve as representation of Twitter in text and graphic less then <700 characters.

     ,~
    ('v)__
   (/ (``/
    \__>' hjw
     ^^
   Twitter
Bird kindly borrowed from: https://www.asciiart.eu/animals/birds-land
Re:Always Bet on Text (2014) by danShumway on Wednesday February 17, 2021 @11:09AM (#26167965)
This isn't text, you're using ASCII symbols as pixels in a grid to represent a raster image. This is literally just a raster image on an unconventional canvas.

If you treat a uniwidth character grid of characters as pixels, you have not converted an image into text, you have encoded text into an image. It's no different than using extended characters and font colors in a fixed width terminal window to make terminal art.

The fact that you use UTF-8 to encode something does not mean it will magically work in a screen reader, or that it will retain any of the advantages of pure text. I can encode any image or video file in a UTF-8 format and send it to you. Down this path lies calling everything text.

But if your "text" stops being readable if I disable monospace, or it stops working if I change the font, or it stops working if I change line wrapping, or it stops being communicable as soon as I try to read it out loud -- then it's not pure text. Using a UTF-8 character as a pixel does not change the fact that you're drawing an image out of pixels.

Re:Always Bet on Text (2014) by doublerabbit on Wednesday February 17, 2021 @11:18AM (#26168075)
Interesting hypothesis. Thanks.
Re:Always Bet on Text (2014) by numlock86 on Wednesday February 17, 2021 @11:09AM (#26167959)
That does not even remotely represent the Twitter logo, though. Shape and color are completely lost information, which are essentially the key properties that make the Twitter logo the Twitter logo.
Re:Always Bet on Text (2014) by doublerabbit on Wednesday February 17, 2021 @11:36AM (#26168290)
Valid point.