Skip to main content

Show HN: I ranked news websites by speed https://ift.tt/wfnQMUI

Show HN: I ranked news websites by speed I've been working on building "the fastest news website" for a few reasons: 1. I got tired of waiting for news websites to load, so I made a text-only news website that only has major news headlines. 2. I wanted to demonstrate to the world that if you want to build something really fast on the web, you can do it without loads of JavaScript. 3. I wanted to show that you can design something that looks good without having tons of images, etc. I put together the speed page at https://ift.tt/IUtTZAC to hold my website to be more accountable for speed, but it's also interesting to see how fast other news websites are (or in most cases, are not). Some feedback I'm interested in receiving: 1. What's your take both on the speed ranking methodology for Legible News? 2. Are my descriptions of the metrics for a non-web developer reasonable? Example of that at https://ift.tt/2hxBKdH , and if you click through the links on that table, you see a description like https://ift.tt/DQPYElI Sorry ahead of time, but I can't fit all news websites on the speed report. I had to target general news websites, not ones for specific niches like HN for Tech. If there's something you think that's missing please post it, but I can't promise that I'll add it. If you like it, please consider subscribing! Thanks! https://ift.tt/IUtTZAC June 28, 2022 at 11:05PM

Comments

Popular posts from this blog

Show HN: TypeScript query builder with full type inference https://ift.tt/xZp9HOm

Show HN: TypeScript query builder with full type inference Hey HN! Colin here - a TypeScripter, open sourcer, and engineer at EdgeDB. As the creator of Zod and tRPC, I'm interested in designing tools/APIs that use type inference and generics to make life easier for devs. This query builder represents another step in that direction. We set out to build an EdgeQL query builder that can express queries of arbitrary complexity (EdgeQL has feature parity with SQL, roughly) and infer the static type of the query result. We introspect the database and generate a schema-aware client that represent any query, including ones that use built-in functions, operators, string/array/tuple indexing, aggregations, conditionals, type casting, subqueries, computed properties, etc—things most ORMs can’t represent. This post mostly discusses the API design, which I think will be interesting regardless of familiarity with EdgeQL. I’d love to see some of these ideas bleed into future generations of TypeSc...