Mr. Musk, you tease us...

[Gąska]

@Gribnit probably id on regular HTML elements.

[dcon]

@Atazhaia said in Mr. Musk, you tease us...:

In other Musk news, apparently he expects his employees to work 80 hours/week, because ”that’s the amount of time you need to put in if you want to change the world” as he put it according to the article I saw.

I saw that on FB and commented:
"How To Become Single In One Easy Step" (or something like that)

[Gribnit]

@Gąska said in Mr. Musk, you tease us...:

@Gribnit probably id on regular HTML elements.

That doesn't even sound silly.

[Gąska]

@Gurth said in Mr. Musk, you tease us...:

<a name=foo><h2>Bar</h2>
<!--​ Note lack of quotes and </a> -->

Whaaaa? How did the parser even work with that? Did </a> close the nearest <a>, or just the one with href, or what? How were children elements determined?

In fact, I suspect that suggesting <a name="foo"> to some modern web developers might even get you into a flame war over how that’s not the “correct” way to do it.

Well, in HTML5, it's literally not correct.

[Gąska]

@Gribnit said in Mr. Musk, you tease us...:

@Gąska said in Mr. Musk, you tease us...:

@Gribnit probably id on regular HTML elements.

That doesn't even sound silly.

Because it's not.

[Gurth]

@Gąska said in Mr. Musk, you tease us...:

Whaaaa? How did the parser even work with that? Did </a> close the nearest <a>, or just the one with href, or what? How were children elements determined?

It just worked, really. Though there was a </p> too, for example, typically nobody bothered with it either — not even the example for that tag:

Paragraph: P

The P element indicates a paragraph. The exact indentation, leading space, etc. of a paragraph is not specified and may be a function of other tags, style sheets, etc.

Typically, paragraphs are surrounded by a vertical space of one line or half a line. The first line in a paragraph is indented in some cases.

Example of use:

<H1>This Heading Precedes the Paragraph</H1>
<P>This is the text of the first paragraph.
<P>This is the text of the second paragraph. Although you do not 
need to start paragraphs on new lines, maintaining this 
convention facilitates document maintenance.</P>
<P>This is the text of a third paragraph.</P>

(How do you quote a code block, BTW?)

That document is a good example of <a name>, by the way:

<H1><A NAME="SEC5" HREF="html-spec_toc.html#SEC5" REL=TOC>Document Structure</A></H1>

though it does use </a>.

[Gribnit]

This post is deleted!

[dkf]

@Gurth said in Mr. Musk, you tease us...:

It just worked, really.

SGML magic! But then virtually everything to do with SGML parsing is magical anyway; it's insanity factor was way higher than that of XML…

[Gribnit]

@Gąska said in Mr. Musk, you tease us...:

Well, in HTML5, it's literally not entirely correct.

HTML Standard

[Flips]

@Gurth said in Mr. Musk, you tease us...:

It just worked, really.

No it did not work, really. Evidence.

@pie_flavor
Hehe thanks.. Too busy with my new job. Maybe I can share some WTFs in the future if I encounter one (even tough I hope I won't find any, as it makes life harder then necessary).

[pie_flavor]

@Flips Welcome back!

[pie_flavor]

@Gurth said in Mr. Musk, you tease us...:

(How do you quote a code block, BTW?)

fn main() {
    println!("You just do!");
}

[PleegWat]

@dkf said in Mr. Musk, you tease us...:

@Gurth said in Mr. Musk, you tease us...:

It just worked, really.

SGML magic! But then virtually everything to do with SGML parsing is magical anyway; it's insanity factor was way higher than that of XML…

Like where <!--​--> is an SGML comment, but <!--​---> is not?

And in addition to the optional close tags, I recall the existence some additional syntaxes where you can run straight from one tag to another without >< inbetween, but not the actual details.

[Gribnit]

@PleegWat said in Mr. Musk, you tease us...:

not the actual details

open it. open the locked door. it probably was not locked for even any reason. let alone a good reason. probably an accident. open the locked door. open it.

[PleegWat]

@Gribnit I fear the day the performance problems in our third party XML parser drive me to the point of having to write my own.
Since we also use that to parse arbitrary HTML that will expose me to many horrors.

But it will be nowhere near as bad as true SGML.

[Gribnit]

@PleegWat jsoup may be your friend that day or maybe not. maybe it already is your 'friend' for all I know.

[PJH]

@Lorne-Kates said in Mr. Musk, you tease us...:

@PJH said in Mr. Musk, you tease us...:

SpaceX founder

Why would we want a pedophile on Mars?

Hey, if he can baselessly accuse people of being pedophiles, so can I!

He's probably going to look for some.

Though given Mars currently has 1.88 Earth years and 1d37m Earth days, I'm sure he'll spend far too long figuring out whether they're an Earthian or Martian pedo - if at all - depending on, variously

• age/species of victim
• age/species of abuser
• lengths of time each has spent on which planet.

[Magus]

@Zecc Considering no one ever hasn't.

[Gribnit]

@Magus said in Mr. Musk, you tease us...:

@Zecc Considering no one ever hasn't.

Have you?

[Magus]

@Gribnit As a human, none of whom ever have?

[Gribnit]

@Magus said in Mr. Musk, you tease us...:

@Gribnit As a human, none of whom ever have?

So are you dead or are you immortal, make up your mind.

[Gurth]

@Flips said in Mr. Musk, you tease us...:

@Gurth said in Mr. Musk, you tease us...:

It just worked, really.

No it did not work, really. Evidence.

It did work well enough for the kinds of web pages people typically made back then: little more than straight text with headers, some colours, and a couple of images.

[Magus]

@Gribnit What difference is there, for one such as I?

[hungrier]

@Gurth But did it work out for the miners in The Expanse?

[brie]

@Magus said in Mr. Musk, you tease us...:

@Zecc Considering no one ever hasn't.

Actually, three people haven't.

Aug 18, 2017

Only Three People Have Ever Died In Space, And You've Probably Never Heard Of Them

[Magus]

@brie I suppose it counts, but only barely - it at least wasn't in the atmosphere. These people definitely managed to die the furthest away from the surface. Still goes to show we aren't a very adventurous species, when it comes to space.

[brie]

@Magus Yes... we as a species usually prefer to let other species be the adventurous ones, when it comes to dying in space.

Nov 4, 2017  /  News

60 years on, what happened to all the animals sent to space

Stray dog sent into space in 1957 was first living creature to orbit Earth

[tharpa]

@topspin said in Mr. Musk, you tease us...:

@Zecc said in Mr. Musk, you tease us...:

He said:

Your probability of dying on Mars is much higher than on Earth

I very much disagree. I'm pretty sure I'm going to die on Earth.

Mr. Bayes would like to have a word with you.

"MrBayes is a program for Bayesian inference and model choice across a wide range of phylogenetic and evolutionary models. http://nbisweden.github.io/MrBayes/

Not sure I see the connection.

[Flips]

@Gurth said in Mr. Musk, you tease us...:

It did work well enough for the kinds of web pages people typically made back then: little more than straight text with headers, some colours, and a couple of images.

I can imagine it worked. But for a different reason. To elaborate:

If you got an <a> anchor, with a <parent> element, and you close the </parent> it would auto-close the children (in this example ) too.because the browser assumes this anchor should've been closed by now. Which probably is expected/correct behavior.

Otherwise (without such parent) you get this behaivor, where the rest of the text will be part of the anchor <a>.

Funniest part: even tough this forum should not accept <a> (and maybe all html-elements for that matter), it does. This forum even makes it a clickable link (and the browser autocloses with </a> after the parent-element, my forumpost-element, gets closed. again, expected behavior).

Who's gonna file a bug-report?

[anotherusername]

@Flips said in Mr. Musk, you tease us...:

Funniest part: even tough this forum should not accept <a> (and maybe all html-elements for that matter), it does.

If you click the "COMPOSE " in the composer, you'll see that it does accept <a>, as well as a few other "safe" HTML tags.

[Zecc]

@brie said in Mr. Musk, you tease us...:

Nov 4, 2017  /  News

60 years on, what happened to all the animals sent to space

Stray dog sent into space in 1957 was first living creature to orbit Earth

meteoric rise

Uh...

[Gurth]

@Flips said in Mr. Musk, you tease us...:

@Gurth said in Mr. Musk, you tease us...:

It did work well enough for the kinds of web pages people typically made back then: little more than straight text with headers, some colours, and a couple of images.

I can imagine it worked. But for a different reason.

Nobody so far gave a reason for why it would have worked, so I’m wondering what makes yours different :)

If you got an <a> anchor, with a <parent> element, and you close the </parent> it would auto-close the children (in this example ) too.because the browser assumes this anchor should've been closed by now. Which probably is expected/correct behavior.

I’m trying to remember if <a> was required to have an end tag or not if it had the name attribute, but I can’t really find it in the early spec — it seems to definitively indicate there should always be an end tag only from HTML 3.2 onwards. Looking at some of my very early HTML work, I notice I did add end tags in that case, so my example earlier is probably just my memory confusing the use of </a> with that of </p>, for which some early specs do say that it’s optional.

Funniest part: even tough this forum should not accept <a> (and maybe all html-elements for that matter), it does.

YMBNH

[Flips]

@Gurth said in Mr. Musk, you tease us...:
Nobody so far gave a reason for why it would have worked, so I’m wondering what makes yours different :)

That <p>-artiicle you gave was reason I disagreed. Hope you understand now (I'm not always clarifying enough unfortunately. Specially with my broken Dutch-English language)

YMBNH

@anotherusername said in Mr. Musk, you tease us...:
If you click the "COMPOSE " in the composer, you'll see that it does accept <a>, as well as a few other "safe" HTML tags.

Thanks. I never knew. So finally I learned how I can make code-blocks too! Kind-of handy, on a programmers forum

[Tsaukpaetra]

@Gąska said in Mr. Musk, you tease us...:

@Gurth said in Mr. Musk, you tease us...:

<a name=foo><h2>Bar</h2>
<!--​ Note lack of quotes and </a> -->

Whaaaa? How did the parser even work with that? Did </a> close the nearest <a>, or just the one with href, or what? How were children elements determined?

Remember that thing about parsing HTML with regex? And how it's almost impossible? Examples like this are why.

[anotherusername]

@Tsaukpaetra said in Mr. Musk, you tease us...:

@Gąska said in Mr. Musk, you tease us...:

@Gurth said in Mr. Musk, you tease us...:

<a name=foo><h2>Bar</h2>
<!--​ Note lack of quotes and </a> -->

Whaaaa? How did the parser even work with that? Did </a> close the nearest <a>, or just the one with href, or what? How were children elements determined?

Remember that thing about parsing HTML with regex? And how it's almost impossible? Examples like this are why.

Not closing an <a name> is really no big deal. It keeps going and going and going, but nobody's going to notice because it's not styled any differently. If you click a link to that anchor, it'll scroll to the top of it anyway, so you won't notice then either.

Closing tag always closes the nearest corresponding tag, anyway. In fact, if the nearest tag isn't corresponding then it's technically invalid HTML. <b>bold <i>bold italic</b> italic</i> will work, but it's invalid (the browser "fixes" it by splitting the <i> style so it's not overlapping with the <b> anymore -- making it <b>bold <i>bold italic</i></b><i> italic</i>).

[Gurth]

@Flips said in Mr. Musk, you tease us...:

That <p>-artiicle you gave was reason I disagreed. Hope you understand now (I'm not always clarifying enough unfortunately. Specially with my broken Dutch-English language)

Je mag het wat mij betreft best in het Nederlands uitleggen als je dat makkelijker vindt …

Anyway, the <p> example I quoted is from the actual standard for HTML 2.0, and the DTD for that says:

<!ELEMENT P     - O %p-content>

(The - O there indicates opening tag required, end tag optional.)

It probably also pays to beware of applying current methods of parsing HTML to 25-year-old specs. I don’t really know what’s changed in that, but I suspect quite a lot.

Thanks. I never knew. So finally I learned how I can make code-blocks too! Kind-of handy, on a programmers forum

Use a couple of backticks on a line by themselves, with a matching number after the code block. Inline code needs just one backtick before and after.

@anotherusername said in Mr. Musk, you tease us...:

Not closing an <a name> is really no big deal. It keeps going and going and going, but nobody's going to notice because it's not styled any differently.

Not normally, no, but:—

A {
color: blue;
text-decoration: underline;
}

[Gąska]

@anotherusername said in Mr. Musk, you tease us...:

@Tsaukpaetra said in Mr. Musk, you tease us...:

@Gąska said in Mr. Musk, you tease us...:

@Gurth said in Mr. Musk, you tease us...:

<a name=foo><h2>Bar</h2>
<!--​ Note lack of quotes and </a> -->

Whaaaa? How did the parser even work with that? Did </a> close the nearest <a>, or just the one with href, or what? How were children elements determined?

Remember that thing about parsing HTML with regex? And how it's almost impossible? Examples like this are why.

Not closing an <a name> is really no big deal. It keeps going and going and going, but nobody's going to notice because it's not styled any differently.

Okay, now this is really retarded. <a name> is styled like regular text because it performs no function other than being an anchor. <a href> is styled like a link because it's clickable and gets you somewhere. But <a>, which also performs no function, isn't styled like that other a that perform no function, but rather like this clickable thing that takes you somewhere - even though it doesn't take you anywhere? Nevermind, I was wrong.

[Luhmann]

@Gurth said in Mr. Musk, you tease us...:

Je mag het wat mij betreft best in het Nederlands uitleggen als je dat makkelijker vindt …

En Vlaams?

[Gąska]

@Luhmann jasny holender o czym oni tam szprechają.

[Applied Mediocrity]

Vēl tik vienīg leļļu teātrī runā šitajās jocīgās valodās, it kā mutē būtu ieņēmuši kaķu spalvas kamolu.

[Luhmann]

@Applied-Mediocrity
Ach wat maalt het? Grootste pluspunt is dat we die lijperds van de andere kant van de plas weer een kloot kunnen afdraaien.

[Applied Mediocrity]

@Luhmann
Pilnīgi piekrītu. Barankas cauruma enerģētiskā vērtība ir izsakāma kā tā rādiuss reiz vidukļa apkārtmērs vai arī pēc metodes leņķis-mala-leņķis.

[Zecc]

@Applied-Mediocrity

Bacon ipsum dolor amet shankle turducken prosciutto tail, andouille shank filet mignon capicola tongue jowl. Shoulder bresaola short loin pork chop bacon tri-tip. Tri-tip spare ribs sirloin short ribs bacon tongue cow pork belly.

[Benjamin Hall]

@Applied-Mediocrity upvote for Lithuanian. Or at least something that looks Lithuanian.

[Applied Mediocrity]

@Benjamin-Hall
Upvoted for being close, but no cigar.

Anyway, I got carried away. We were deliberating on whether Elon Musk invented HTML? Right then.

[PleegWat]

@Luhmann tut, tut, tut, wat een taalgebruik.

[Luhmann]

@PleegWat
Dacht dat het anders hollands genoeg was

[anotherusername]

@Gąska said in Mr. Musk, you tease us...:

@anotherusername said in Mr. Musk, you tease us...:

@Tsaukpaetra said in Mr. Musk, you tease us...:

@Gąska said in Mr. Musk, you tease us...:

@Gurth said in Mr. Musk, you tease us...:

<a name=foo><h2>Bar</h2>
<!--​ Note lack of quotes and </a> -->

Whaaaa? How did the parser even work with that? Did </a> close the nearest <a>, or just the one with href, or what? How were children elements determined?

Remember that thing about parsing HTML with regex? And how it's almost impossible? Examples like this are why.

Not closing an <a name> is really no big deal. It keeps going and going and going, but nobody's going to notice because it's not styled any differently.

Okay, now this is really retarded. <a name> is styled like regular text because it performs no function other than being an anchor. <a href> is styled like a link because it's clickable and gets you somewhere. But <a>, which also performs no function, isn't styled like that other a that perform no function, but rather like this clickable thing that takes you somewhere - even though it doesn't take you anywhere?

You certainly can style it differently (and NodeBB's stylesheet has styled it), but it isn't by default.

[Gąska]

@anotherusername I stand corrected.

[Polygeekery]

@gordonjcp said in Mr. Musk, you tease us...:

@gleemonk I don't know, here we have a guy with the money to pay people who can build him spaceships, and a stated aim to Get To Mars Or Die Trying...