fgkramer

You could track if users actually try to read the rest of the article.

I was just using a simple analogy to explain that currency != exchangers

How are dollars worth anything after all the bank robberies across the years? :)

Maybe is up to implementation? I've got an X and the intent to pay pops up the native pay modal, which still requires you to double press the power button AND to be authenticated. So what you say never really happens.

I'd actually pay for it.

I'm tempted to say JS is not the biggest problem between browsers, but CSS... the fact that valid CSS code behaves differently and that it cannot be fixed without changing most of it. Not even mentioning if you actually need to change your DOM structure to make a layout work.

Are you on a mac? 99% of times it's because of an external mouse connected.

edit: the css for the element that overflows has: `grid-template-columns: 50vw 50vw;` and based on the spec: https://www.w3.org/TR/css3-values/#viewport-relative-lengths, scrollbars are not taken into account, therefore as long as you have a _forced_ scrollbar, the content WILL overflow regardless of your screen size.

By forced I mean a scrollbar you cannot remove and that's not enforced by your systems settings, you can clearly see this behaviour on mac if you toggle the "Show scroll bars" setting to "Always".

Safari and webkit based browsers can avoid this issues with `::-webkit-scrollbar{ display: none}` but it's not a cross browser solution nor a wise decision to hide scrollbars overall.

Isn't success defined by your own metrics at the end of the day? You need to choose what are the things you are willing to tolerate/live with and what is your end goal in life.

It's hard nowadays to define such thing with so much information around, moulding what a "successful" life should look like, how should it feel and where should it be lived.

It's up to us to define what we care about and how to measure our happiness.

As always, good reading material: https://www.goodreads.com/book/show/28257707-the-subtle-art-...

I think that what they mean is not to use Django's templates, but to use it as an API server. Django's DRF is one of the easiest ways to create and maintain resource endpoints.

Nginx would serve the index.html with the scripts and the React components would request their data to the API.

This of course doesn't consider SSR'd React as it is just to get started, but the community is working on it (see pipy's projects)

Not OP, but it is usually done by using support tags:

https://developer.mozilla.org/en-US/docs/Web/CSS/@supports

You'd write two versions, one for browsers which do support grid and one for the ones which don't.

Jen Simmons has written excellent tutorials on doing fallbacks and explaining how we can use css grids nowadays: https://hacks.mozilla.org/2016/08/using-feature-queries-in-c...

And also has a YouTube channel where she explains a lot on how to deal with css grid in the wild: https://www.youtube.com/channel/UC7TizprGknbDalbHplROtag