Chromecast all but requires another smart device running (continuously) to control it. You can't control it directly.
Google TV, on the other hand, AKA "Android TV Sticks", are a full-on Android device, just like your phone or tablet, but without the screen. You control it with something like a mouse/keyboard.
You can turn off your phone/laptop while using a Google TV. You can browse the Internet on your Google TV, without using anything else to help. You can plug in a keyboard/mouse and use it like a computer! You buy apps on it from Google play, just like any other android device, and it's very compatible!
I just loved my first TV stick that I bought on Amazon (MK808b) for $35! I just bought an MK809 when my MK808b finally died after 3 or 4 years of daily use, and it has (so far) been a nice upgrade. Faster processor, better wifi reception, more memory/storage. Still runs just fine off the power from the USB port on the side of my TV...
PS: To control one of these, you want a "flying mouse remote". It's a keyboard that "mouses" by waving it in the air.
We've been using Samsung drives in "non production" status servers, embedded servers, etc. and have had a terrible time of it. The first drives we bought a few years ago (840 Pro) were good, but we've seen Samsung SSDs run entirely through their write capacity (as reported by SMART) and then go dead when not even mounted! Turns out we aren't the only ones to get bit by buggy Samsung drives.
My current laptop, a Dell Precision M3800 has it all: light weight, powerful, reasonable (if not fantastic) battery life, 4K screen, and native support for Linux, out of the box but it's hard to figure out what something the same size would be like at 1/4 the weight.
But I'm agreeing with other comments: I'd rather have this exact weight laptop with 3 days of battery life.
A few years back, I bought the phone with the very best battery life and I don't regret it one minute. Now on its third year, the phone still easily powers through a day with 50% or so battery life, and never leaves me high and dry when flying commercially which is when battery life is most important.
My next phone will be the phone with the best battery life Now that I finally have a powerful laptop that isn't also dreadfully heavy, battery life will once again be #1 for my next purchase.
What's sad is that UOP really could have done it! If they offered actual counseling guidance, and curricula that didn't just suck, and made sure that their clients passed classes with rigor, they could have *easily* made a profitable college with good reviews and earned trust.
Instead, they violated that trust, and probably deserve to be shut down.
While they had a good run at first, I won't buy Samsung EVO SSDs any longer. They have had terrible issues with reliability, write amplifications, and trim support on Linux.
I just bought a house. One of the things I was initially pleased to find is that it was built with full-on, 3/4" sheet rock - quality construction!
That is, until I plugged in my wifi router and tried to connect from my bedroom. I don't know what it is about 3/4" sheetrock made in 1978, but it's practically a Faraday cage. I'm contemplating setting up numerous routers with 1-antenna per room so you can get decent access everywhere in the house.
A compromise position in the hall closet gets the bedrooms *almost* OK through the doors...
You make it sound *onerous* but it doesn't need to be. You can buy many home routers with a USB port. Plug in a thumb drive and enable webDAV shares!
We've been using webDAV for many, many years to create a distributed, "cloud based" storage accessible anywhere with good security. (Authenticated webDAV over SSL is approximately as secure as the password)
Microsoft has always been fairly smart about courting developers with excellent tools and development platforms, and making it quite easy to build applications for Windows
Maybe you don't remember history the way I do.
Remember VB? An excellent toolkit that gained widespread acceptance in the Enterprise world for it's tight IDE, integration environment and easy forms. But then MS came out with VB.net which was about as related to VB 6 as javascript is to java. It was a horrible mess, everything had to be re-written to be compatible because it was really an entirely new language. Developers were left in the lurch, oh well, perhaps you shouldn'ta Microsoft, you know?
Remember Silverlight? The "Flash Killer", it was an excellent toolkit for writing distributed applications quickly. Performance was excellent. Many big names "bet the farm" on it. Until Microsoft walked away from it, too. Netflix will *never again* bank on a MS technology, I'm sure.
But that's not where it ends. Remember Windows Phone 7? The next big thing (tm) and they ditched it, for WP8, and all the devs were screwed. Again.
But that's not where it ends. Why is the XBox 360 not compatible with the original XBox? Why is the XBox "One" not compatible with the XBox 360? With every console generation, MS has been screwing the developers.
And so it goes. Over and over, the devs get the shaft any time they bet on Microsoft's newest, highly promoted technology.
What's next?
Re:Excellent. Now how about High Fructose Corn Syr
on
FDA Bans Trans Fat
·
· Score: 1
France banned hydrogenated vegetable oil and saw something like a 30% or 40% reduction in heart attacks... in just a single year. Just how blatant of a good idea do you need this to be?
You're right! When they "went red" they stopped all racism and are now a paradise of integration. Not that the parties themselves have changed ideologies or anything... Nope.
No degree is a guarantee of employment. If you can't be bothered to shower and show up, you're going to have a hard time. Degrees merely improve your odds of success significantly.
Just to be fair "perfectly secure" is probably overstating things considerably. It would pass "no known exploits" pretty well, certainly "commercially viable".
The only "perfectly secure" computer is off, unplugged from the Internet, and encased in 50 feet of reinforced concrete. And even then, there *are* ways to exploit it using *ahem* brute force...
It's easy to design something that people can do. It's tough to design a system that people can't fail at. And that's where there's a big, soft, squishy line that divides what people can generally keep up with and the things that people have to work at to get wrong.
As a software engineer, I require the first, and aim for the latter. It's tough.
My uncle was an BART engineer. He controlled BART ([San Francisco] Bay Area Rapid Transit) trains in the SF Bay Area for a living. The train had doors on both sides of the train and some stations opened on one side, or the other.
BART trains are frequently "up in the air" as much as 50 feet, where the expectation is that you climb a flight or two of stairs to the BART station and board the train. And, for passengers, the doors automatically opened on the correct side so that nobody got hut.
For passengers. But the engineers were expected to manually open the doors on the appropriate side when leaving their station. Now, it's not particularly difficult to look outside the door and see which side the station is on, and the doors for passengers automatically opened on the correct side.
This is where that big, squishy line starts to rear its ugly head. Because while passengers weren't expected to remember which side to get off, engineers were. And my poor uncle made a mistake one day, and opened the wrong side. It was a fatal mistake.
Answer me this: Why would we expect that passengers would never get it right, but engineers would never get it wrong?
Intelligently designed systems that account for and prevent common human mistakes is a design goal. It's tough to do because you have to predict what the end user will likely get wrong and account for that. Nonetheless, it's a hallmark of engineering advancement that we've designed something so safe and resistant to human error as a car that casually travels 100 MPH with as low a death toll as we see today.
Having never left the RedHat fold, (I'm typing this on a Fedora 21 Laptop) I can't say with any honesty that I've missed them. At all.
Red Hat has been very, very good to me! My business is based on RHEL/CentOS and since Red Hat is quite profitable, I have a simple, economic assurance that my technology base won't disappear.
Feel free to use Ubuntu/Mint/Whatever as your hip distro; but Red Hat has carried a solid, economically potent and robust distro for decades.
It's only bullshit if Chris Roberts was actually lying. And validating it is pretty straightforward: Did the plane yaw, as was claimed? Can Chris' software cause it to happen again?
It's a pretty simple test. And as far as Chris' treatment, if he's been trying to tell people about this vulnerability and getting the cold shoulder, he's as innocent as they get and should be compensated for time served.
But... you'd be surprised how often it happens that I've learned a new tool, technique, or technology, only to be presented with an opportunity to use that new technology shortly thereafter.
You miss many opportunities simply because you don't see them as such because you lack the context, understanding, or tools to recognize them as such. Broadening your horizons helps you see the solutions and opportunities for what they are.
As it is now, you are not notified of security issues when you have no security whatsoever. HTTP sites should be given a dire, red warning because they represent the least secure position online. An SSL site with an expired certificate is far more desirable than an HTTP website.
Green should represent proper SSL certificates, as it does now.
But there's one more problem with SSL/HTTPS sites that nobody talks about: the fake SSL certificate. Your browser *probably* trust a multitude of SSL certificate vendors, and *any* of them can issue a certificate for *any* domain.
So there are literally hundreds of SSL certificate vendors that could issue a cert for google.com or whatever, and you wouldn't know. If the NSA offered a bit of $$ to a commonly trusted (but otherwise unheard of) certificate vendor to issue a few certificates to be used discreetly....
See the problem?
If I go to Thawte or RapidSSL to get a cert, I should have the ability to publish my vendor of choice, and nobody else's certificates should be considered trustworthy. Similarly, I should be able to publish revoked certificates the same way.
In practice, I've gone through 4 different routers, and so far, this one has come out on top. It has two decent antennas which may be some of that difference, to be fair.
My house was (over)built in the 1970s with 3/4" sheet rock, making each room almost like a Faraday cage - getting wifi signal *at all* from two rooms over is spotty at best. In my bedroom (2 doors away from the hotspot) I see about 15-20 Mbits, but in the same room I see up to ~ 40 Mbits for torrents. (50 Mbit connection, shared)
Oh, and it being open source, I'm gonna bank on its code quality being a bit better...
I bought a similar model about a year ago, and its large antennas and decent range/speed make it the best router I've yet had. If it's not even more expensive, why not support a vendor that supports (more) secure, Open Source solutions?
I have no relationship with this vendor other than being a happy customer
Slashdot Mirror
Chromecast all but requires another smart device running (continuously) to control it. You can't control it directly.
Google TV, on the other hand, AKA "Android TV Sticks", are a full-on Android device, just like your phone or tablet, but without the screen. You control it with something like a mouse/keyboard.
You can turn off your phone/laptop while using a Google TV. You can browse the Internet on your Google TV, without using anything else to help. You can plug in a keyboard/mouse and use it like a computer! You buy apps on it from Google play, just like any other android device, and it's very compatible!
I just loved my first TV stick that I bought on Amazon (MK808b) for $35! I just bought an MK809 when my MK808b finally died after 3 or 4 years of daily use, and it has (so far) been a nice upgrade. Faster processor, better wifi reception, more memory/storage. Still runs just fine off the power from the USB port on the side of my TV...
PS: To control one of these, you want a "flying mouse remote". It's a keyboard that "mouses" by waving it in the air.
We've been using Samsung drives in "non production" status servers, embedded servers, etc. and have had a terrible time of it. The first drives we bought a few years ago (840 Pro) were good, but we've seen Samsung SSDs run entirely through their write capacity (as reported by SMART) and then go dead when not even mounted! Turns out we aren't the only ones to get bit by buggy Samsung drives.
It also turns out that Samsung drives are even blacklisted in the Linux Kernel
I welcome Samsung's excellent cost/size value proposition! I just wish their drives were solid enough for our actual use.
My current laptop, a Dell Precision M3800 has it all: light weight, powerful, reasonable (if not fantastic) battery life, 4K screen, and native support for Linux, out of the box but it's hard to figure out what something the same size would be like at 1/4 the weight.
But I'm agreeing with other comments: I'd rather have this exact weight laptop with 3 days of battery life.
A few years back, I bought the phone with the very best battery life and I don't regret it one minute. Now on its third year, the phone still easily powers through a day with 50% or so battery life, and never leaves me high and dry when flying commercially which is when battery life is most important.
My next phone will be the phone with the best battery life Now that I finally have a powerful laptop that isn't also dreadfully heavy, battery life will once again be #1 for my next purchase.
What's sad is that UOP really could have done it! If they offered actual counseling guidance, and curricula that didn't just suck, and made sure that their clients passed classes with rigor, they could have *easily* made a profitable college with good reviews and earned trust.
Instead, they violated that trust, and probably deserve to be shut down.
Who would have thought that distracting drivers with information would make them less safe as drivers?
+1 for Lemon Pledge. Works GREAT to clear bug remains! We use Lemon Pledge to clean our Cessna at the flight club.
While they had a good run at first, I won't buy Samsung EVO SSDs any longer. They have had terrible issues with reliability, write amplifications, and trim support on Linux.
Friends don't let friends buy Samsung EVO SSDs!
What I find fucks with wifi is big thick walls.
I just bought a house. One of the things I was initially pleased to find is that it was built with full-on, 3/4" sheet rock - quality construction!
That is, until I plugged in my wifi router and tried to connect from my bedroom. I don't know what it is about 3/4" sheetrock made in 1978, but it's practically a Faraday cage. I'm contemplating setting up numerous routers with 1-antenna per room so you can get decent access everywhere in the house.
A compromise position in the hall closet gets the bedrooms *almost* OK through the doors...
You make it sound *onerous* but it doesn't need to be. You can buy many home routers with a USB port. Plug in a thumb drive and enable webDAV shares!
We've been using webDAV for many, many years to create a distributed, "cloud based" storage accessible anywhere with good security. (Authenticated webDAV over SSL is approximately as secure as the password)
I would add Fight For The Future which has been extremely active for Net Neutrality
Microsoft has always been fairly smart about courting developers with excellent tools and development platforms, and making it quite easy to build applications for Windows
Maybe you don't remember history the way I do.
Remember VB? An excellent toolkit that gained widespread acceptance in the Enterprise world for it's tight IDE, integration environment and easy forms. But then MS came out with VB.net which was about as related to VB 6 as javascript is to java. It was a horrible mess, everything had to be re-written to be compatible because it was really an entirely new language. Developers were left in the lurch, oh well, perhaps you shouldn'ta Microsoft, you know?
Remember Silverlight? The "Flash Killer", it was an excellent toolkit for writing distributed applications quickly. Performance was excellent. Many big names "bet the farm" on it. Until Microsoft walked away from it, too. Netflix will *never again* bank on a MS technology, I'm sure.
But that's not where it ends. Remember Windows Phone 7? The next big thing (tm) and they ditched it, for WP8, and all the devs were screwed. Again.
But that's not where it ends. Why is the XBox 360 not compatible with the original XBox? Why is the XBox "One" not compatible with the XBox 360? With every console generation, MS has been screwing the developers.
And so it goes. Over and over, the devs get the shaft any time they bet on Microsoft's newest, highly promoted technology.
What's next?
France banned hydrogenated vegetable oil and saw something like a 30% or 40% reduction in heart attacks... in just a single year. Just how blatant of a good idea do you need this to be?
You're right! When they "went red" they stopped all racism and are now a paradise of integration. Not that the parties themselves have changed ideologies or anything... Nope.
Gotta love this mass insanity and head burying.
The so-called "STEM shortage" is pretty much bullshit. If you take a look at the degrees that pay the best you find that standard STEM degrees dominate.
No degree is a guarantee of employment. If you can't be bothered to shower and show up, you're going to have a hard time. Degrees merely improve your odds of success significantly.
I like how it's unpopular to point out that some traits of conservatism are undesirable. For example, looking at the map of the laws against interracial marriage and also gay marriage looks pretty similar to the standard red/blue map that seems to dominate politics.
But hey, it's not a "Republican Core Value" or something. Yeah. /s
Just to be fair "perfectly secure" is probably overstating things considerably. It would pass "no known exploits" pretty well, certainly "commercially viable".
The only "perfectly secure" computer is off, unplugged from the Internet, and encased in 50 feet of reinforced concrete. And even then, there *are* ways to exploit it using *ahem* brute force...
It's easy to design something that people can do. It's tough to design a system that people can't fail at. And that's where there's a big, soft, squishy line that divides what people can generally keep up with and the things that people have to work at to get wrong.
As a software engineer, I require the first, and aim for the latter. It's tough.
My uncle was an BART engineer. He controlled BART ([San Francisco] Bay Area Rapid Transit) trains in the SF Bay Area for a living. The train had doors on both sides of the train and some stations opened on one side, or the other.
BART trains are frequently "up in the air" as much as 50 feet, where the expectation is that you climb a flight or two of stairs to the BART station and board the train. And, for passengers, the doors automatically opened on the correct side so that nobody got hut.
For passengers. But the engineers were expected to manually open the doors on the appropriate side when leaving their station. Now, it's not particularly difficult to look outside the door and see which side the station is on, and the doors for passengers automatically opened on the correct side.
This is where that big, squishy line starts to rear its ugly head. Because while passengers weren't expected to remember which side to get off, engineers were. And my poor uncle made a mistake one day, and opened the wrong side. It was a fatal mistake.
Answer me this: Why would we expect that passengers would never get it right, but engineers would never get it wrong?
Intelligently designed systems that account for and prevent common human mistakes is a design goal. It's tough to do because you have to predict what the end user will likely get wrong and account for that. Nonetheless, it's a hallmark of engineering advancement that we've designed something so safe and resistant to human error as a car that casually travels 100 MPH with as low a death toll as we see today.
Having never left the RedHat fold, (I'm typing this on a Fedora 21 Laptop) I can't say with any honesty that I've missed them. At all.
Red Hat has been very, very good to me! My business is based on RHEL/CentOS and since Red Hat is quite profitable, I have a simple, economic assurance that my technology base won't disappear.
Feel free to use Ubuntu/Mint/Whatever as your hip distro; but Red Hat has carried a solid, economically potent and robust distro for decades.
It's only bullshit if Chris Roberts was actually lying. And validating it is pretty straightforward: Did the plane yaw, as was claimed? Can Chris' software cause it to happen again?
It's a pretty simple test. And as far as Chris' treatment, if he's been trying to tell people about this vulnerability and getting the cold shoulder, he's as innocent as they get and should be compensated for time served.
(takes out his autonomous, self-contained smartphone to post on Slashdot)
what where you saying about new stuff having more dependencies ?
Oh. Yeah.
So then the police just cut your hand off. One more reason why biometrics isn't such a great idea.
But... you'd be surprised how often it happens that I've learned a new tool, technique, or technology, only to be presented with an opportunity to use that new technology shortly thereafter.
You miss many opportunities simply because you don't see them as such because you lack the context, understanding, or tools to recognize them as such. Broadening your horizons helps you see the solutions and opportunities for what they are.
As it is now, you are not notified of security issues when you have no security whatsoever. HTTP sites should be given a dire, red warning because they represent the least secure position online. An SSL site with an expired certificate is far more desirable than an HTTP website.
Green should represent proper SSL certificates, as it does now.
But there's one more problem with SSL/HTTPS sites that nobody talks about: the fake SSL certificate. Your browser *probably* trust a multitude of SSL certificate vendors, and *any* of them can issue a certificate for *any* domain.
So there are literally hundreds of SSL certificate vendors that could issue a cert for google.com or whatever, and you wouldn't know. If the NSA offered a bit of $$ to a commonly trusted (but otherwise unheard of) certificate vendor to issue a few certificates to be used discreetly....
See the problem?
If I go to Thawte or RapidSSL to get a cert, I should have the ability to publish my vendor of choice, and nobody else's certificates should be considered trustworthy. Similarly, I should be able to publish revoked certificates the same way.
Why hasn't this already been done?
By spec, wireless N, up to 300 Mbit.
In practice, I've gone through 4 different routers, and so far, this one has come out on top. It has two decent antennas which may be some of that difference, to be fair.
My house was (over)built in the 1970s with 3/4" sheet rock, making each room almost like a Faraday cage - getting wifi signal *at all* from two rooms over is spotty at best. In my bedroom (2 doors away from the hotspot) I see about 15-20 Mbits, but in the same room I see up to ~ 40 Mbits for torrents. (50 Mbit connection, shared)
Oh, and it being open source, I'm gonna bank on its code quality being a bit better...
You could do that, or you could buy a router pre-configured with OSS from the factory. It's not even expensive at ~ $50.
I bought a similar model about a year ago, and its large antennas and decent range/speed make it the best router I've yet had. If it's not even more expensive, why not support a vendor that supports (more) secure, Open Source solutions?
I have no relationship with this vendor other than being a happy customer