A combination of vw and vh were ultimately how I decided to tackle the problem. I'm very happy with the amount of control and flexibility I ended up with on my slightly design heavy website.
Viewport-relative widths are a poor practice for accessibility, in general (maybe you don't care for your small personal website). The user can't set their own preferred size, font-size becomes illegible at small sizes, and way too large on large viewports (2160px is becoming more common). It breaks zoom on some browsers as well.
The clamp() examples here mitigate that somewhat, but why do we need fluid shifts in text size? Just use media queries.
Well it's just a little film about a magician, a 'guesser'. To be honest I think I wrote that mostly because I'd watched it the night before! But as a magician I recon you would enjoy it. :)
I feel many of the comments here are akin to saying "laying out in documents latex is hard, if you can't figure it out you're not ready to write" while the author of the article is saying "I think writing documents could be easier." Google docs is proof it's possible.
Sure everyone could learn about $path with a little research but there is SO MUCH to learn to get started with a "simple" react app... It's not necessary.
Great tools hands a "low floor AND a high ceiling" meaning it's easy to get started and possible to go really really far.
Clearly tools like replies show there's a desire for easier to set up environments.
Have you never wished you could save your css tweaks directly from chrome dev tools?
Why should the browser show you the page source when you could just curl it? Well... Let's try to make the unimportant things EASY so we can focus on the useful parts.
Firefox could absolutely come with a standard node server and editor. And it could integrate with providers like GitHub or netlify.
> Firefox could absolutely come with a standard node server and editor
A node server runs JavaScript files as do browser engines and the majority of node’s API exists in the browser in a similar form, as well as an editor. GitHub as well comes with an editor built-in, Netlify can be connected to GitHub by clicking one button.
I agree that it’s good to simplify, but are these good examples for that?
I'm open to feedback! Mostly.... did it work? I build a lot of things and it's hard to find people to "practice" on. I'd prefer if you don't share how it's done yet... I'll be posting an explanation on that soon :-)
I'd expect latency might be juuust in the range where it doesn't feel interactive yet? But honestly any search that isn't ripgrep or --omg-optimized-etags feels like that to me now, and people use symbol rename features in IDEs all the time that take multiple seconds, so maybe I'm just unreasonably picky.
I'm a magician who invents new technology at a FAANG.
I've started posting podcasts showing how I use the magician's toolset to invent new technology that's focused on doing the impossible in a way that meets users needs and dreams!
Https://magicseth.com/