Are you talking about TN visas under NAFTA? Those are a very different thing from H1B visas. NAFTA TN visas were designated with the term "Systems analyst", and being a programmer can get you rejected on either side of the border.
This article is a sort of saving of face because recall during the debacle there were poorly supported claims (via leading online surveys) that every Note 7 user was marching right to their nearest Apple store to buy an iPhone.
Slashdot has notoriously always had a comically unfunny April 1st, and at this point I have to think the complete lameness of it all is the real meta-joke.
The whole "HTTP/2 stink" thing seems to be a bit of a meme, but it's remarkable how the people who state it vaguely wave their hands around and make unsupported claims.
1. HTTP/2 is *fantastic* for higher latency connections. If you're a small site and you can't afford to have geolocated servers around the globe, HTTP/2 offers a much better experience for those high latency connections. I've been using SPDY for a couple of years to service clients in Singapore from a server in the US (which for a variety of legislative and technical reasons I can't replicate there). It is absolutely better.
2. HTTP Pipelining is when you know that someone is just doing the "I oppose" thing and searching around for objections. HTTP pipelining is not supported by default in a *single* major browser because it has critical, deadly faults that render it useless. When people bring it up to oppose HTTP/2, their position is rendered irrelevant.
3. HTTP/2 removes the need to do script and resource coalescing. It removes the need to deal with difficult to manage image sprites. All of those are bullshit that are particularly onerous and expensive to little sites.
4. HTTP/2 makes SSL much cheaper to the experience. This is very good.
HTTP/2 is a *huge* benefit especially to the little guy. Google can do every manner of optimization, they can deploy across legions and armies of servers around the globe. This can be expensive and logistically difficult for little sites, especially if you want SSL. HTTP/2 levels the playing field to some degree.
It isn't about "a chip". It's about a system that is designed for a specific thermal and electrical load. nvidia probably got flak from notebook makers who were facing dissatisfied customers.
You only have to look at a lot of the nonsense comments throughout, such as yours -- people just contriving how "easy" everything is, and how simple it is. Yeah, and I'll bet all of you design notebooks. No? Then shut up.
Quite the opposite, if you file and are granted a patent for something that is later ruled invalid, there should be substantial penalties for the filer, because the purpose of a patent application is a government granted monopoly, leveraging the legal power and force of government to suppress other business. If you tell the government that you've done something novel that isn't, and prevent competition through that mechanism, there are substantial social costs (none of the benefits of invention, but all of the costs of a monopoly).
I know, right? Being valued at $410 billion -- on the backs of two consumer products in a very fickle market -- is just brutally punishing, treating them like some fly-by-night nobodies. How grossly unfair.
It's not a technical limitation...but they'll fix that non limitation in WP8? Am I reading you right?
It is *absolutely* a technical limitation. Microsoft used iOS as the baseline that they emulated, only once they got where iOS was, it had moved long down the road (now supporting Android-like multitasking).
Further it is a bit humorous seeing WP boosters constantly using Android as the punching bag to elevate WP features. Only the Lumia 900 has rather terrible battery life.
I would strongly sanction what they wrote. The sore loser "change the rules because we lost the game" knee-jerk reaction is an embarrassment.
It's worth noting that Dion basically imploded the Liberal government with their "green shift" plans. If the Liberals didn't backtrack and try for another direction, the Conservatives would have had a much, much larger majority. Kyoto has not sold in Canada at all, and the tiresome "fuck you Harper!" tirades on her do not mirror actual sentiment in Canada.
That comment is, pardon the expression, horse shit. It is fundamentally wrong on virtually every level.
While Canada does, like pretty much every jurisdiction, have levels of government with their own responsibilities, in most matters the federal government reigns supreme. There have been a number of false starts at federal legislation to achieve Kyoto, but they were abandoned because they were politically untenable.
The two most populace provinces -- Quebec and Ontario -- have actually been taking substantial action on greenhouse gases. Ontario gets little credit, but we've been shutting down coal plants while hugely expanding renewable resources.
" I do not believe that local dialects and pronunciation is the issue"
I have been using the voice input functionality since it came out, and have been shocked at the startling accuracy of it. It is almost never wrong, and is eminently useful for navigation, making calls (by number or by name), or for voice dictation in a message. I use it frequently and it is shockingly rare that it isn't dead on.
I'm talking about just general voice to text, not about translate which adds another language to language issue, however Google has the voice recognition thing DOWN. I imagine there are some accents and manners of speech that present it difficulty however.
I see that you're getting talking points from the internet's biggest misinformed windbag, Fleurian Miller (seriously, that guy is just a stream of baseless, misinformed bullshit. How he gets linked by anyone is a marvel).
Nokia sued over GSM patents, as clearly Nokia had a pretty good lead in that area. Motorola, HTC, Samsung, and others already license those patents. Apple refused. Nokia litigated and won. Those are the breaks.
So....no. Every single person who pulls the "Now they're going after Android" bit is just ignorant of basically everything about this lawsuit.
An expert on codecs is not an expert on patents. The mere idea is ludicrous. His analysis in no way was based upon the specific claims of the patents, but instead was just broadly claiming that they do similar things.
A lot of very smart people have looked at the patents and completely disagree with him. Further, Google is available for all of their lawsuit target needs, yet the silence is deafening.
The best part is that licensing h.264 in no way protects you from patents either -- at any point in the future anyone can come forward and sue every user of h.264, and there is no protection offered by the consortium: They simply protect you from their own patents.
This has HUGE ramifications since IE 9 is not slated to support Web-M - which would mean IE 9 would not work with HTML 5 YouTube, while every other browser did.
IE supports plug-ins. Adding a Web-M plug-in is non-difficult, and really I wouldn't be surprised to see Google themselves provide one.
Hey look, it's all of the "I wave the Apple flag and therefore adopt all of the same positions" talking points conveniently collected into one post. That is mighty helpful of you.
Whatever my opinion on this (though your post is absolutely dripping with stunning ignorance and outright lies), what really makes me laugh is the continual references to a x264 developer -- who has a very strong incentive to defend the knowledge he has -- as an "expert" on patents. That really is the delightful cherry on the top of the cake.
Yes, it should be interesting to see what effect this has on marketshare. I recall that in the months leading up the iPhone 4's release, all of the talk was that Android's advances were only temporary, all just waiting for the iPhone 4. Of course that turned out to be utter bunk. So then everyone moved onto the Verizon ruse.
People dedicated to getting an iPhone have long moved to AT&T (which paid off handsomely for AT&T, which is why they paid heavily for exclusivity). For all of the anti-AT&T chatter, in most empirical tests it has a faster network, it uses global bands, and it has better support. Now instead people are supposed to rush to a company with worse support, slower real world speeds, a network that works on one provider in one country on the planet, and no simultaneous data and voice, to get a phone to be replaced in mere months?
Give me a break. In two months you and others breathing the same nonsense will have to somehow find some new spin. Ah yes -- it's just the calm before the iPhone 5 storm!
Note also that AT&T, in losing their exclusivity, is suddenly becoming far less enamored with the iPhone. Not only are they getting some premiere devices like the Atrix, they're actually starting to promote them. They might even stop gimping them quite as much.
This is big news for a couple of days because it was so anticipated for so long. Yet it really is too-little, too-late. If Apple makes a killer iPhone5, which is entirely possible, then the game changes, but for this it's just the pent up nature that has so much hoopla. Once people sober up I think the reality will set in.
Gaming on the Android platform has generally been terrible because of frequent, experience-killing pauses, and generally poor performance. The concurrent garbage collector offers to improve the former (including every existing game), while the latter is being dealt with by a much wider gamut of usability from the NDK, with optimized, efficient, lifetime-controlled native code that has the ability to manage and capture events, handle sound, etc.
Those two things are HUGE, and will help make up for the massive quality gap between Android gaming and entertainment relative to the iPhone. I seldom pull up a game on my Nexus One, but when I do it is generally a disappointment. Gingerbread will start the change away from that.
The success of Android has been driven by the fact that Apple held onto their exclusive deal with AT&T too long.
Oh bulllllshit.
Android has seem similar gains around the world, where the whole weak AT&T excuse (you know, a carrier that covers virtually 100% of the US population) has no relevance. In Canada the iPhone had a brief period where it shone, but now the Android devices are coming on very strong.
However comparing Linux/Windows on the desktop iOS/Android on smartphones is asinine. Windows was never locked down or exclusionary even remotely to the degree that iOS is. It was an open, free market for virtually everyone.
why add support for something that's going to cause a bad user experience?
Just wait until the dogpile forming on the Flash->HTML5 conversion toolkits have their way on the net. Soon your iPad will be grinding to a halt trying to running a bunch of evading monkeys.
No, seriously, it will. If you think HTML5 can drag your machine to the depths of hell, enjoy some of the HTML5 showcase apps. Of course, don't try the games because most of them rely upon keyboard inputs. Try that new Arcade Fire HTML5 video and see how that works out for you.
There's my quick and ugly Flash demo. There are speed slowdowns of videos encoded to target desktops (which are most Flash videos, while most HTML5 videos, knowing that the target is primarily iOS devices, target much lower complexity profiles and bitrates), and it is not an elegant experience, but I enjoy having the option of enabling it whenever I want to.
I have written complex javascript applications and can tell you objectively that javascript on the Droid (recently updated to Android 2.2) is orders of magnitude slower than the iPad.
Every empirical metric says that you are very, very wrong. The V8 engine in Froyo demolishes iOS.
Do smart phones really have a routable, unique IP? I always presumed that my smartphones were behind a mega-NAT.
It is hard to believe, but early in the era of the internet, we didn't have NATs, and the prediction was that we would exhaust the supply much, much quicker (along with the whole "everyone's toaster is going to have an IP address" predictions). Then NAT was invented, corporations installed it, and suddenly instead of megacorp needing a/16 address, they needed just a/28 or the like.
For about a week-long period Verizon had a "two for one" special. Of course, the "two for one" included the requirement that you buy two contracts, weighing it at some $2500 of total spend per device. So, not really.
Seriously, the "freebies" myth has never been true, because a smartphone is never free. The pittance $99 or $199 that someone pays for an iPhone barely differs, and of course is ghetto cheap compared to the $550 I spent on my Nexus One. I guess I'm with the Elite.
Slashdot Mirror
Are you talking about TN visas under NAFTA? Those are a very different thing from H1B visas. NAFTA TN visas were designated with the term "Systems analyst", and being a programmer can get you rejected on either side of the border.
This article is a sort of saving of face because recall during the debacle there were poorly supported claims (via leading online surveys) that every Note 7 user was marching right to their nearest Apple store to buy an iPhone.
Slashdot has notoriously always had a comically unfunny April 1st, and at this point I have to think the complete lameness of it all is the real meta-joke.
The whole "HTTP/2 stink" thing seems to be a bit of a meme, but it's remarkable how the people who state it vaguely wave their hands around and make unsupported claims.
1. HTTP/2 is *fantastic* for higher latency connections. If you're a small site and you can't afford to have geolocated servers around the globe, HTTP/2 offers a much better experience for those high latency connections. I've been using SPDY for a couple of years to service clients in Singapore from a server in the US (which for a variety of legislative and technical reasons I can't replicate there). It is absolutely better.
2. HTTP Pipelining is when you know that someone is just doing the "I oppose" thing and searching around for objections. HTTP pipelining is not supported by default in a *single* major browser because it has critical, deadly faults that render it useless. When people bring it up to oppose HTTP/2, their position is rendered irrelevant.
3. HTTP/2 removes the need to do script and resource coalescing. It removes the need to deal with difficult to manage image sprites. All of those are bullshit that are particularly onerous and expensive to little sites.
4. HTTP/2 makes SSL much cheaper to the experience. This is very good.
HTTP/2 is a *huge* benefit especially to the little guy. Google can do every manner of optimization, they can deploy across legions and armies of servers around the globe. This can be expensive and logistically difficult for little sites, especially if you want SSL. HTTP/2 levels the playing field to some degree.
It isn't about "a chip". It's about a system that is designed for a specific thermal and electrical load. nvidia probably got flak from notebook makers who were facing dissatisfied customers.
You only have to look at a lot of the nonsense comments throughout, such as yours -- people just contriving how "easy" everything is, and how simple it is. Yeah, and I'll bet all of you design notebooks. No? Then shut up.
Quite the opposite, if you file and are granted a patent for something that is later ruled invalid, there should be substantial penalties for the filer, because the purpose of a patent application is a government granted monopoly, leveraging the legal power and force of government to suppress other business. If you tell the government that you've done something novel that isn't, and prevent competition through that mechanism, there are substantial social costs (none of the benefits of invention, but all of the costs of a monopoly).
Haven't logged into Slashdot in just short of forever, but I see that you're my foe. To the death!
I know, right? Being valued at $410 billion -- on the backs of two consumer products in a very fickle market -- is just brutally punishing, treating them like some fly-by-night nobodies. How grossly unfair.
It's not a technical limitation...but they'll fix that non limitation in WP8? Am I reading you right?
It is *absolutely* a technical limitation. Microsoft used iOS as the baseline that they emulated, only once they got where iOS was, it had moved long down the road (now supporting Android-like multitasking).
Further it is a bit humorous seeing WP boosters constantly using Android as the punching bag to elevate WP features. Only the Lumia 900 has rather terrible battery life.
http://www.anandtech.com/show/5724/nokia-lumia-900-review-supersized-with-lte/3
I'm not really feeling the advantages. But if we just wait until the next version...
I would strongly sanction what they wrote. The sore loser "change the rules because we lost the game" knee-jerk reaction is an embarrassment.
It's worth noting that Dion basically imploded the Liberal government with their "green shift" plans. If the Liberals didn't backtrack and try for another direction, the Conservatives would have had a much, much larger majority. Kyoto has not sold in Canada at all, and the tiresome "fuck you Harper!" tirades on her do not mirror actual sentiment in Canada.
That comment is, pardon the expression, horse shit. It is fundamentally wrong on virtually every level.
While Canada does, like pretty much every jurisdiction, have levels of government with their own responsibilities, in most matters the federal government reigns supreme. There have been a number of false starts at federal legislation to achieve Kyoto, but they were abandoned because they were politically untenable.
The two most populace provinces -- Quebec and Ontario -- have actually been taking substantial action on greenhouse gases. Ontario gets little credit, but we've been shutting down coal plants while hugely expanding renewable resources.
Score:5? Seriously?
Quick question to see how much you really know: How much does Alberta and the oil industry contribute the federal government coffers?
The entirety of this nation has been propped up by the oil sands, like it or not.
" I do not believe that local dialects and pronunciation is the issue"
I have been using the voice input functionality since it came out, and have been shocked at the startling accuracy of it. It is almost never wrong, and is eminently useful for navigation, making calls (by number or by name), or for voice dictation in a message. I use it frequently and it is shockingly rare that it isn't dead on.
I'm talking about just general voice to text, not about translate which adds another language to language issue, however Google has the voice recognition thing DOWN. I imagine there are some accents and manners of speech that present it difficulty however.
I see that you're getting talking points from the internet's biggest misinformed windbag, Fleurian Miller (seriously, that guy is just a stream of baseless, misinformed bullshit. How he gets linked by anyone is a marvel).
Nokia sued over GSM patents, as clearly Nokia had a pretty good lead in that area. Motorola, HTC, Samsung, and others already license those patents. Apple refused. Nokia litigated and won. Those are the breaks.
So....no. Every single person who pulls the "Now they're going after Android" bit is just ignorant of basically everything about this lawsuit.
An expert on codecs is not an expert on patents. The mere idea is ludicrous. His analysis in no way was based upon the specific claims of the patents, but instead was just broadly claiming that they do similar things.
A lot of very smart people have looked at the patents and completely disagree with him. Further, Google is available for all of their lawsuit target needs, yet the silence is deafening.
The best part is that licensing h.264 in no way protects you from patents either -- at any point in the future anyone can come forward and sue every user of h.264, and there is no protection offered by the consortium: They simply protect you from their own patents.
http://developer.android.com/resources/dashboard/platform-versions.html
Humorously the uptake rate of new Android versions exceeds the rate that Apple has gotten updates adopted.
IE supports plug-ins. Adding a Web-M plug-in is non-difficult, and really I wouldn't be surprised to see Google themselves provide one.
Hey look, it's all of the "I wave the Apple flag and therefore adopt all of the same positions" talking points conveniently collected into one post. That is mighty helpful of you.
Whatever my opinion on this (though your post is absolutely dripping with stunning ignorance and outright lies), what really makes me laugh is the continual references to a x264 developer -- who has a very strong incentive to defend the knowledge he has -- as an "expert" on patents. That really is the delightful cherry on the top of the cake.
Yes, it should be interesting to see what effect this has on marketshare. I recall that in the months leading up the iPhone 4's release, all of the talk was that Android's advances were only temporary, all just waiting for the iPhone 4. Of course that turned out to be utter bunk. So then everyone moved onto the Verizon ruse.
People dedicated to getting an iPhone have long moved to AT&T (which paid off handsomely for AT&T, which is why they paid heavily for exclusivity). For all of the anti-AT&T chatter, in most empirical tests it has a faster network, it uses global bands, and it has better support. Now instead people are supposed to rush to a company with worse support, slower real world speeds, a network that works on one provider in one country on the planet, and no simultaneous data and voice, to get a phone to be replaced in mere months?
Give me a break. In two months you and others breathing the same nonsense will have to somehow find some new spin. Ah yes -- it's just the calm before the iPhone 5 storm!
Note also that AT&T, in losing their exclusivity, is suddenly becoming far less enamored with the iPhone. Not only are they getting some premiere devices like the Atrix, they're actually starting to promote them. They might even stop gimping them quite as much.
This is big news for a couple of days because it was so anticipated for so long. Yet it really is too-little, too-late. If Apple makes a killer iPhone5, which is entirely possible, then the game changes, but for this it's just the pent up nature that has so much hoopla. Once people sober up I think the reality will set in.
Gaming on the Android platform has generally been terrible because of frequent, experience-killing pauses, and generally poor performance. The concurrent garbage collector offers to improve the former (including every existing game), while the latter is being dealt with by a much wider gamut of usability from the NDK, with optimized, efficient, lifetime-controlled native code that has the ability to manage and capture events, handle sound, etc.
Those two things are HUGE, and will help make up for the massive quality gap between Android gaming and entertainment relative to the iPhone. I seldom pull up a game on my Nexus One, but when I do it is generally a disappointment. Gingerbread will start the change away from that.
Oh bulllllshit.
Android has seem similar gains around the world, where the whole weak AT&T excuse (you know, a carrier that covers virtually 100% of the US population) has no relevance. In Canada the iPhone had a brief period where it shone, but now the Android devices are coming on very strong.
However comparing Linux/Windows on the desktop iOS/Android on smartphones is asinine. Windows was never locked down or exclusionary even remotely to the degree that iOS is. It was an open, free market for virtually everyone.
Just wait until the dogpile forming on the Flash->HTML5 conversion toolkits have their way on the net. Soon your iPad will be grinding to a halt trying to running a bunch of evading monkeys.
No, seriously, it will. If you think HTML5 can drag your machine to the depths of hell, enjoy some of the HTML5 showcase apps. Of course, don't try the games because most of them rely upon keyboard inputs. Try that new Arcade Fire HTML5 video and see how that works out for you.
http://www.youtube.com/watch?v=cb9jfdltkUU
There's my quick and ugly Flash demo. There are speed slowdowns of videos encoded to target desktops (which are most Flash videos, while most HTML5 videos, knowing that the target is primarily iOS devices, target much lower complexity profiles and bitrates), and it is not an elegant experience, but I enjoy having the option of enabling it whenever I want to.
Every empirical metric says that you are very, very wrong. The V8 engine in Froyo demolishes iOS.
Do smart phones really have a routable, unique IP? I always presumed that my smartphones were behind a mega-NAT.
It is hard to believe, but early in the era of the internet, we didn't have NATs, and the prediction was that we would exhaust the supply much, much quicker (along with the whole "everyone's toaster is going to have an IP address" predictions). Then NAT was invented, corporations installed it, and suddenly instead of megacorp needing a /16 address, they needed just a /28 or the like.
It's humorous that this keeps getting brought up.
For about a week-long period Verizon had a "two for one" special. Of course, the "two for one" included the requirement that you buy two contracts, weighing it at some $2500 of total spend per device. So, not really.
Seriously, the "freebies" myth has never been true, because a smartphone is never free. The pittance $99 or $199 that someone pays for an iPhone barely differs, and of course is ghetto cheap compared to the $550 I spent on my Nexus One. I guess I'm with the Elite.