473 karma · joined August 15, 2017
Shortly after uploading them, I received a string of emails from Google indicating that those files had been flagged for copyright infringement...
the automated email notification she received offered no way to push back against the determination of Google's content vetting algorithm – the Request a Review button was not included in the message she received ...
The e-mail explicitly said 'A review cannot be requested for this restriction,'"
How far does pattern this need to go, before someone changes direction?
...and at least consumers in that are not the customers, but the product...
https://github.com/electron/electron/blob/main/LICENSE
So everyone can use it without the need to expose his IP.
- language: ES / Typescript are quite established
- CSS: also quite established
- Frameworks: there is still a lot of innovation here, but also React / Vue / Angular are quite established.
on that latter part I prefer the innovation. Let's just imagine for a while what UI would look like if we only had Swing (Java) or QT (C++)
At least for Google most of the time the end user is not the customer, the advertiser is.
This has various reasons, one of them being economics, another one being end user psychology.
Also for Amazon this is more and more becoming the case, as sellers and businesses using their services contribute much more to Amazons margin than an end user does.
The rest follows pretty much automatically from the internal incentive structures of those companies, which are dominated by share value increases.
<center style="font-size: 18px">...
is it now web1?
This is not a universally true statement. It is only true when you don't have enough information. The statement confuses the physical world with our mental representation of it.
one could argue, that programming languages that are more close to the mind are more efficient. At least when looking at 2nd to n-th order efficiency effects, not just pure runtime performance.
const App = ( <div> <h1>Hello Bitcoin!</h1> </div> );
curious about version 0.0.2 ;-)
Let [customer group] do [pain point solved].
I think, a "model" tag is a good and forward compatible path