Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
The apps either didn't exist or were featureless, including Microsoft's own ones. Needless to say, I was happy to go back to Android
Then you'll be pleased to discover that Lollipop's new Material Design aesthetic also aims to eliminate all visual features. And just so you don't miss out, most of the Google apps in KitKat have also been updated with Material Design.
Slashdot is disposable. It's just news that I saw days ago on Hacker News, combined with oh-no-it's-Bennett, and idiotic articles from Dice. The comments are sometimes fun, but frankly, I don't know you nor really care about you. Hacker News has comments, too, with a different moderation system.
I see plenty of English speakers learning Chinese. A lot of them never learn "proper" English. But I work in San Francisco with the children of Chinese immigrants. Even the elected mayor is a child of Chinese immigrants, now.
Going back to the OP, the current entrenchment is no guarantee. 100 years ago, everybody who wanted to do science learned German. 300 years ago, everybody learned French. 600 years ago, everybody in the West learned Latin. 2000 years ago, everybody in the Mediterranean learned Greek. For most of that time, everybody in China learned Chinese.
Resolution though is largely irrelevant to most usages - it's the physical size of the screen real estate that matters.
Let's compromise: Both physical size and resolution matter. You're not getting a lot of work done on an old-school 240p Apple II screen, no matter how big it is.
There are many limits against low resolutions. I can totally read a 14-pixel-tall 'a' much faster than a 6-pixel-tall 'a' and more pixels would be even better. You can see a lot more content when your icons, that need to be at least 12 pixels tall to be recognizable, use 1/100 of your screen instead of 1/20. I used computers in the 1980's. I remember what they looked like. Using more than 50 pixels for 'a' is a bit silly, though.
Resolution makes a difference when you're working with stuff that is laid out like pages. Ever tried to read a PDF in less than 1000 horizontal pixels? I did. It's illegible. On the typical 1080p widescreen monitor, you split that 1920 pixels horizontally between 2 windows, and you get only 960 pixels per window. That's not enough resolution to see an entire page reasonably.
I have a 20-inch 1600x1200 monitor that I run in portrait mode with 1 program on screen at a time. 1200 pixels is frequently not enough, unless I'm doing work in classical terminals. 2560x1440 would allow me to show multiple programs at the same time, less need for portrait mode, and 3840x2160 would be great.
For me, the biggest issue is that most videos still require Flash.
Google is the biggest hypocrite here. One part of the company paid a lot of money to promote patent-free video on the Internet, but the YouTube team won't use it for music videos and prefers to use Flash even when HTML5 <video> is available. The Chrome team not only backpedaled on removing patent-encumbered <video>, but also partnered with Microsoft and Netflix to bring DRM into the HTML5 standard.
My practice is to use Google Chrome when I really do need Flash or some other Google monstrosity, but otherwise keep that browser closed.
Oh, come on, it's not just that. It's also PulseAudio, also from Poettering, and udev, from RedHat's Kay Sievers, and how glibc emphasizes performance over security, from (formerly) RedHat's Ulrich Drepper, and possibly some of the silliness around RedHat-funded KVM, and the NIH silliness around ZFS vs (Oracle) btrfs, and dtrace vs strace/ftrace/whatever, and the performance of NetFilter and its proposed replacement nftables vs BSD's pf...
systemd might be the straw that breaks the camel's back, but there are many areas where someone might have issues with Linux. Personally, I'm not that invested in it either way, so I'm most swayed by software and hardware compatibility, where Linux wins really, really big. Though, I wonder what sort of reality distortion bubble RedHat is projecting around their developers, that so many of the issues are with RedHat stuff.
> I refuse to support PowerVR outside of iOS, so I'm going to sit this one out.
Somebody on maemo.org quoted a Jolla employee from IRC as saying, it will be an Intel GPU.
Even better, The Register found somebody from Intel to claim that it's an Atom 3700 series device, meaning Bay Trail. Now I'm much more interested in this device, but I'm still inclined to wait until firm confirmation.
And ONLY 2 GB of RAM? What's the fucking point of including a 64-bit processor?
A couple points that come to mind:
- Better performance per clock, due to instruction set simplification and larger working set of registers.
- Slightly better security, because of more address space to do ASLR.
- Finally enough address space to mmap everything. If your memory usage is dominated by static assets like graphics, this would allow you to use the operating system's virtual memory paging to handle which assets are in RAM at any time.
They don't explicitly say, but it looks very much like they're using a Moorefield system, like the Nokia N1. The PowerVR graphics in the Moorefield benchmark well on Android, but it's no good.
The PowerVR drivers are closed-source, the company is hostile to open source, and even on Android the performance is inconsistent. See page 2 of Ars Technica's review of the Nexus Player. And in Jolla, the device driver is not native to the operating system, but goes through libhybris.
I refuse to support PowerVR outside of iOS, so I'm going to sit this one out.
Honestly, every year, twice a year, the DST haters come out of the woodwork, because apparently adjusting your clocks twice a year is soooooo difficult.
You're an idiot (from Greek: "idios," meaning someone thinking only of yourself). Just because you find it so relaxing to change your clocks on cue like an animal in a circus, doesn't mean I want to do that.
There's nothing magic about the clocks in smartphones and computers. Those things take a lot of human labor to build and maintain, and frequently the humans make mistakes. Which you can't fix because with all that "magic," they leave out the manual controls. Or have you forgotten how iPhones sometimes make people late to meetings, or how Zunes used to die completely, or how every new program that deals with local time acts weird during the time switches, or how your unpatched system would show you the wrong time for about a month ever since this latest time switch?
I hate experiencing anxiety every time I get a new gadget that has a magical networked clock, wondering whether the clock will change correctly, or whether I'll unnecessarily wake early in the autumn or come to work late in the spring. That's on top of the general misery of changing my biological clock, and knowing that all this hassle is scientifically proven to be wrong and counterproductive but still it continues.
I don't mind having more sunlight in the afternoon. I hate changing the clock.
I don't care whether it's DST all year or standard time all year, but I hate switching back and forth. It's responsible for so much loss of life and productivity. I feel that DST switching is a twice yearly reminder that our "betters" in Congress are in charge and easily capable of messing with our lives. Until it's eliminated, I'll continue voting against my local Representative and Senators.
Yours wouldn't be the first software that has become abandonware. Users may appreciate the stability of an unchanging release. If it's distributed under a Libre license, then it can be forked and redistributed, but chances are that kids would rather make their own mistakes than work on your program.
Argh! No! CUPS did not originally come from Apple, and Apple did not own CUPS back in 2000. Apple bought CUPS and its main developer in 2007.
I notice Apple protocols such as AirPlay and AirPrint, the whole Designed for iPhone licensing system, and how Apple is going out of their way to avoid any GPLv3 software such as Samba 3.
Oops, I meant Samba 4. Starting in MacOS X 10.7 Lion, Apple has used the closed-source SMBX instead of Samba to provide SMB service, and Apple's SMB client is licensed under APSL 2.0, which is not compatible with GPL. Apple's SMB software has also been slower and buggier than Samba.
I think Apple's aversion to GPLv3 is wrongheaded, as is Google's avoidance of GPL in Android other than the kernel. I'm not saying that it's evil, just a mistake.