excellent collection, what's the closest to functional graphql directives you've come across so far? i think directives are really going to unlock the power of graphql, and replace a lot of code with something more declarative
JS will eventually support types natively and will be similar to TS/Flow's API. I have more faith in ReasonML taking off than Dart/Flutter but I hope I'm wrong.
- React and React Native, even ReactXP/react-native-web if appropriate
Vue is good but not good enough to convince most of the community and the community makes it. Their native strategy needs more work, and it's too valuable not to have one.
- Apollo Client
So much boilerplate disappears, and it's powerful enough to be your one data source which enforces many best practices and capabilities.
- GraphQL Gateway stitching GraphQL Servers and serverless resolvers
GraphQL/serverless does for the backend via microservices what React did for the frontend via components. The benefits to the entire stack are countless. Apollo Server (even AppSync) make it simple.
- A serverless datastore
There's also many great GraphQL ORMs but managing infrastructure/scaling should be avoided.
Two months with the Pixelbook i7, don't regret investing that much on a Chromebook, which was my main concern. Kept the old MBP just in case and it's been just sitting there, even through tax season.
Pretty happy with performance, Linux apps work well but still "feel" a little out of place. Very like how it runs Android apps, so much works but it's just the issues that DO come up that can be frustrating. If you're not ready for that experience then it might not make sense to switch your main dev machine.
Doubt I'll ever buy a laptop bigger than this one ever again, but it is a little harder to dev directly on this, mainly bc of that MBP trackpad, but this keyboard is MUCH better.
I had a similar problem previously and considered automating it by comparing frames. It's not easy and would have obvious false positives/negatives, but YouTube does help by publishing key frames and it could at least be used to help rank results.
I see us at the beginning of a path that grants magic powers, controlling everything with our voice, or even our intention.
That requires machine learning, which requires data, which requires data collection, and the closest one to Google there isn't Apple or Amazon, it's Facebook.
This is worthy of a bug bounty, and I feel it should be handled as such: reported privately to them first. The people trying to hack reCaptcha at scale are not good people.
The temporary fix Google might have to do in the mean time however is to stop all audio reCaptchas, blocking the people who vitally depend on it.
I really don't know if SDCs would become commoditized, lots of startups doing it are more indicative that they're all trying to win rather than be a small player in a large industry. VCs in the area are probably betting on acquisitions, I think it'll be incredibly hard for that space to be more than two or three top players.
I just wanted to give a positive comment, specifically about the things that people are giving negative comments about. The website design isn't boring, and emphasizes that the app differentiator is that it's looking to be a better design and have things like "album art first".
Electron does have a small resource problem, but that doesn't stop plenty of people from downloading the desktop version of Slack, or other popular electron wrappers. There's a reason a lot of people put up with Electron, it fills a gap.
Whether you did this to try Electron or design, comments on HN can be very subjective and not representative of actual reception. I personally never thought album art was super important cause I grew up with Napster, but like "cover flow" was REALLY well received. Artistic design is especially highly opinionated.
