News for hackers. Stuff that matters.
Re:Let's create a Tree-sitter grammar by tillcarlos on Wednesday March 20, 2024 @01:43AM (#39763175)
(unrelated to content) Wow, that site speed!

In the footer there’s a link to OPs source code. The whole site gets compiled with Rust. Interesting gem to find.

Re:Let's create a Tree-sitter grammar by prabir on Wednesday March 20, 2024 @02:19AM (#39763354)
I did the same with my blog which is written in rust https://github.com/prabirshrestha/rblog. While it could be static I wanted it to be server. But I don't think rust is the reason for it. Not depending on external resources such as fonts and javascript for critical path along with compression is the most critical. Since it is a blog focus on text instead of fancy images and only include when absolutely necessary. Testing the site in Fast 3G or Slow 3G is the best way to find the places where you can optimize your site.
Re:Let's create a Tree-sitter grammar by juanrgon on Wednesday March 20, 2024 @01:48AM (#39763205)
It’s a static site. It would be strange if it wasn’t fast
Re:Let's create a Tree-sitter grammar by codethatwerks on Wednesday March 20, 2024 @04:45AM (#39764065)
It is hard to make a slow one. Even shared hosting wordpress with the cache turned on is fast.
Re:Let's create a Tree-sitter grammar by viraptor on Wednesday March 20, 2024 @06:44AM (#39764786)
You'd think so... There's so many versions of WP caching and so many ways it's deployed, that (with a fairly small experience) I've seen sites taking 5s+ to load after enabling the relevant option because suddenly minimisation and bundling kicked in on every request and kept the page fresh. WP is trivial to make accidentally slow.
Re:Let's create a Tree-sitter grammar by lawn on Wednesday March 20, 2024 @01:47AM (#39763197)
Static sites are a breath of fresh air in this day and age.
Re:Let's create a Tree-sitter grammar by emmanueloga_ on Wednesday March 20, 2024 @05:27AM (#39764350)
The only nitpick is that the site loads 1.2Mb of fonts... apparently through CloudFront. It seems it serves them uncompressed, perhaps because the fonts are woff2? [1]

Also, the bold version of iosevka is an order of magnitud heavier than the other fonts :-).

--

1: https://docs.aws.amazon.com/AmazonCloudFront/latest/Develope...