6 ms·
Probably true, and I'm so glad we have Apple in this industry. Otherwise everything would be optimized for ease of development instead of the end user experienc
by tambourine_man 9y ago
Probably true, and I'm so glad we have Apple in this industry. Otherwise everything would be optimized for ease of development instead of the end user experience.
- chrisper 9y agoElectron phone apps everywhere. That would be horrible.
- ex3ndr 9y agoTo be honest React Native is Electron for mobile. On Android it starts custom Chrome engine in it.
- ashark 9y agoThat might explain how they got around the horror that is trying have have complex, flexible styling across several major Android versions without every single thing you do being entirely broken on one or another. I'd wondered why the various things I'd tried kept actually working. That'd do it.
- eropple 9y agoI don't believe that this is accurate. It starts a V8 engine, not a Chrome engine, and renders (on the standard framework UI loop) using--as one would expect--native controls. If you want to use a WebView, you must invoke a WebView.
- amelius 9y ago> It starts a V8 engine, not a Chrome engine And that V8 engine contains functionality which is surprisingly similar to Chrome. Except they decided to reinvent the wheel.
- flai 9y agoYou are aware that chrome uses V8, not the other way around?
- eropple 9y agoI don't know if you're aware, but Chrome uses V8 to provide that functionality. Perhaps this is a Chesterton's Fence situation you should think about a bit? (Though, as the sibling comment notes, it uses JavaScriptCore, which is Webkit's JavaScript engine, not V8 at all.)
- amelius 9y agoSorry, I'm fully aware of what V8 is (I actually embedded V8 once myself). By "V8 engine", I meant an engine containing V8, among other things such as a renderer. Bad wording, my mistake.
- eropple 9y agoReact Native doesn't contain a renderer in the Chrome-y sense of the term, to the best of my knowledge. It wraps native APIs instead. Am I missing something?
- cobar 9y agoThey actually ported JavascriptCore over to Android. The only time it uses V8 is if you run the code through the Chrome Debugger. Not sure what the benefit was perhaps performance or lower disk usage.
- eropple 9y agoAh, TIL - I pretty much always have the Chrome debugger attached, so that's interesting. :)
- htormey 9y agoNope. React native doesn't use webviews to render its ui. Business logic and view configuration are in JavaScript but all rendering and event processing is done in native. Also it's easy to wrap native components and insert them, something you just can't do in a webview.
- jasonkostempski 9y agoBut the end user experience is still shit on iOS, it's just a more specialized kind of shit, delivered through a fancy sphincter.
- eecc 9y agoPlease elaborate... I've been on iOS since the iPhone4 and didn't notice the smell
- fredsir 9y agoHow is it shit? There's always room for improvement, but it's not shit if you ask me. In my opinion it's the best mobile OS we've got.
- jasonkostempski 9y agoWalled garden, monopolistic practices, favoritism, planned obsolescence. None of these things are a net gain for the end user. They do it better than anyone else, but it's still the same shit.
- scarface74 9y ago"planned obsolescence"? The latest version of iOS runs on all iOS devices back to the iPhone 5 -- introduced in 2012. How many Android phones still get updates from their manufacturer 5 years later? When Apple releases a security patch, it's available from day one to all users worldwide over the air. Can you say the same for Android?
- deleted 9y ago[deleted]
- sqeaky 9y agoI hold no opinion on "planned obsolescence", rather I want to separate OS from vendors. Vendor support is not a feature of the software it is a feature of the Vendor. Android is open for anyone to do anything with, and there is no way to force someone to support something after they release it any more than it is possible to get them to not use Android in the first place. If we look at Apple, Samsung, LG, HTC, etc... independently as companies I am sure some have crappy upgrade policies and some have great policies. If you want shop around for it, look at reviews for other phones. If you don't want it, like if you are planning on installing your own OS or have other plans for the hardware then this is misfeature. It becomes a thing you have paid for but will never use.
- ashark 9y agoExactly my first thought on reading the headline. "Oh, really? Then thanks for prioritizing my battery life and general UX over cheaper app development, Apple!"
- mitchty 9y agoExactly. I remember hearing "eight megs and constantly swapping" as a joke, I think for anything javascript app related I can now say: 8 watts and constantly increasing The amount of energy javascript pages now take makes me in some ways wish we had the ease of blocking crap like flash back in the day to not make my fans spin. Also a webpage or app taking up 900MiB of memory? Really, this is what I want? Hell no, i'll stick to what I have thank you very much. Certain web developers are an interesting breed of late.
- thehardsphere 9y ago>Certain web developers are an interesting breed of late. We live in an age of unparalleled abundance. "Evolution" no longer selects as aggressively against devs who are inefficient.
- wolfgke 9y ago> "Evolution" no longer selects as aggressively against devs who are inefficient. It still does - but now efficiency is measured in development/maintenance time.
- ElijahLynn 9y agoApple is hampering web apps. I am so not glad we have Apple in the industry slowing things down. They didn't mention anything web related at the last WWDC. The web is the future, not their little sandboxed world.
- eridius 9y agoWhy are you expect Apple to announce web-related stuff at WWDC? Besides the fact that the web isn't really what WWDC attendees care about, WebKit is also open source and you can watch development happening. Yes, sometimes Apple does work on a big thing that doesn't actually land on the open source project until they announce it, but that's usually when it's being done to support some other hardware or OS feature that they haven't announced yet. If you want to see what's going on in WebKit, just check out https://webkit.org https://webkit.org. A simple way to follow along is to read the "What's New In Safari Technology Preview ##" blog posts (and install the Safari Technology Preview to actually try this stuff out).
- ElijahLynn 9y agoBecause they used to announce web-related things at WWDC. e.g. https://developer.apple.com/videos/play/wwdc2013/601/ https://developer.apple.com/videos/play/wwdc2013/601/
- eridius 9y agoYeah, and last year they had a session called Extending your App with Safari App Extensions (https://developer.apple.com/videos/play/wwdc2016/214/ https://developer.apple.com/videos/play/wwdc2016/214/), as well as Apple Pay on the Web (https://developer.apple.com/videos/play/wwdc2016/703/ https://developer.apple.com/videos/play/wwdc2016/703/). So they still do have the occasional web-related session. But for the most part there's not much need to be talking about web stuff at WWDC, because most development of the web stuff happens in the open already throughout the entire year, and WWDC isn't being attended by web developers anyway, it's being attended by app developers.