News for hackers. Stuff that matters.
[dead]
Re:I bootstrapped my private-journaling project into a lifes... by dang on Tuesday June 25, 2019 @01:43PM (#20276784)
Re:I bootstrapped my private-journaling project into a lifes... by a13n on Tuesday June 25, 2019 @01:48PM (#20276838)
Yes sir, sorry Dan.

Does saying a website doesn't work with JS disabled count as flamebait? This feels like a flamewar to me.

Re:I bootstrapped my private-journaling project into a lifes... by dang on Tuesday June 25, 2019 @02:35PM (#20277375)
People interpret these terms differently but you're at least in the right ballpark. At minimum it's a generic tangent, and those always lead to tedious, predictable discussions, and often flamewars. That's why the guidelines bundle the two:

"Eschew flamebait. Don't introduce flamewar topics unless you have something genuinely new to say. Avoid unrelated controversies and generic tangents."

Re:I bootstrapped my private-journaling project into a lifes... by komali2 on Tuesday June 25, 2019 @01:17PM (#20276493)
I understand why you feel justified in this tone, because it would be absurd to assume a web application could work without Javascript in 2019.

But like... a static blog post? Why bother with JS at all? It seems like creating more work that necessary, bloating downloads, increasing load speed, and for no reason blocking out people with JS disabled (so like, not just people using Firefox with plugins, but people that browse from emacs or whatever... which seems weird, except those are exactly the kind of people that are also technologists building 20k side projects). Also makes accessibility harder than necessary.

Re:I bootstrapped my private-journaling project into a lifes... by a13n on Tuesday June 25, 2019 @01:24PM (#20276574)
Indie Hackers is so much more than just a site with static content. There are user accounts and voting and commenting, just for starters.

The market of people who disable JS is minuscule and very likely not worth the effort to serve.

If you choose to disable a core web technology, then you should expect that many sites will not work for you.

Re:I bootstrapped my private-journaling project into a lifes... by RHSeeger on Tuesday June 25, 2019 @01:31PM (#20276659)
> If you choose to disable a core web technology, then you should expect that many sites will not work for you.

If you choose to disable a core web technology, then you should expect that many users will not work with you.

Re:I bootstrapped my private-journaling project into a lifes... by carlosdp on Tuesday June 25, 2019 @01:41PM (#20276763)
Part of the point before was that it's actually not many though...
Re:I bootstrapped my private-journaling project into a lifes... by beat on Tuesday June 25, 2019 @01:39PM (#20276748)
And since browsing the web via emacs is a huge market encompassing possibly upwards of .001% of all web traffic...
Re:I bootstrapped my private-journaling project into a lifes... by komali2 on Tuesday June 25, 2019 @01:59PM (#20276961)
Or more if we're talking about the slice of the market that are of the type to be interested in indie hacking projects... aka exactly the sort of people that want a editor they can hack on, or whatever.
Re:I bootstrapped my private-journaling project into a lifes... by beat on Tuesday June 25, 2019 @02:18PM (#20277170)
That makes it, what, .01%? I haven't read the web via emacs since the 1990s.
Re:I bootstrapped my private-journaling project into a lifes... by paulryanrogers on Tuesday June 25, 2019 @01:17PM (#20276490)
No need for the patronizing tone. Some block JS for the same reason others block ads: security and faster load times.

Is it really too much to ask for a single <NoScript> tag on the home page explaining what the service is and why JS is necessary?

Re:I bootstrapped my private-journaling project into a lifes... by dymk on Tuesday June 25, 2019 @01:25PM (#20276580)
Yeah, I think it's a bit much to ask every single website on the internet that uses JavaScript to add a tag for the incredibly small demographic that is NoScript users.
Re:I bootstrapped my private-journaling project into a lifes... by komali2 on Tuesday June 25, 2019 @01:29PM (#20276641)
https://gds.blog.gov.uk/2013/10/21/how-many-people-are-missi...

1%. Of all people.

Except... maybe your content is targeting exactly the kind of people to wander around the internet with Javascript disabled, and then they're suddenly a much larger slice of your potential audience. Writing articles on engineering, I imagine, already increases that slice. Anything related to security, I imagine another increase. People that participate in Indie Hacking Projects.... another big slice.

Anyway, why not just make it a part of that big ol blob of meta tags we all copy over to every index.html we write anyway? Including the magical bit of viewport meta to make pages look good on mobile?

Re:I bootstrapped my private-journaling project into a lifes... by tracker1 on Tuesday June 25, 2019 @01:32PM (#20276678)
I'm working on several applications that only support browsers with ES2017 (async) and above... That said, for mostly static content, there's very little excuse not to do server renders. I mean this stuff isn't new, and dynamic bits can be attached after render. Hell, most of the interaction beyond the text content I'd be fine with.

One thing that REALLY bugs me, is blocking usage of analytics systems that you cannot access a site without it. Makes the site unusable if the analytics are blocked or otherwise fail to load. I keep JS on, but will be damned if I shut of uBlock.