Because Chromium isn't in the Google Play Store, so you can't "just get" it?
There's an unofficial, test, "use at your own risk", "untested" APK that one can download from the Chromium website and side-load onto their Android device. But that's a lot more difficult than just installing it via Play Store.
Because Kodi sucks compared to Plex? Especially when it comes to multi-screen/multi-user setups with everything stored/managed on a single server. Or if you want to access your media from outside of the house.
Eh, it still works without any issues, it's in the bedroom, and really only used when we're too sick to walk downstairs. Why get rid of a perfectly working TV?
Eventually, we'll replace the lowly 39" LCD downstairs with something larger, move that one into the bedroom, and move the CRT into the kids' room with the NES, SNES, and Wii.
At that point, I'll have to replace the Athlon64 with something that can handle 720p or 1080p. Until then, we'll just keep on rocking.
and wish their kids only listened to the good stuff they grew up with. my dad grew up with classic rock and hated 80's metal bands that i listened to. listening to rap around him was likely to get you a beating
"Classic" means "at least 25 years ago". Guess what qualifies as "Classic Rock" now?
Pretty sure the pre-80s rock can now be classified as "Pre-historic Rock".
Tsk, tsk, tsk. Such a wasted opportunity.
Should have been:
"Know what I like even more than video articles?"
"Tune in tomorrow to see
One of our HTPCs is rocking an Athlon64 with an All-in-Wonder 9800 AGP card. One of the last ones to support component video out. Plugged into a 27" CRT. Works great for Plex Web client (via Google Chrome).
The main server in the house is a Phenom-II something-or-other. With a lowly, silent Nvidia 210 GPU for transcoding videos as needed via Plex Mediaserver.
Neither system is CPU-bound, or even GPU-bound, for what they do. The lowly 1 TB SATA drives in the server (even in a 4-disk RAID10) are the bottleneck. Not worth upgrading the motherboard, CPU, or GPU until those get upgraded or replaced.
Except it's been shown that orgasm released chemicals in the brain that can eliminate most headaches. So the correct come back to "Not tonight, I have a headache" is "Excellent, because I have the cure for that in my pants".
If you think Smirnoff makes good vodka that's worth spending money on, then I'm sorry to say that you're the chump. Smirnoff is swill, and you can taste it in anything you mix it with. You shouldn't be able to taste vodka, that's kind of the point of vodka. If you can taste vodka, they screwed up somewhere. And you can definitely taste Smirnoff
A great way to taste test vodka is to stick it in the freezer overnight (all vodka should be refrigerated, as should most tequilas). Then take a couple shots the next day, letting the liquid linger in your mouth a bit. If you cringe, snort, sniff, cough, or spit, it's crap vodka. And Smirnoff will make you do all of that.
Sure, if you just want to get smashed, Smirnoff will do. But if you want to actually enjoy your drinks, you'll avoid Smirnoff.
There's a very big difference between a $6 bottle of random vodka on the back shelf of a gas station in butt-fuck-nowhere Iowa, and a $40 bottle of Grey Goose. One you can taste, no matter how duluted you make the drink; the other you won't taste no matter how strong you make the drink.
Granted, not all $40 bottles of vodka are better than the $6 bottle. Just as not all $40 bottles of whiskey are better than the $6 bottles. But some most definitely are!
He also had issues with scene length.
4-6 were ok. Scenes were fairly long, with decent amounts of dialogue and/or action in them. And the transitions between scenes were fairly smooth.
1-3 were horribly short (it felt like 30-45 seconds at most), with crazy transition effects. The action jumped around so quickly most of the time you didn't really know where you were or what was going on. It was like watching a PowerPoint presentation where the class assignment was "how many transition effects can you squeeze into a 2 minute presentation".
Surface RT and Surface 2 (the previous versions of the Surface tablet) used ARM-based SoCs.
Surface 3 uses an Intel Atom x7 SoC.
Don't confuse these with the Surface Pro tablets which have used Intel Core i3, i5, i7 CPUs (depending on version).
Only 100 MHz, and using 100 MHz of spectrum. Most carriers in North America are lucky to have 10-20 MHz of contiguous spectrum, and maybe 40 MHz total usable spectrum in a specific area. Good luck finding 100 MHz of spectrum to use anywhere other than lab conditions.
Would be nice if they worked on increasing the number of bits that can be transferred per MHz of spectrum, instead of increasing the amount of spectrum required to send the bits.
Unless you used an Amiga or MacOS, if you played a sound, that was it - no one else could play a sound (MacOS and Amiga had software mixers so you could listen to music AND hear application generated sounds - you could use exclusive mode if you needed it, though).
FreeBSD 4.x, also from the 90s, allowed you to play multiple sounds simultaneously. It used the same OSS code that Linux used
Fixing "exclusive sound" issues on Linux shouldn't have required a 10+ year commitment; but nobody wanted to fix OSS-on-Linux.
And your networking options were... single. You either had Ethernet, or a modem, and only one IP per host. And rarely did you move - I mean, if you were on Ethernet, it was assumed you were on the same network permanently, or at least changes were rare.
Been running wireless on laptops since the days of the Orinoco Silver and Orinoco Gold PCMCIA cards (aka before 802.11b). Windows 9x and FreeBSD never had issues with them. Plug the card in, dhclient runs, you have Internet access. Remove the card, connect the Ethernet cable, dhclient runs, and you have Internet access. Moving between networks would (rightly so) drop running connections, but everything worked. It did require a bit of manual configuration for the wireless side of things, but that was all in a single configuration file and easy to manage. And it got even easier in the early 802.11g days with the advent of wpa_supplicant.conf
Again, Linux devs and their NIH syndrome saw them go through multiple different wireless stacks, multiple different ways to configure things, and things were a mess! Each wireless driver included its own wireless networking stack, for pete's sake. And what you configured to work with one driver wouldn't work with the next. There was no centralised configuration file for wireless on Linux, although Debian got close with their wpa_supplicant extensions to
Users haven't gotten more complicated; nor have use-cases. But Linux desktop developers have certainly developed more complex cases of NIH and are constantly re-writing everything "just because", thus overly-complicating things. Things are not better now than they were 15 years ago on the Linux desktop. Especially not compared to other OSes out there. Even the other F/OSS OSes.
Sony bases the PlayStation 3 and 4 OSes on FreeBSD. And the Xbox runs a variant of Windows.
Other than some Android-based handhelds and micro-consoles, there's next to no Linux in gaming consoles.
Depends on the app and the phone. Some phones, like the Nexus 5/LG G2, have hardware step counters that apps can use instead of the accelerometer/GPS. Those phones and apps barely touch your battery at all, and are significantly more accurate than the rest.
Without life, Biology itself would be impossible.
