stereobooster
Online demo: https://facets-demo.stereobooster.com/
Show HN: Hiring Process
Function vs. Object
Show HN: Dev.wtf – Developer's Reference
Show HN: Type Systems FAQ
TypeScript: Type vs. Interface
Introduction: From Function to Closure
Show HN: The Button
Fullscreen mobile modal: how hard can it be?
What are types (in type systems)?
How to Handle JSON Based APIs in FlowType and TypeScript
Opaque types and how they could have saved Mars Climate Orbiter
Small practical guide on Flow and TypeScript for JavaScript developers
> The discussion on performance is too focused on mobile
Because mobile users have a slower internet connection and worse CPUs.
What kind of performance are you talking about? If load performance, then this component uses well-established techniques (not invented by me), like lazy-loading (known since jQuery times), srcset (web standard), LQIP (used by Facebook, Medium), width, height (required for all blocks in AMP).
If you are talking about JS performance like frame rate or paint or "junk" on the scroll - I didn't measure it but didn't say it was the first target either.
This component allows to retry image load (click on it).
It can be even more smart, like if network is good go ahead and download everything. Need to think about it
> maybe default max width of 100% on mobile?
It is.
> optional ability to overlay an empty full size block so the image cant easily be right clicked and saved
Not sure what you mean, but as soon as image loaded it turns into good old image, so you can do right click