191–200 of 276 posts
Earlier quoted context omitted.
>nothing will ever be good enough for them again. Reading this made me so sad. This is exactly how I feel. Nothing will ever be good enough again. :(
There are certain devices like this, right? A similar thing happens with the HP-15C calculator, it was so sought after in eBay, etc., that HP even made a special edition a few years ago.
Earlier quoted context omitted.
I've heard of sailfish before, but I had NO idea sailfish is somewhat maemo based. This really makes me want to reconsider the Jolla phone.
Sailfish is based on Meego, which was a merge of Maemo and another project. It was the OS that backed the N9, the last phone Nokia made before they went to MS.
The other project was called Moblin. It was an Intel project.
It's a shame the N950 never got a proper release. The N9 got praised highly on release, but the N950 would've been the true successor to the N900.
If I understand correctly, this is a user environment. What OS does it run on? A Linux distro? Android? I don't see that detail mentioned on the site. Perhaps people familiar with KDE and Plasma know, but I don't. Or perhaps I'm overlooking something obvious ... EDIT: Wikipedia says that Plasma is a desktop environment, not an OS, and that "Plasma Mobile is a Plasma variant for smartphones". https://en.wikipedia.org/…
But for some reason they use marketing language to make it look like they have invented some new mobile OS.
By the way, it doesn't look very secure:
- first, you have to unlock the bootloader. It means you can install custom firmware but anyone having physical access to your phone can do it too.
- Google did a lot to make Android more secure. For example, every application is run under a separate user account to protect it from other (potentially malicious) applications. Applications' privileges are restricted. KDE doesn't have such features.
So if you like KDE or want to run or maybe write KDE applications this project will help you. But you'll have to forget about security and I guess the project is in early development stage now so there can be bugs and something might not work.
The power of things like this taking off is not what they are now, but what they can be. There are lots of real people with their own good reasons to not be tied to Google/Apple, and whats really impressive here is that unlike firefox OS, they are (in my opinion) doing this in a much better way. As this catches on, it only helps improve linux hardware (ARM) support, telephony applications for linux, and the like. As…
The trouble isn't the software. I'd gladly jump onto Ubuntu Touch and wanted to try out FireFox OS when it was still maintained, but the trouble is the hardware. I didn't want to buy a Nexus, which seems like the only device that's the first to be supported by any alt-OS. Back in the late 90s/early 2000s, you could just run Linux on your x86. Sometimes half your hardware didn't work, but as long as you could get Ethe…
Earlier quoted context omitted.
I used to have that. It was my Nokia n900. I was able to pull up live thumbnail previews of all apps running in the background, and this included live simultaneous previews of: youtube videos in a web browser, games, and Debian, without lag. Try doing that on today's technology. It had a wonderfully acurate resistive touch screen that was pressure senstive that was really good for drawing and coloring! The camera wou…
Google made a huge mistake choosing to base Android on Java, IMHO. I know they did it because they felt it would be easier to get developers on board but it's the main reason Android is slow and memory hungry. OSes like Plasma prove that compiling binaries for ARM processors is not a big problem and that compiled code runs much faster. Java byte code may have the potential to run close to native speed but in practice…
Android is 100% native code since that version.
Even the changes in Android 7, although they use an intepreter written in Assembly, the code is JITed with profile information, both are cached and it gets ultimately fully compiled to native code when the device is charging.
Also in case you didn't notice, Apple is pushing for LLVM bitcode for their newer OS versions.
There is even a BOF on this weeek's LLVM meeting about how to make LLVM IR fully hardware neutral.
Earlier quoted context omitted.
I spent $300+ (way too much!) for my n900 and I still think it was worth it. It was my replacement for my tmobile g1 phone. The n900 is everything that I thought the g1 was going to be, but wasn't. In a way, it was my fault for blindly creating my own hype over a first generation product I knew nothing about. The g1 turned out to be my bad and disappointing foray into smart phones. Also, yes I have heard of the neo90…
I wouldn't be so sure. There are a lot of N900 users and fans. Another interesting project which might fill my desire for a true mobile computer (if only I could afford it) is the Pyra, the more powerful successor to the Pandora. But at $~500-$~600, it may not be worth it, and it still hasn't actually released yet (although the company did make the Pandora, so they have a history of Getting Stuff Done). If you're goi…
Earlier quoted context omitted.
The content on the page does a very poor job of explaining what it is and why we should care. It's only until I saw the KDE developers at the bottom that I realised it's a graphical desktop environment but for your mobile phone. It's FOSS so it's hackable, as in you have access to the source code and development is done in the open and contributions are encouraged. The target developer phone seems to be the LG Nexus…
Yea, the Plasma Mobile home page doesn't really make a strong pitch towards a potential user. For mobile developers, the biggest difference is that they'd be using the Qt framework instead of the Android framework. So the pitch at least for mobile developers, should be why it's a more pleasant and better (and more productive) experience to develop mobile apps with Qt vs the Android frameworks. I'm not how much better…
Hello, Main plasma mobile developer here, I wanted to reply some questions that surfaced in comments and give a bit of overview on current state and where we need help. We initially based it on Ubuntu Touch, and later on started using our own stack based on Cyanogenmod, more information on it at : http://blog.bshah.in/2016/05/02/plasma-mobile-new-base-syste... So basically currently Plasma Mobile is made of, - KDE Fr…
Earlier quoted context omitted.
Google made a huge mistake choosing to base Android on Java, IMHO. I know they did it because they felt it would be easier to get developers on board but it's the main reason Android is slow and memory hungry. OSes like Plasma prove that compiling binaries for ARM processors is not a big problem and that compiled code runs much faster. Java byte code may have the potential to run close to native speed but in practice…
The code is written in Java, but a technical note: it's actually compiled to bytecode for the Dalvik runtime (and later, the Android runtime). Your points are still relevant, don't get me wrong, but the system isn't running Java bytecode specifically.