News for hackers. Stuff that matters.
Re:Designing very large JavaScript applications by komali2 on Friday April 20, 2018 @05:25PM (#16888543)
I've always disliked the "BIG TEXT CHOPPED-OUT BUT YOU'LL READ IT BELOW AGAIN IN JUST A SECOND" paradigm in magazines and newspapers. Like, I'm reading the article anyway, why suddenly spit some of the words in my face super big? I'm guessing it's for skimmers, catch their eye and bring them into an interesting paragraph that's further down from the top.

But this article does it at the beginning... we read the sentence "Hello, I used to build very large JavaScript applications" three times. First as an image, then as a label for the image... and then as the first sentence of the article. Why lol

Re:Designing very large JavaScript applications by gyrgtyn on Friday April 20, 2018 @10:43PM (#16889734)
Recently, I'm annoyed at coming into a hackernews thread and the top thing is some completely irrelevant thing.
Re:Designing very large JavaScript applications by muyuu on Saturday April 21, 2018 @02:06AM (#16890200)
meta
Re:Designing very large JavaScript applications by bunderbunder on Friday April 20, 2018 @10:16PM (#16889655)
> Why lol

Because, even closer to the beginning, in the real first sentence of the article (by which I mean, the first sentence after the title), it says, "This is a mildly edited transcript of my JSConf Australia talk."

This is not an example of the "big text chopped out" paradigm from magazines, it's an example of the, "each slide contains a brief of the most important part of what you'll be saying while that slide is being displayed" paradigm from conference lectures.

Re:Designing very large JavaScript applications by et-al on Friday April 20, 2018 @11:24PM (#16889835)
The problem is those slides hinder the readability of the actual article.

For a reader, you get into the rhythm of the writer's voice, only to be interrupted by a giant image of text every other paragraph. It's a battle between just skimming the slides, or trying to read the content.

If the author had just swapped out the "loud" text images for subtle headers, the article would actually flow.

Re:Designing very large JavaScript applications by chrismorgan on Friday April 20, 2018 @11:08PM (#16889795)
And therein is also seen a limitation of using someone else’s blog engine; on large (wide) displays, this would be better done with the slides on one side, and the speech on the other, appropriately lined up. But you can’t do that when you’re using Medium for the post.
Re:Designing very large JavaScript applications by tejohnso on Saturday April 21, 2018 @11:43AM (#16891826)
I've been thinking the exact same thing for years and couldn't put it into words.

The most annoying thing is I can never be sure whether the BIG TEXT CHOPPED-OUT is actually going to be repeated again later in the article. Otherwise I'd just happily ignore those big sections every single time. As it is now, I have to read it and then get mad when moments later I find myself reading the exact same thing. I wish there was a way to stop this.

edit: Thanks to those commenters who mentioned https://en.wikipedia.org/wiki/Pull_quote - It's nice to be able to properly refer to that which I despise.

Re:Designing very large JavaScript applications by bichiliad on Friday April 20, 2018 @11:27PM (#16889844)
The images are labeled for accessibility reasons; they're used as fallback descriptions for figures and images. The slides are wrapped with `<figure>` tags, and the captions with `<figcaption>` tags. They're so that screen readers can interpret the figure, which is why the text is often redundant.
Re:Designing very large JavaScript applications by mort96 on Saturday April 21, 2018 @07:00AM (#16890926)
...But images have the alt attribute when you want to help screen readers without cluttering things up for people who read the image.
Re:Designing very large JavaScript applications by bryanrasmussen on Saturday April 21, 2018 @12:31AM (#16889987)
I guess Medium should offer a visually-hidden style then.
Re:Designing very large JavaScript applications by pacomerh on Saturday April 21, 2018 @01:42AM (#16890151)
These look like they where adapted from the talk linked bellow, and each slide image has a description probably for accessibility (screen readers).

https://www.youtube.com/watch?v=ZZmUwXEiPm4

Re:Designing very large JavaScript applications by nkantar on Friday April 20, 2018 @05:28PM (#16888563)
Those appear to be be slides from the talk that's the original form of this article.

This doesn't necessarily justify the first slide's presence at the very beginning, but it might explain it.

Re:Designing very large JavaScript applications by oftenwrong on Saturday April 21, 2018 @07:33AM (#16891015)
https://en.wikipedia.org/wiki/Pull_quote

I think they're more useful in a newspaper because they can catch the eye as the reader scans the page. On the web they are fairly useless.

Re:Designing very large JavaScript applications by saghm on Friday April 20, 2018 @09:30PM (#16889536)
> I've always disliked the "BIG TEXT CHOPPED-OUT BUT YOU'LL READ IT BELOW AGAIN IN JUST A SECOND" paradigm in magazines and newspapers.

Just came here to say you're not alone; I've always hated this too, and I really wish it hadn't gotten adopted on the web

Re:Designing very large JavaScript applications by droidist2 on Saturday April 21, 2018 @12:05AM (#16889926)
It's sort of like reality TV teasers but in printed form. Right before the commercial break they show a clip of something you'll see "when we return."
Re:Designing very large JavaScript applications by xbryanx on Friday April 20, 2018 @06:10PM (#16888807)
That text (here and in magazines, newspapers) isn't for you. It's for the casual browser who isn't reading the article yet. It's trying to suck you in and/or give you teensy bite of info even if you don't read the article. https://en.wikipedia.org/wiki/Pull_quote

Of course this article format is kinda pushing the limits I agree.

Re:Designing very large JavaScript applications by saurik on Friday April 20, 2018 @07:19PM (#16889096)
Which is why it doesn't have any place being used on a web page :/.
Re:Designing very large JavaScript applications by zer00eyz on Friday April 20, 2018 @08:21PM (#16889298)
Why not?

I admit to often reading things that are far outside my wheelhouse, or not always topics I assume I will enjoy. If I start one of these and find myself loosing interest, these quotes and call outs can draw me further in or push me right out.

Re:Designing very large JavaScript applications by myth_buster on Saturday April 21, 2018 @09:08AM (#16891290)
This is a talk so it makes sense to put the text on the slide and also talk about it.

The image caption, I took it as medium's implementation of although text for cases the images don't load.

In this case they just happened to be similar.

Re:Designing very large JavaScript applications by stjohnswarts on Friday April 20, 2018 @09:07PM (#16889462)
It's like putting a cover on a book that is related to the matter in the book, to keep you reading because you may start getting bored, so they pull out a sound byte. Pretty obvious.
Re:Designing very large JavaScript applications by karmakaze on Sunday April 22, 2018 @02:18PM (#16897592)
Yeah the picture labels in that article looked machine generated--generc and redundant unless vision impaired.
Re:Designing very large JavaScript applications by kraftman on Friday April 20, 2018 @10:41PM (#16889726)
I always assumed it was to bulk the article out to fit the printed page.