phponpcp

5 ms·

1.
by phponpcp 5y ago
They do. There are many, many millionaires created by NFTs and collectors who are buying millions of dollars of NFTs.
2.
by phponpcp 5y ago
That's a great way to get sued. Already happened when SolBlocks took art from Artblocks and profited on it.
3.
by phponpcp 5y ago
Does it bother anyone else that Google is basically saying "How can we use race/gender as a driver for selling phones."
4.
by phponpcp 5y ago
What's silly is not embracing new ways of making your art a revenue stream so that you can live off of it.
5.
by phponpcp 5y ago
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.
6.
by phponpcp 5y ago
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.
7.
by phponpcp 6y ago
I dont know about that... Twitter has a huge problem of leftwing extremism.
8.
by phponpcp 6y ago
You do for full width retina images on 1440p+ monitors.
9.
by phponpcp 6y ago
"I don't remember React being the very clear choice until probably 2017." Maybe you werent paying attention then.
10.
by phponpcp 6y ago
Is the new FB even live yet?
11.
by phponpcp 6y ago
Performance on complex vector graphics is abysmal with Inkscape :(
12.
by phponpcp 7y ago
This is so much easier to parse too. If you need more rigidity, add BEM on top then you're good to go.
13.
by phponpcp 7y ago
"but I'm not willing to install and use npm and several hundred dependencies" Good luck being a employable lol
14.
by phponpcp 7y ago
Having a disjointed UI is a huge risk of dropping conversions. So yeah, it does matter.
15.
The sad state of Daisy Chaining monitors on OS X(medium.com)
4 points by phponpcp 7y ago|0 comments
16.
by phponpcp 7y ago
Obtrusive scroll bars by default screw up certain CSS rules like 100vw. So that's why it matters.
17.
by phponpcp 7y ago
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
18.
by phponpcp 7y ago
Spoken like someone in a truly insular bubble. Go spend any amount of time in a city with an arts college.
19.
by phponpcp 7y ago
The new RPi has like 4gb of RAM tho
20.
by phponpcp 7y ago
Gee that sounds awesome when I'm trying to watch the local news at 9AM in the morning.
21.
Stale Props and Zombie Components(react-redux.js.org)
1 points by phponpcp 7y ago|1 comments
22.
by phponpcp 7y ago
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
23.
by phponpcp 7y ago
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.
24.
by phponpcp 7y ago
Literally none of those things apply to React though.
25.
by phponpcp 7y ago
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.
26.
by phponpcp 7y ago
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 fl
27.
by phponpcp 8y ago
Lol now that you mention this, it makes the React community make way more sense to me.
28.
by phponpcp 8y ago
Awesome, advertising is terrible.
29.
by phponpcp 8y ago
Because being rich is awesome. And if you're rich, you can do whatever you want, including helping overs if that's your prerogative.
30.
by phponpcp 8y ago
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(...);

More ›