Comment Re:what a laugh (Score 1) 532
IMHO Sanders is equally good in the saying it like it is department but without the extra negativity and oversimplification of issues.
IMHO Sanders is equally good in the saying it like it is department but without the extra negativity and oversimplification of issues.
but you also are still pushing this over the same SAS/SATA connection, which means you approach a SSD's lower-end performance.
For non-cached data, I don't see these new 2.5" drives exceeding SATA's 6Gbps (about 600 MBps) or SAS's 12Gbps (1.2 GBps). By the time these get put into production, SATA and SAS 4 (or, who knows, 5) will already be out.
I think videos do have a place on slashdot and this feature just needs a major rework. I watch more tech-related videos on the BBC site than I do here. You guys should look to that for inspiration. On the Slashdot story page, I wouldn't mind seeing videos/pictures along with the text of the story.
Then you just write it in fancy sounding bullshit, and pass it off as a unique invention -- and the morons at the patent office, whose only real criteria is if the checks clear, will rubber stamp it and suddenly you have a patent.
To a great degree this is actually true. The patent officers don't care about the checks that much, though. It just creates a lot of work for them when they reject a patent claim and the lawyers of the people applying for the patent, i.e. prosecuting (that's the technical term) it prove them wrong and get their rejections overturned. It also shows badly on the record of the patent officer if their rejections tend to not hold up. The lawyers usually have more resources and motivation to make the patent pass through. So, the patent clerks tend to take the path of least resistance, i.e. approving the patents after doing their due diligence. Patent officers have a pre defined set of databases(including scientific journals, previous patents, etc) that they look through for prior art, and they don't look outside of that set (for example on Google) to find out if an idea is original. There is a fair amount of screening that goes into granting a patent for sure, and they don't just stamp anything. But they will stamp anything as long as their asses are covered. And they are really tiny asses that don't need a whole lot of cover.
Now when you bring up a case in court to invalidate somebody else's patent, that's when your lawyers will do all the google searches and thorough research to show that the invention was publicly known before the patent was granted. This research would go in front of a judge who will most likely rule in favor of whoever hired the bigger guns.
The problem with ideas in software (as opposed to, say, chemistry) is that they are generated far too quickly and anonymously to be included in formal databases and journals, even though they may be publicly known. I'll give you a rough example. Around the year 1998, you could use a plugin in Winamp called Geiss that showed trippy visualizations of music. Before that plugin (correct me if I'm wrong), music visualization was mostly just fancy waveforms. Apple lifted this idea wholesale and made it part of iTunes in 2001. Sony patented this idea in 2009. Poor Mr. Geiss got diddly squat for his invention, even though millions or even billions have probably used it till date, and his idea got patented more than a decade after conception. Such is the state of affairs: big tech companies go out and patent ideas that they learn from the general public. If the idea's implementation takes off, the patent provides them security, and if it doesn't, it's a bargaining chip to gouge money from anyone that tries to use the idea.
Regarding the patenting of ideas versus inventions, in theory you can only patent inventions, but the definition of what constitutes an invention is very lax, especially for software, and you don't have to go and show a working proof of concept to a patent officer. If the patent application describes the software in enough detail so as to allow an average programmer to develop it based on just the description, it's good enough to qualify. In other words, you can pretty much patent a piece of software at the requirements and architecture stage.
As far as replacing parts is concerned, you can always pop a new battery or memory card (at least on non-iOS devices). By the time a non-replaceable part is gone, chances are that other parts are also getting old and you probably need a new phone anyway. If you want to spare the money buy a ~$400+ phone, and if you don't, you can get a ~$100 model that does everything your old phone did, and use the old phone for a simpler purpose just like you would do with an old laptop. If you still insist on replacing the part, you can always go to a "mobile hospital" (there are literally hundreds here in India, and I've seen one or two in pretty much every major US city) and get the screen, camera, or charger port replaced. Spares are available for everything. If you did the same replacement on a Fairphone, the most you would be saving on is the labor that the mobile repair guy would be charging. And even that savings would probably get lost because the Fairphone modules would be costly because of their low volumes, proprietary physical interface, and 'ethical manufacturing'. Sure, it's ethical for the big picture and Gaia would be so happy, but it's probably cruel to my communications budget which is already getting bled dry paying ridiculous prices for mobile data. $10 for 3 long youtube videos over your data limit? It's highway robbery out there.
As far as actual customization goes, the smartphone OS and hardware ecosystem pretty much has you locked in place. You can't really remove any features. Want a phone without a camera? you'll either have a half-functional phone (no QR codes, etc.), or you'll have a buggy piece of shit. Maybe the developer of your favorite app did the right thing and added a check for a camera, but most likely he just programmed it to go straight to the camera and getImage(). Want a phone without a GPS to go with your tinfoil hat? It's most likely coupled with some other useful part (like a modem) in a module, and even if you could take it out, the Google WiFi SSID-based location system's already got your exact location within 3 feet as soon as you turn on the WiFi. Want a phone with a bigger camera? Why not get the extra processing power that it would end up needing anyways and get the newest and biggest Samsung, HTC or Xiaomi. Wanna upgrade GPU, CPU, RAM or root storage? Fuggedaboutit - It's probably soldered to the base phone and/or inside an SoC chip. Want a new OS? Good luck finding anything that is worth switching to and will run reliably unless your phone sold at least a 100,000 copies. Want a bigger battery or a wireless charging system? Most good and recent-ish phones can be easily fitted with one.
You can't compare the IBM PC platform to these SoC phones, and here's why:
1. The choice of internal components is very limited, and a lot of stuff is combined into one chip. There are 3-4 major SoC vendors out there. Same goes for the Camera CCDs, sensors, and all the chips that go in there. Compare that to the ~10 major graphics card and motherboard manufacturers in the market. Or the ~40 different types of CPUs you can install on a given motherboard socket.
2. Unlike a desktop OS with replaceable drivers, an Android OS image has to already have all the drivers it needs installed in the image. With a desktop OS you get an installer that lets you install it on any compatible hardware. With a smartphone OS, the install takes a team of 40 engineers 6 months of work, day and night, after which they release the OS image (which still has fucking bugs in it, mind you, till they iron half of them out with every +.001 version). Or some smart kid makes the install using Cyanogen or something in one all nighter, but it ends up having bugs that never go away because the kid got bored of the project or got hired to that team of 40 engineers.
3. The choice of manufacturers and models at different price points is simply fucking crazy. There are easily hundreds of smartphone/tablet manufacturers out there if you know how to look beyond what Best Buy/Verizon will sell you. You can pretty much customize by simply choosing the right phone for what you need.
4. Unless your phone usage is very different from the average user, there's almost no difference in the experience of using any of these devices. No matter how good your phone is, it's gonna get slow as fuck anyways once you actually start using it because you'll keep installing shit until it slows down, and then try to optimize it.
5. When a good Samsung falls out of your pocket, you get a few scratches and your Gorilla glass screen survives the drop. When a modular phone does the same, the floor is scattered with modules and pieces of your dignity. Oh, and that 100 megapixel camera module that you got for $400? nowhere to be found - probably fell into the hole with the cockroaches in it.
Don't get me wrong - these problems could all be ironed out and we may indeed have a truly awesome modular phone in our hands someday. It's just going to a take an industry-wide paradigm shift (and a mature and widely deployed version of Project Ara) for it to be actually useful. Until then, the most a Fairphone will do for you is make you the star of one coffee break where people finally notice your Code Monkey ringtone. If you're really desperate and work at Facebook or some shit, maybe, just maybe it might be worth it for that.
I don't see why this represents a serious objection. You would obviously have the vehicle software / sensor stack optimized for local conditions. Indian designers could rig it so that lights flashed and horns honked. Algorithms could be designed so that you could simulate bluff charges / random aggressive behavior / whatnot.
Really, from what I've seen of third world driving, a simple pseudo random number generator along with five or so stock behaviors (go, stop, go faster, swerve, swerve more) should do just fine.
You present the problem better than I do. In third world driving, the road is full of random actors like that, and in close enough proximity that any automated driving device/"stack" safe enough to be made road legal would keep the car stopped the whole time. I have a reverse sensor that pings if there's an obstruction some x feet away from the car. If I'm reversing out of parking into busy mixed vehicle/pedestrian traffic (and you have to in places), it just beeps constantly - if I was to go strictly by the sensor I'd probably have to wait hours. Bad third world traffic requires a human driver who also acts as a negotiator for the right of way, and has a sensor grid complex enough to sense every inch of the car, and has the human intelligence required to predict the actions of these random actors quick enough. I'm not saying it's impossible for self-driving to one day be good enough to use here. It's just that the state of the art is not as advanced right now. No amount of million dollar cars that can barely traverse the I-90 by itself will convince me that self-driving cars are going to be a thing any year soon. All kinds of automation is already used for safety features and assists and that will keep getting advanced, but autonomous driving throughout the world is still pretty far from real.
Actually, if you combine all different versions it beats even the 64bit integer. Techsmartly made a fancy pivot chart of it a while back: http://techsmartly.net/freePS3...
Well played, sir. Well played
A morsel of genuine history is a thing so rare as to be always valuable. -- Thomas Jefferson