Everybody needs friends of some sort. Unless you're suggesting that robots will be good enough friends by then. But if they're autonomous and free-thinking enough to make good friends, they're going to be just as much of a problem as real humans. They're also going to be harder to destroy.
latency is the real issue, if wireless can improve that (which is a big ask) then it can be viable. Don't get me wrong 10GB/s would be great but what are we downloading that is that big, 100MB/s would be more than enough for me and I'm a pretty heavy user.
Trying streaming Netflix or Hulu along with your neighbors.... All of a sudden, that shared 100MB/s becomes 2MB/s or less, and a stuttering image for your viewing pleasure. Or try uploading those nifty 20+MB images you just took to your favorite photo printer to create a poster or two. You might be there a while. Yes, this is also a problem with wired, at least in the US, with hugely asymmetric upload / download ratios. I have wireless N in the house, I'm running cable next week to remove my HTPC from wireless, it's just too slow.
Actually - you said they did it for Android (Samsung).
Android, FYI, belongs to Google.
Apple kicking Google off the included apps seems to have gotten Apple exactly that, a free update to an almost Android equivalent.
On the creation of a mapping dept - yes, Apple didn't handle that as well as they might. There is far too much involved in mapping that is currently manual labor and shouldn't be (IMHO) Apple probably would have been better served outright buying one of the GPS providers, but in this one case they were pretty naive. Then again, you can't hit a home run every time. Their app was serviceable depending on where you were, and it's getting better. It's not like google maps are perfect either. I've been led through what was a 10 mile loop to get to where I needed to go a couple of miles away - turns out google missed a road. It happens. Garmin and TomTom are more error prone than Google I've found.
That argument doesn't wash, it took Google quite a long time to provide Google Maps on the iPhone after being removed. They knew as early as June, yet it took them until Dec to release a new updated maps app?
And it had nothing to do with branding, Google wants ad dollars and customer info. I'm pretty sure initially they thought they'd be fine without a maps app on the iphone. The drop in traffic and info I'm guessing spurred them to rethink that. From Apple's side, I'm sure that relying on a competitor for a key standard component was no small part of the decision to removing Google from the picture.
For all of us, it was actually a good thing, even if Apple's maps aren't as good. Google has a competitor in the maps space now, and Apple, if they work at it, could become a real maps player.
No, but skimming through them, these are remarkably clear and short claims. Also, the '135 was filed in 2000, and I'm 99% sure that ToR already existed and did some of this then, if not all of it. VPNs and mechanisms to create links on the fly existed prior to this patent. So I'm surprised that the patent was found to be valid over Chat and video protocols, more careful reading is required.
Maps? Google didn't improve or do squat with the iOS map app until Apple kicked them off as a standard app. When Apple's maps came out, bad as they were, all of a sudden Google's map app came back improved and updated, with features that were only released on Android? Coincidence? Don't believe so..
12 months sounds about right, after that, for a total of 7 years, max, they can retain the general billing information (there's some timeline, 7 I believe is the maximum?)
There's more harm here than mere latency. Now all communications go through known relays. The NSA must be dancing in the streets. Before they'd actually have to tap the actual IPs.
Partially correct. You can find some nugget in open source. However, for real successful enterprises, you generally have to take that and do significant work and extensions to actually produce a worthwhile product. This can be true even of commercial code.
I'll give you a story about 2 companies. One chose language A and its eco-system. It was all proprietary and locked in. The other chose language B, and it's eco-system. This language was much more open source oriented, and by its nature, not locked to the vendor's platform. 2 very comparable systems were built (either could have fronted for the other) For sake of argument we'll say that the people were equal, possibly even of greater skill in language A (actually, my real lang A people probably were significantly better, sadly) Both companies were within an order of magnitude of customers and revenue. Profit was in company B's favor. Number of customers was in company B's favor, by a multiple. IOW, company B served more customers with smaller transactions with greater profit but lower revenue.
Now, company A required 800% more servers to serve almost an order less data to 1/10th the customers. Actually, I'm not sure about that, but I do know for a fact that the data layer was an 80 fold increase while the total number of servers at B was less than 1/20th of just the DB servers at company A, and company B had at least 100% overhead available for growth. I have no idea about the app and web layer comparisons between the two. I also know that company B had releases roughly 12 times as often as company A, and a lot less rollback / downltime. Also, the personnel comparison was 1/10th the people at B vs A in development. Neither company was small.
What you can take away from that is yes, language has a very big impact on what you can deliver and how fast you can deliver it, and the cost of maintenance and scalability do directly correlate to the technologies chosen. Even if there are smarter people overall on the poorer technological choice, they will lose on every metric except maybe the initial release, and then only by time to release.
So whatever elitism you might think I exhibit, it's merely my observations of my experiences. You see someone building a bridge out of marshmallows, you just know the end is going to be ugly.
It's not language elitism. It's a given that the knowledge base required to do something with JS or Python is significantly lower than with assembly. I wish I was an assembly master in addition to what I know, obviously it's preferred for my current hardware platforms, but even with other modern architectures it'd help me better understand how to optimize my code more than I do currently. As it is, I'm probably a "script kiddie" when it comes to assembly. A little knowledge is a dangerous thing. At least I know enough to know that and leave those sections to experts in their fields.
Python and javascript are syntactically much more difficult to master than assembly language.
That's why there are so many assembly masters as compared to script kiddies, err, Python and JS "masters"? Or were you meaning to be funny? The mods certainly were clueless. (Interesting, really?)
Sorry to hear about your friend. I've always wondered whether a dose of HGH, either alone or combined with a some other hormones that are much lower as we age, would kick start the healing process and give an artificial bounce back for older people. I'm sure there would be side effects, but manipulating the body's systems in this fashion is something we are only starting to explore.
I'd have to agree with the AC a couple of threads above - the US engaged in this activity against the Indians even prior to becoming a country and continued into the 1900s on an ever reducing scale.
That major drop in vitality is directly related to your exercise level and genetics. Some have it earlier, some later, exercise can delay it for many. I suffered a drop and started eating better and exercising, and recovered most of the drop. Some will tell you for men that it's the drop in testosterone. I'm sure it has an effect. But knowing a 90 year old guy that still runs marathons and started in his mid 50s when he was overweight and on his way to a major heart attack tells me it's not the entire story.
And yet, the faster IT "develops", the more it seems like year x's crop reinvents the wheel, and several years later, the "hot" trend that was the silver bullet either really does have all the same flaws as yesteryear's tech, or brought in some new ones that made it an even worse choice.
The only thing that's developed rather rapidly is hardware, and that train has slowed relative to technology to take advantage of it. Software wise, some new tech has come out, but mostly existing tech has refined itself. Nothing I'd call revolutionary compared to what existed before.
Hell, look at Keith Richards! That guy should have been dead long ago with all the chemicals he's put in his body, even with regular transfusions. YMMV
Who says he's not? Perhaps the first known zombie.
Seriously, or, I transferred to another college, why does Amazon care? If I rent from a physical location, and haul them myselves, does it matter to whom I rent them from?
I'll go back to my statement: posted rates. No difference for person A, B or C at provider 1. Provider 2 can have a different posted rate, but insurance just has to pay the middle going rate for non-emergency care, just like they do for auto repair.
Creaking? They're cemented together with blood, sweat, and duct tape that has solidified into a solid mass over the years. It's probably more stable than Roman mortar, given all the attempts to replace them. Have the original travel systems ever been replaced that travel agents used to look things up on?
Slashdot Mirror
Everybody needs friends of some sort. Unless you're suggesting that robots will be good enough friends by then. But if they're autonomous and free-thinking enough to make good friends, they're going to be just as much of a problem as real humans. They're also going to be harder to destroy.
Ted Kaczynski
latency is the real issue, if wireless can improve that (which is a big ask) then it can be viable. Don't get me wrong 10GB/s would be great but what are we downloading that is that big, 100MB/s would be more than enough for me and I'm a pretty heavy user.
Trying streaming Netflix or Hulu along with your neighbors.... All of a sudden, that shared 100MB/s becomes 2MB/s or less, and a stuttering image for your viewing pleasure. Or try uploading those nifty 20+MB images you just took to your favorite photo printer to create a poster or two. You might be there a while. Yes, this is also a problem with wired, at least in the US, with hugely asymmetric upload / download ratios. I have wireless N in the house, I'm running cable next week to remove my HTPC from wireless, it's just too slow.
Actually - you said they did it for Android (Samsung).
Android, FYI, belongs to Google.
Apple kicking Google off the included apps seems to have gotten Apple exactly that, a free update to an almost Android equivalent.
On the creation of a mapping dept - yes, Apple didn't handle that as well as they might. There is far too much involved in mapping that is currently manual labor and shouldn't be (IMHO) Apple probably would have been better served outright buying one of the GPS providers, but in this one case they were pretty naive. Then again, you can't hit a home run every time. Their app was serviceable depending on where you were, and it's getting better. It's not like google maps are perfect either. I've been led through what was a 10 mile loop to get to where I needed to go a couple of miles away - turns out google missed a road. It happens. Garmin and TomTom are more error prone than Google I've found.
Sounds like you're agreeing that Google had no interest in expanding the maps app. Thanks!
That argument doesn't wash, it took Google quite a long time to provide Google Maps on the iPhone after being removed. They knew as early as June, yet it took them until Dec to release a new updated maps app?
And it had nothing to do with branding, Google wants ad dollars and customer info. I'm pretty sure initially they thought they'd be fine without a maps app on the iphone. The drop in traffic and info I'm guessing spurred them to rethink that. From Apple's side, I'm sure that relying on a competitor for a key standard component was no small part of the decision to removing Google from the picture.
For all of us, it was actually a good thing, even if Apple's maps aren't as good. Google has a competitor in the maps space now, and Apple, if they work at it, could become a real maps player.
No, but skimming through them, these are remarkably clear and short claims. Also, the '135 was filed in 2000, and I'm 99% sure that ToR already existed and did some of this then, if not all of it. VPNs and mechanisms to create links on the fly existed prior to this patent. So I'm surprised that the patent was found to be valid over Chat and video protocols, more careful reading is required.
Maps? Google didn't improve or do squat with the iOS map app until Apple kicked them off as a standard app. When Apple's maps came out, bad as they were, all of a sudden Google's map app came back improved and updated, with features that were only released on Android? Coincidence? Don't believe so..
12 months sounds about right, after that, for a total of 7 years, max, they can retain the general billing information (there's some timeline, 7 I believe is the maximum?)
There's more harm here than mere latency. Now all communications go through known relays. The NSA must be dancing in the streets. Before they'd actually have to tap the actual IPs.
Partially correct. You can find some nugget in open source. However, for real successful enterprises, you generally have to take that and do significant work and extensions to actually produce a worthwhile product. This can be true even of commercial code.
I'll give you a story about 2 companies. One chose language A and its eco-system. It was all proprietary and locked in. The other chose language B, and it's eco-system. This language was much more open source oriented, and by its nature, not locked to the vendor's platform. 2 very comparable systems were built (either could have fronted for the other) For sake of argument we'll say that the people were equal, possibly even of greater skill in language A (actually, my real lang A people probably were significantly better, sadly) Both companies were within an order of magnitude of customers and revenue. Profit was in company B's favor. Number of customers was in company B's favor, by a multiple. IOW, company B served more customers with smaller transactions with greater profit but lower revenue.
Now, company A required 800% more servers to serve almost an order less data to 1/10th the customers. Actually, I'm not sure about that, but I do know for a fact that the data layer was an 80 fold increase while the total number of servers at B was less than 1/20th of just the DB servers at company A, and company B had at least 100% overhead available for growth. I have no idea about the app and web layer comparisons between the two. I also know that company B had releases roughly 12 times as often as company A, and a lot less rollback / downltime. Also, the personnel comparison was 1/10th the people at B vs A in development. Neither company was small.
What you can take away from that is yes, language has a very big impact on what you can deliver and how fast you can deliver it, and the cost of maintenance and scalability do directly correlate to the technologies chosen. Even if there are smarter people overall on the poorer technological choice, they will lose on every metric except maybe the initial release, and then only by time to release.
So whatever elitism you might think I exhibit, it's merely my observations of my experiences. You see someone building a bridge out of marshmallows, you just know the end is going to be ugly.
It's not language elitism. It's a given that the knowledge base required to do something with JS or Python is significantly lower than with assembly. I wish I was an assembly master in addition to what I know, obviously it's preferred for my current hardware platforms, but even with other modern architectures it'd help me better understand how to optimize my code more than I do currently. As it is, I'm probably a "script kiddie" when it comes to assembly. A little knowledge is a dangerous thing. At least I know enough to know that and leave those sections to experts in their fields.
Clueless.Programming is a whole lot more than merely syntax and what to do with it. That sounds like:
learn words. Words mean things. Mean you words are.
Which is my impression of script kiddies. They're at the first rung of the ladder that leads to programming.
Which explains the extremely high quality of Excel and other MS Office products
Python and javascript are syntactically much more difficult to master than assembly language.
That's why there are so many assembly masters as compared to script kiddies, err, Python and JS "masters"? Or were you meaning to be funny? The mods certainly were clueless. (Interesting, really?)
Sorry to hear about your friend. I've always wondered whether a dose of HGH, either alone or combined with a some other hormones that are much lower as we age, would kick start the healing process and give an artificial bounce back for older people. I'm sure there would be side effects, but manipulating the body's systems in this fashion is something we are only starting to explore.
I'd have to agree with the AC a couple of threads above - the US engaged in this activity against the Indians even prior to becoming a country and continued into the 1900s on an ever reducing scale.
That major drop in vitality is directly related to your exercise level and genetics. Some have it earlier, some later, exercise can delay it for many. I suffered a drop and started eating better and exercising, and recovered most of the drop. Some will tell you for men that it's the drop in testosterone. I'm sure it has an effect. But knowing a 90 year old guy that still runs marathons and started in his mid 50s when he was overweight and on his way to a major heart attack tells me it's not the entire story.
And yet, the faster IT "develops", the more it seems like year x's crop reinvents the wheel, and several years later, the "hot" trend that was the silver bullet either really does have all the same flaws as yesteryear's tech, or brought in some new ones that made it an even worse choice.
The only thing that's developed rather rapidly is hardware, and that train has slowed relative to technology to take advantage of it. Software wise, some new tech has come out, but mostly existing tech has refined itself. Nothing I'd call revolutionary compared to what existed before.
Time
Hell, look at Keith Richards! That guy should have been dead long ago with all the chemicals he's put in his body, even with regular transfusions. YMMV
Who says he's not? Perhaps the first known zombie.
Seriously, or, I transferred to another college, why does Amazon care? If I rent from a physical location, and haul them myselves, does it matter to whom I rent them from?
I'll go back to my statement: posted rates. No difference for person A, B or C at provider 1. Provider 2 can have a different posted rate, but insurance just has to pay the middle going rate for non-emergency care, just like they do for auto repair.
It makes sense when you consider that huge software projects like that run on the order of ~$25,000,000.
That's what happens when you hire the likes of IBM consulting to write code for a project that isn't well defined.
Creaking? They're cemented together with blood, sweat, and duct tape that has solidified into a solid mass over the years. It's probably more stable than Roman mortar, given all the attempts to replace them. Have the original travel systems ever been replaced that travel agents used to look things up on?