phponpcp

They do. There are many, many millionaires created by NFTs and collectors who are buying millions of dollars of NFTs.

That's a great way to get sued. Already happened when SolBlocks took art from Artblocks and profited on it.

Does it bother anyone else that Google is basically saying "How can we use race/gender as a driver for selling phones."

What's silly is not embracing new ways of making your art a revenue stream so that you can live off of it.

Check out IPFS, this is already happening in the NFT world. Have you noticed how all NFTs are high quality and not compressed to shit? That's because of the IPFS.

I saw it too, and IMO the ecosystem is better than ever now. It took a few years of stagnation for SF to really dig their hooks in, but everything is nice and integrated now.

I dont know about that... Twitter has a huge problem of leftwing extremism.

You do for full width retina images on 1440p+ monitors.

"I don't remember React being the very clear choice until probably 2017."

Maybe you werent paying attention then.

Is the new FB even live yet?

Performance on complex vector graphics is abysmal with Inkscape :(

This is so much easier to parse too. If you need more rigidity, add BEM on top then you're good to go.

"but I'm not willing to install and use npm and several hundred dependencies"

Good luck being a employable lol

Having a disjointed UI is a huge risk of dropping conversions. So yeah, it does matter.

Obtrusive scroll bars by default screw up certain CSS rules like 100vw. So that's why it matters.

The point that they didn't raise is that scrollbars effect the size and position of things in the browser. Try setting 100vw on an element when you have obtrusive scrollbars, the result will be a page which now has horizontal scrolling, leading to terrible UX.

Spoken like someone in a truly insular bubble. Go spend any amount of time in a city with an arts college.

The new RPi has like 4gb of RAM tho

Gee that sounds awesome when I'm trying to watch the local news at 9AM in the morning.

It's all about the use case. If you're on an ecommerce website and click between category and PDP pages 5-10 times browsing, a SPA is going to make that transaction an order of magnitude faster. Since you're only loading the smallest possible payload (JSON) that contains only the things that have changed, it is optimized in a way that is never going to be achievable with server-side rendering.

At least that's why I opted to push for a SPA.

That doesn't scale after awhile. Generally the next step is putting your business logic in HOCs or Redux thunks or sagas. Now it can be dropped in hooks too.

Literally none of those things apply to React though.

Yeah I dont know about that. If you've ever had to deal with optimizing event delegation and updating the DOM without causing massive repaints you'd change your tune.

Benchmarking on low-end devices to prove your point is situational at best in my opinion. For example if you work at a luxury ecommerce brand, you can assume that most users who actually are going to buy something are going to be using a flagship model device.

Lol now that you mention this, it makes the React community make way more sense to me.

Awesome, advertising is terrible.

Because being rich is awesome. And if you're rich, you can do whatever you want, including helping overs if that's your prerogative.

Then this breaks in older browsers because forEach isn't a method on a NodeList. So you have to polyfill in features to do [...document.querySelectorAll('.tpm_sensors')].forEach(...);