I love this page. Text, photos, links. Straight up HTML 4, maybe even using a template in a text editor and FTPed to go live. I didn't see any inline or referenced CSS. No scripts. No ads. No social junk. The home page even has a just like it's 1994. What are the drawbacks to reverting to this type web publishing? That's how I used to do things before publishing tools and CMS and platforms took over, but I know the s…
The main drawback with the page's unstyled design is that the page is not mobile friendly. Publishing web pages by manually editing HTML files is still very common today; any GitHub Pages blog does this.
Upper stage impacting the moon on 2026 August 5
31–40 of 89 posts
Re: Upper stage impacting the moon on 2026 August 5
#32someone send them a littering bill sadly one day hundreds of years from now parts of the moon will look like all the garbage left on Everest (and maybe even the dead frozen bodies too, moon dust is sticky and very sharp apparently)
Also what's the alternative? Moon missions don't have enough extra propellant to go back to earth and deorbit. They might have enough to move to a relatively stable orbit, but then it's just long-lived orbital debris.
Re: Upper stage impacting the moon on 2026 August 5
#33I love this page. Text, photos, links. Straight up HTML 4, maybe even using a template in a text editor and FTPed to go live. I didn't see any inline or referenced CSS. No scripts. No ads. No social junk. The home page even has a just like it's 1994. What are the drawbacks to reverting to this type web publishing? That's how I used to do things before publishing tools and CMS and platforms took over, but I know the s…
The main drawback with the page's unstyled design is that the page is not mobile friendly. Publishing web pages by manually editing HTML files is still very common today; any GitHub Pages blog does this.
Re: Upper stage impacting the moon on 2026 August 5
#34Earlier quoted context omitted.
The main drawback with the page's unstyled design is that the page is not mobile friendly. Publishing web pages by manually editing HTML files is still very common today; any GitHub Pages blog does this.
What part of this is actually not mobile friendly? I’d argue this is laid out pretty well compared to some websites that are “mobile friendly” but load poorly or make it impossible to scroll.
Re: Upper stage impacting the moon on 2026 August 5
#35I love this page. Text, photos, links. Straight up HTML 4, maybe even using a template in a text editor and FTPed to go live. I didn't see any inline or referenced CSS. No scripts. No ads. No social junk. The home page even has a just like it's 1994. What are the drawbacks to reverting to this type web publishing? That's how I used to do things before publishing tools and CMS and platforms took over, but I know the s…
The main drawback with the page's unstyled design is that the page is not mobile friendly. Publishing web pages by manually editing HTML files is still very common today; any GitHub Pages blog does this.
It's sorta hard to read text that spans the whole screen and at least on mobile, that's not nearly as wide.
Re: Upper stage impacting the moon on 2026 August 5
#36I love this page. Text, photos, links. Straight up HTML 4, maybe even using a template in a text editor and FTPed to go live. I didn't see any inline or referenced CSS. No scripts. No ads. No social junk. The home page even has a just like it's 1994. What are the drawbacks to reverting to this type web publishing? That's how I used to do things before publishing tools and CMS and platforms took over, but I know the s…
The main drawback with the page's unstyled design is that the page is not mobile friendly. Publishing web pages by manually editing HTML files is still very common today; any GitHub Pages blog does this.
It’s not what I’d call mobile unfriendly either.
I had to zoom in slightly but then it’s perfectly readable in landscape.
Some very basic inline responsive CSS would make it work great in portrait too.
But the thing is, with no ads, complex layout, or other bullshit, it’s perfectly usable on mobile as is.
I’d certainly take this over any website from any major media outlet, other than those that are publicly funded like the BBC (and, even then, only in the UK because they show ads everywhere else).
Re: Upper stage impacting the moon on 2026 August 5
#37something they didn't mention, what is in this upper stage? I'm presuming a rocket motor and some fuel is that right..? They do a calculation of energy release on impact, but I'm wondering if there is any fuel left and whether that would affect their equation?
Re: Upper stage impacting the moon on 2026 August 5
#38Re: Upper stage impacting the moon on 2026 August 5
#39I love this page. Text, photos, links. Straight up HTML 4, maybe even using a template in a text editor and FTPed to go live. I didn't see any inline or referenced CSS. No scripts. No ads. No social junk. The home page even has a just like it's 1994. What are the drawbacks to reverting to this type web publishing? That's how I used to do things before publishing tools and CMS and platforms took over, but I know the s…
The main drawback with the page's unstyled design is that the page is not mobile friendly. Publishing web pages by manually editing HTML files is still very common today; any GitHub Pages blog does this.
Then fix mobile browsers to display it correctly.
Re: Upper stage impacting the moon on 2026 August 5
#40Earlier quoted context omitted.
The main drawback with the page's unstyled design is that the page is not mobile friendly. Publishing web pages by manually editing HTML files is still very common today; any GitHub Pages blog does this.
In this pages case, I disagree. I feel like when pages try to force their 'aspect ratio / styling' to fit the view port I have to fight more with it. at least as it stands I can zoom as needed on this page, I can appreciate the web devs 'vision' as in how it probably appeared on their machine. I honestly hate mobile sites unless they are done just super super well which is harder than expected. https://rockauto.com i…
Except it does not, for some weird reason unstyled pages like this which should look great on mobile look like ass. Why are mobile browsers defaults so wrong?
This hits hard because this is how I build my pages (you can probably tell I am not a front end designer) I just want to put well structured content out and let the users agent display it in the manner that suits the user best. And it mostly works, it will not win any awards but it looks fine. Until someone asks why it looks like the dog's breakfast on mobile.