This is the reason why I pay for Dropbox to host my pictures. The problem with Google is often not about severe privacy problems, it's about 'you never know' and getting educated and finding the right setting is hassle everytime. Worse here is FB.
My brain says never, for everything there is some turn-key thing. Even your entire project might be franksteined with some third-party products and Zapier into something working. Same with libs, better a crappy lib than working days for something you might not need.
My gut says always: most of the times turn-key stuff has weaknesses and good libs with perfect apis, well maintained and with a great community are rare but they are there of course.
Hard question since what the gut says is more fun while the alternative is just about gluing libs together. But using libs and once they don't fulfill your needs build yourself is the right but more boring way to go.
Your brain is falling into the classic JS/NPM trap of thinking that dependencies are zero cost. The time it takes to use something is not 0, there's still a comparison to make. There's tons of stuff out there with APIs, documentation and community resources that are way more complex to navigate than whipping out a text editor and building something that handles your own use case.
You are nitpicking and TBH I don't get your message. My post was a general advice and the tendency of a creative mind, still you need to look into each case and decide if make or buy. And your NPM trap analogy is just blatantly wrong and doesn't help OP. You could have mentioned any package manager btw.
I'm not nitpicking, I just picked out the first part of your post because it's the only bit I disagree with.
I'm saying it's dangerous to have this line of thought that the "correct" way to build a system is with a mish mash of third party libraries and that doing any non-glue coding yourself is only for fun. You're insinuating that the decision OP is making is between efficiency and fun, whereas in reality it's an optimisation problem for efficiency that a lot of people mess up because they don't understand one side of the equation. (and if OP wants to have fun and roll his own that's great but it's another case entirely, I'm assuming he's not asking HN for permission to do that).
I use NPM as an example because for JS devs in the places I visit it's becoming a cultural thing, which IME is not the case in other communities. I don't see as many python devs entertain the thought of maintaining something for years with "crappy libraries" in it for the sake of saving "days" of work. But in JS land that attitude is all over the place and the phrasing of the first bit of your post reminded me of it, so...
Ports are good and what Apple does is ridiculous but it is also about which ports.
Nowadays, I tend to miss real Thunderbolt 3 ports on USB-C, better 2 than 1 and with 4 lanes. This is what they totally forgot. So I could connect to an ancient VGA projector but not to a common 2x 4k@60hz display setup? This doesn't make sense.
"Unfortunately, Vaio commits a huge blunder when it comes to the fan control. Ideally, the fan should not run at all while the device is idling. The opposite is true for the Vaio SX14: The fan always runs with 32.5 dB(a), which is definitely audible. Under load, the fan becomes much louder with 43.9 dB(a), which is annoyingly loud."
I really like some VAIO models, as I think quality is superior to Thinkpad. So I wish they took a bit more care with these issues. Their recent fanless convertible suffers from coil whine. Some online reviews discuss this too.
Ok good to know. Fan control is super important, the only one managing this well with different and really working profiles seems to be Dell. Lenovo just started to get better there (with the S940 which is quiet but because of heavy throttling and no options for profiles, however better than the way around).
Desktop and web versions are in the making. So we will be able to make all of them from a single codebase.
I am really dependent on static types so take my take on this with a grain of salt :)
Flutter is more mature right from the Dev tools to the overall ecosystem. The types are first class and make it a joy to use. Not to mention the libraries are better quality and stuff works even when you upgrade. I could never work on any RN project for more than 1-2 weeks without something or the other breaking and me cursing out aloud for the really shitty (again subjective) state of things. I am used to having codebases just keep on working almost forever.
IDK what you mean but there so many things much easier and straightforward with web-based tech, eg sane layout systems like flexbox are way superior than anything native frameworks have to offer.
The Discord devs use RN and their app is anything but experimental or small. And there are by far not the only one (Skype, Instagram, Wix, UberEats, Tesla, Baidu, Salesforce).
Native devs don’t like RN because the mobile dev supply gets bigger which hurts their market value. That’s the real reason of your post, spreading FUD.
RN has its limitations but for 80% of apps it’s absolutely fine.
Please stop with the market value/FUD attacks, they are nonsense and childish. You clearly have an axe to grind.
I don't like RN because I have had to sunset multiple large projects in RN. Javascript is a mess for mobile development. The interaction between the native layer is a mess. Hell, it's still not even a 1.0 release yet - smart CTOs would be insane to suggest it as a tool. Just look at the upgrade guides they post - a mess.
