I remember when it started, trolls were telling me how my React Native stack is bad and how active flutter's github is, how it was trending with stars. I'm like bro, having way more issues than stars isn't something to be proud of. LOL
Well said! Pasting my comment from Facebook where this was reposted:
---
Idiots. The new monitor and stand isn't made for you. Not even you, clueless Engadget journalist. It's made for graphics, movie studio pros whose company pay $18000 currently for Reference monitors. Compared to that and the fact that this is 6k with that fancy nano coating, this thing is cheap.
And I'm not buying it, because I don't need it. If you don't understand the price, it's not for you either. Move along.
Agreed. It's all the javascript redirects a dozen times through a dozen ad networks that often kill your data (and battery), and sometimes autoplaying videos too, when you just want to read the damn article.
I've written about what I'm working on which address this in my other comment. I've been secretly trying to scratch my itch for the last 2 years. Love to hear more on what irks you when it comes to mobile search. I've written more at https://medium.com/p/rethink-mobile-search-10-100x-faster-in...
While we are thinking similar in regards to the stupidity of clicking hit-and-miss links on a list of search results on mobile, fussing with history back and forth in browsers, Cake hasn't gone nearly far enough. Our goal is to not render HTML at all, but summarize text extracted from articles. Full browser views are there only as backup. Only then can we achieve something truly remarkable: 10-100x speedup compared to conventional browsers.
In short, we skip the bloat in dealing with the full HTML DOM and Javascript that's been so abused in ads and articles, which signicantly drain your phone battery and slowdown browsing. And then the summaries reduce your cognitive load in cutting through the noise and getting to an answer, faster.
And in the midst of all the social ails surrounding fake news and filter bubbles, I have plans to address those too. I'm just starting to market WonderSwipe after being in stealth developing it for the last 2 years, so even though it's still in private beta, I'd love your ideas and feedback in terms of what I'm proposing. As web search is like consulting the Oracle in ages past, I believe there's no more important issues to address than truly rethinking mobile search and knowledge transfer.
Skill issue.
REST serverless business logic on top and graphql is great