rajington
Joined 15 years ago
Joined 15 years ago
I especially like the explicit url parameter passing vs. others where it just magically shows up in your component.
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.
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.
Take this example music video:
https://www.youtube.com/watch?v=6vopR3ys8Kw
Frames:
https://img.youtube.com/vi/6vopR3ys8Kw/0.jpg
https://img.youtube.com/vi/6vopR3ys8Kw/1.jpg
https://img.youtube.com/vi/6vopR3ys8Kw/2.jpg
https://img.youtube.com/vi/6vopR3ys8Kw/3.jpg
And this lyrics video version (more interesting because it's SOMEWHAT changing):
https://www.youtube.com/watch?v=FoAqHxm5dpo
Frames:
https://img.youtube.com/vi/FoAqHxm5dpo/0.jpg
https://img.youtube.com/vi/FoAqHxm5dpo/1.jpg
https://img.youtube.com/vi/FoAqHxm5dpo/2.jpg
https://img.youtube.com/vi/FoAqHxm5dpo/3.jpg
Simply finding the differences between frames would give the first video a higher score than the second.
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.
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 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.
> Users should have the freedom to choose where their data resides and who is allowed to access it by decoupling content from the application itself.