3,208 karma · joined August 22, 2011
Related question: Is multi-threading accomplished via these Isolates, or is there a threading model within each Isolate too?
Thanks!
For me, the instability and unopinionated nature of the group of technologies that loosely define "React" have been a real turn off. When answers to questions like "What language should you program in?", "How should you store your data?" and "How should I handle routing between pages?" all have no specific answer, it leads to a fragmentation of knowledge that in my past experience usually leads to a technology's demise.
And a side note, I was a Windows user for a decade and have now been a Mac user for a decade and the level of maintenance required for a Mac is _easily_ an order of magnitude less than Windows.
An example: To install an app for all students on the iPads, we need to plug them all in to a big USB hub, then connect a Mac with management software to it and run a sync procedure. It fails on about 10% of the devices, so we run it again. Each run takes several minutes. There are over-the-air methods for doing this, but they're corporate solutions not provided by Apple and are pretty expensive.
So given all that, if ChromeBooks promise per-user customization and document storage with much simpler administration, it's no wonder they're taking over.
At this point, these kind of problems are on us as a community that we keep using unsafe tools. Every time we choose one of these languages we are implicitly trading security for performance (a.k.a. money).
1) Apple now has most code examples in Swift. 2) Most talks at WWDC are either in Swift only, or with ObjC as the alternative examples. 3) Swift was made available almost 3 years ago. 1.0 was released in Sept 2014. The Swift team was working on it for several years before that. This is now roughly 6 years that the team has been working on it. So when should we consider it stable? 10 years? Longer?
To release a new language, call it the future of iOS development, but also call it "unstable and beta" is a really poor way to treat your developers. I am then stuck between possibly starting a project with an entire deprecated development environment (ObjC), or one that's going to be changing every year forcing me to spend significant time upgrading and possibly introducing bugs.
It seems possible to have a language change and mature in a more sensible way than this, it's just harder and takes more work by the language maintainers. The easy way is just to break everything, which is what Swift is doing.
Whatever happened to graceful deprecation of older language features an APIs? They invalidated all the related example code online and created a ton of mandatory work for all iOS developers within a 1 year timeframe, that's nuts. In my opinion :)
These are the kind of lazy generalization that causes people to make poor technology decisions.
"...prices for lithium-ion batteries have fallen fast — by almost half just since 2014." "But for the most part, according to a BNEF analysis, the costs of new projects would need to drop by half in order to be profitable on a wider scale in California, and that’s not likely to happen for another decade."
The prices for the batteries dropped by half in 2 years, but it will take a decade for them to drop by the same amount again? What am I missing here?
Also the chart seems to indicate the cost was $273/kWh to build a plant in 2016, but then they say "While Tesla declined to provide its pricing data, the similarly sized Altagas project was expected to cost at least $40 million, or $500 per kilowatt hour." I guess the costs unrelated to the battery cells themselves added another ~$230/kWh in costs?
I'm sure you could argue with the dollar amount estimate, but not that it isn't a form of subsidy.
However, one thing everyone agrees on is that most of the mail I receive sucks. :)
For environmental, business efficiency, and personal reasons it seems like we would be better off receiving far less physical mail.
Again, I'm not trying to say that you shouldn't be able to charge for your product, but it has kept me from trying it out so far. Thanks!
Happy to be proven wrong but this has always been the sticking point for me trying this out.
I'm just interested in general - I'm a Mac owner now, but used to be a happy thinkpad owner back in the day.
Or really anything other than this title.