Earlier quoted context omitted.
What percent of people regularly use them as tablets without the keyboard?
I think there are several different characteristics that make us categorise a device as a tablet vs. a laptop, input methods being just one of them; there are many others e.g. form-factor, weight, battery life etc.
Google’s not-so-secret new OS
461–470 of 561 posts
Re: Google’s not-so-secret new OS
#462So Google is going with a DartVM on this one. Dart is cool and all, but why DartVM? It's the same restrictive model we have with Android (dalvikVM) where you can only develop with languages that can compile down to Java bytecode. In this case, however, we will be using languages that can transpile to Dart source instead! Why not JavaScript engine? With the current movement with WebAssembly, I see a lot potential use…
Re: Google’s not-so-secret new OS
#463So Google is going with a DartVM on this one. Dart is cool and all, but why DartVM? It's the same restrictive model we have with Android (dalvikVM) where you can only develop with languages that can compile down to Java bytecode. In this case, however, we will be using languages that can transpile to Dart source instead! Why not JavaScript engine? With the current movement with WebAssembly, I see a lot potential use…
Dart can compile to JS, so that edge is covered. Dart bytecode is arguably an easier target for other language compilers than, say, assembly. The DartVM's byte code is fully specified, there is some adoption, it's openly accessible, and there's a bold, production-ready reference implementation. For wasm, only half of that is true.
Re: Google’s not-so-secret new OS
#464Earlier quoted context omitted.
Yes, but when you talk to regular people and their needs for web pages, apps, they are often either very trivial or unbearably complex. You can potentially automate away those very trivial with the current state of ML already, and there is a bulk of money there that goes to a lot of independent developers and smaller companies. And once you have such a system built, you can extend it as new advances in ML/GPU come, a…
Yes, some are very easy to implement, just look at squarespace's customers. One could build an NLP interface (bot?) to configure squarespace sites and this would take you quite far. Not sure I'd call that AI though.
It's not general AI but even less-than-general AI can erode our ability to earn money from developing software.
Re: Google’s not-so-secret new OS
#465Re: Google’s not-so-secret new OS
#466Earlier quoted context omitted.
Is there any research on how many do that across Europe, including new devices versus 2nd hand ones?
My anecdoticat evidence from even poor European countries suggest phones are renewed quite often (~2years). The horrible manufacturing quality of most modern devices ensures the market for 2nd hand devices stays small, because these things break easily. To be honest, subjected to a "mildly aggressive & negligent" usage pattern, like mine, even an iphone will barely last more than 3 years and it will be in "far from g…
I think most people are more like me, but there are indeed a non-negligible segment of the population like you (and my sister) who just destroy their phones. Based on everything I've seen, it's definitely more of a you thing than a modern phone thing.
Re: Google’s not-so-secret new OS
#467Re: Google’s not-so-secret new OS
#468I use Andromeda equivalently with Fuchsia in this article. Andromeda could refer to combining Android and Chrome OS in general, but it's all the same OS for phones, laptops, etc. - Fuchsia. I make no claims about what the final marketing names will be. Andromeda could simply be the first version of Fuchsia, and conveniently starts with "A." Google could also market the PC OS with a different name than for the mobile OS, or any number of alternatives. I have no idea. We'll see.
Re: Google’s not-so-secret new OS
#469Earlier quoted context omitted.
You listed windowing/UI concerns. And, while they may commonly come bundled with the OS, they're not the same thing.
They're a platform concern. Not only does the OS UI reflect the input method, every single application you run does as well. A touch-optimized application will be clumsy and primitive when using a mouse; a mouse-optimized application will be miserable when using a finger. If an application can be written once for both, often it'll be a poor compromise or only properly support one of the two input methods. Look at how…
I think a single OS for them all is fine.
Consider gnome+linux vs android+linux. They're both linux, and they're not the same platform.