I wrote JavaScript to avoid JavaScript

#1

Post by asaaki » Sun, Nov 08, 2020, 6:30 AM UTC

I wrote JavaScript to avoid JavaScript
markentier.tech

Re: I wrote JavaScript to avoid JavaScript

#2

Post by ochronus » Sun, Nov 08, 2020, 10:03 AM UTC

Nice! Pagespeed Insights is also happy with your site ;) I especially liked the new format stats, pretty impressive. Now if only I found a good node module for avif conversion...

Re: I wrote JavaScript to avoid JavaScript

#3

Post by asaaki » Sun, Nov 08, 2020, 10:25 AM UTC

ochronus wrote: post #2

Nice! Pagespeed Insights is also happy with your site ;) I especially liked the new format stats, pretty impressive. Now if only I found a good node module for avif conversion...

Thanks.

If you're okay with a non-node/js solution, use https://github.com/kornelski/cavif-rs - it does the job for me pretty well.

For node it looks surprisingly disappointing right now, the only real candidates being the packages @saschazar/wasm-avif (v1.0.0) and avif (v0.0.1-alpha2) — I'll probably never understand the ecosystem and community, the format is out for some time and fully supported in the most widely used browser, yet barely noticeable support in the JS world.

Re: I wrote JavaScript to avoid JavaScript

#4

Post by ochronus » Sun, Nov 08, 2020, 10:50 AM UTC

asaaki wrote: post #3

ochronus wrote: post #2

Nice! Pagespeed Insights is also happy with your site ;) I especially liked the new format stats, pretty impressive. Now if only I found a good node module for avif conversion...

Thanks. If you're okay with a non-node/js solution, use https://github.com/kornelski/cavif-rs - it does the job for me pretty well. For node it looks surprisingly disappointing right now, the only real candidates being the packages @saschazar/wasm-avif (v1.0.0) and avif (v0.0.1-alpha2) — I'll probably never understand the ecosystem and community, the format is out for some time and fully supported in the most widely…

Thanks for the tips - I'm tied to node at the moment - wasm-avif has serious issues with thready safety an memleaks :( tried it.

Re: I wrote JavaScript to avoid JavaScript

#5

Post by asaaki » Sun, Nov 08, 2020, 6:59 PM UTC

ochronus wrote: post #4

asaaki wrote: post #3

Earlier quoted context omitted.

Thanks. If you're okay with a non-node/js solution, use https://github.com/kornelski/cavif-rs - it does the job for me pretty well. For node it looks surprisingly disappointing right now, the only real candidates being the packages @saschazar/wasm-avif (v1.0.0) and avif (v0.0.1-alpha2) — I'll probably never understand the ecosystem and community, the format is out for some time and fully supported in the most widely…

Thanks for the tips - I'm tied to node at the moment - wasm-avif has serious issues with thready safety an memleaks :( tried it.

If you're in control of the environment, you might want to consider the yak shaving road and build a node package with a C, C++ or Rust library then. ;-)

Re: I wrote JavaScript to avoid JavaScript

#6

Post by anonymoushn » Mon, Nov 09, 2020, 8:57 AM UTC

On OSX Chrome, this page is always horizontally scrollable because the navbar is wider than the rest of the content by a margin of the vertical scrollbar's width. You can set max-width: 100% on the navbar to fix this.

Re: I wrote JavaScript to avoid JavaScript

#7

Post by Dionakra » Mon, Nov 09, 2020, 9:07 AM UTC

I did almost the same last weekend. I wanted to start a blog[1] but all options seemed too much for a simple purpose that is a blog. After researching about VuePress, Sapper, Next.js, Gatsby and so on, I finally decided that it wouldn't have any kind of JavaScript. I was tempted to create yet another static site generator, but I am sticking to the old HTML + CSS duo (and, regarding CSS, classless CSS) for my blog. Yes, it has some downsides, but hey, it only needs a text editor and internet connection and the blog is blazingly fast.

[1] https://boix.dev/

Re: I wrote JavaScript to avoid JavaScript

#8

Post by nodelessness » Mon, Nov 09, 2020, 9:36 AM UTC

He used the stones to destroy the stones.

Re: I wrote JavaScript to avoid JavaScript

#9

Post by gbrindisi » Mon, Nov 09, 2020, 9:37 AM UTC

Wonderful! I am so irritated with JavaScript bloat... completely unnecessary cruft 99% of the time.

I built my blog with the goal to have zero js but I had to capitulate for google analytics.

The blog is a static website deployed on a CDN and I have no access to access.log - I honestly couldn’t find any analytics solution that won’t require js.

Re: I wrote JavaScript to avoid JavaScript

#10

Post by chrismorgan » Mon, Nov 09, 2020, 9:46 AM UTC

gbrindisi wrote: post #9

Wonderful! I am so irritated with JavaScript bloat... completely unnecessary cruft 99% of the time. I built my blog with the goal to have zero js but I had to capitulate for google analytics. The blog is a static website deployed on a CDN and I have no access to access.log - I honestly couldn’t find any analytics solution that won’t require js.

> I had to capitulate for google analytics.

Ask yourself how much you actually need analytics. I found I seldom looked at it. I myself replaced Google Analytics with self-hosted Matomo for a while, but then I just dropped it altogether because I simply don’t need it. Now I do have server logs that I can look at, and from time to time I do (and they reveal things like Atom feeds consume the substantial majority of the traffic and page loads, which client-side JS logging would never have revealed!), but it wouldn’t bother me to have no analytics at all.