There have absolutely been rapid meme based crowd funding of projects in the past. Crypto enhances it because there are a lot of people who’ve made so much money that handing it out like candy is something they can do, but that really wasn’t new.
Just like MySpace existed when Facebook launched, and no one is using Facebook today.
Seems the biggest Kickstarter ever was Pebble, which raised 20 million USD, while ConsititutionDAO seems to have raised ~49 million USD. That's more than double the funds, even while being on a shorter deadline.
I've been using Brave Browser for almost a year already. I fallback to Chrome when I can't get through some Recaptchas: this is the only annoying thing on Brave, you get a lot of Recaptchas that are invisible on Chrome and some are impossible to solve.
I've also switched to Brave Search immediately when it come out. I'm satisfied with the search results I get for 90% of my queries, switching back to Google for the remaining 10%. My main problems with Brave Search are: 1. It doesn't have good localised results for non-english queries; here Google remains the best; 2. It doesn't have support for verbatim searching
The issue is the developer cannot put his app on another App Store for iPhone users. He should still be able to offer this app to iPhone users, but not on apple’s App Store if they so choose.
With HTTP2's multiplexing feature, it doesn't really matter how many requests the frontend is firing up. Just use HTTP 2 when you have multiple requests on a page.
I think the problem in this case is less the number of requests, and more what it implies. If certain endpoints are even a little slower than they should ideally be to fulfill the requests, you now have a metric ton of not-efficient-enough requests, which adds up very quickly. It's not a problem of making the connection, but the abstraction level.
You could argue, well, fix the API performance right?
That would be a valid suggestion. However, if the API is general purpose, what performance level is acceptable? Should it be able to perform tasks as fast as the average API consumer would expect, or should it be fast enough to serve the UI as well?
It creates a requirements problem in my opinion. If you were to have an API team, is this really on them, or is it on you for trying to use it in a way it wasn't necessarily built for?
This disconnect is why I don't believe a UI should ever be written against a generic API that is data or query heavy. It would involve too much coordination to get it right, which removes the advantage of having components and teams separated in this way (which is often done nowadays).
