hate to break it to you, but using a common approach in one industry, on a new industry, is, indeed, patentable.
I don't agree with this practice, but again, lets argue that point, not sit about and bitch about software patents when that is not the issue at hand.
They will give the vast majority of people a headache after 10 minutes. That's a fact!
I hope someone else gets the irony in this line.
A subjectively measured number of people have problem X and "thats a fact"
Really? I had no idea.
Did anyone actually read the patent?
The summary author is an idiot and clearly doesn't understand the patent or simply didn't read it.
They didn't patent measuring and charging for computer resources.
They patented predicting resource utilization at a particular point in the future and varying charging at that time.
They basically patented the ability to charge users hosting services with them based on response time and performance, they implemented this capability by predicting loads at a point in the future.
Sounds like they don't want to charge by the RAM/disk usage/CPU time etc anymore but would rather charge based on guaranteed performance.
Also this isn't a software patent at all. They effectively patented a business model.
If you want to argue the merits of that, fine, lets at least stick to the real issue.
your history of the bible is slightly misleading. The original Greek manuscripts that, some of which, would eventually be known as the new testament were written in the first century AD.
It wasn't till 315AD till the was really decided which of the manuscripts written would be part of 'The New Testament' so in many ways what picture the new testament paints wasn't created till several hundred years after the supposed events and the picture wasn't chosen by the original writers.
The king james bible wasn't printed until 1611AD and still included the Apocrypha. Even this version has some rather comical changes made in the process of translation compared to the original greek manuscripts.
TL;DR your right that the original manuscripts were written in the first century AD, your very wrong if you think the modern, common translations are accurate to the original and have not been tainted by thousands of years of corrupt church influence.
(i'm an atheist for the record btw)
More like this:
*Poly Sci Degree from USC
*Intelligence Specialist in Air force
*Unit Supply Specialist in Army (how do you get busted out of an intelligence job in the air force to being a lowly 'supply specialist' in the army?)
*Gets kicked out of the Army (involuntary honorable discharge)
*Guy with a poly sci degree and experience as a 'intelligence specialist' remains unemployed for 9 months and lives with daddy.
*Randomly writes a $10,000 check to run for seat.
*Raises 0 money, runs word of mouth campaign driving around in his '03 automobile.
*Gets hit with a felony pornography, gets public defender because hes broke.
*Wins Primary when polls indicated hardly anyone knew who he was.
How, on earth, is this entire situation NOT suspect to you?
The ultimate way to get 2 idiots who agree with each other to argue.
last 3 windows machines i've seen friends come home with had multiple partitions. The users never notice.
i don't think you quite understand the complexity of modern device drivers.
hard drive firmware where the code is just implementing a very well defined communication standard like ATA is an incredibly different beast from communicating with a programmable graphics card that supports multiple standards (opengl, directx, 2d accel, open cl) all at the same time. Especially when those API's have additional non-standard extensions. Similar complexity exists with other devices.
As for the last time i had to update my hard drive firmware. I haven't but a few million seagate customers have fairly recently
yea sounds great. Flashing my BIOS/EFI every time theres a driver update, can't wait.
GPT is part of the EFI standard.
It is used on some BIOS based system.
The problem with the standard MBR is that it does not support _partitions_ (note partitions, not disks) greater than 2 TB.
It also doesn't allow the start address to be higher than 2TB. This means your boot partition has to start in the first 2TB of the disk and be smaller than 2TB. The disk can actually be larger than 2TB.
traditional BIOS are an archaic nightmare really.
Most new technologies in them are work around hacks required to maintain some support for very old communication protocols (6GB SATA drives still have to support IDE mode why?) etc.
Give this a read:
I'm also an EE, i use 6 x 22" screens in a 3w x 2h setup using a single nvidia card and a pair of matrox triplehead2go units.
I've been using this setup for over a year or so and couldn't imagine doing design work efficiently on anything smaller.
My usual setup is something like:
1 screen with schematic
1 screen with board layout (or firmware IDE)
1 screen with e-mail/IM/etc
1 screen with browser
2 screens with datasheets or extra browsers or terminals
Some times i also need to work with multiple VM's / remote desktop connections and having a full screen for each one is great.
I would like to eventually change to 1 large center screen and rotate the 2 22" screens on the sides of it to a portrait orientation for better datasheet reading but thats not really possible right now under linux with the nvidia + triplehead2go approach
I'm hoping nvidia will put out a similar type of card as the ati linux drivers are pretty meh.
I've messed around with viewing things on all 6 monitors at once, movies/games. Never really liked it. I just need all the space.
Getting more monitors has been the biggest increase in my productivity since i left college, i can see the same being true for anyone doing design work on a computer (CAD, graphics editing, video editing, etc).
I think your just saying that your management sucked.
Sounds like they didn't realize that implementing correct monitoring infrastructure, testing infrastructure and using that data to optimize your production infrastructure was a long term cost savings over barreling ahead under the 'if it ain't broke don't fix it' ideal.
Sounds like a management failure not that the article didn't provide valuable information.
This is probably the first time I've seen the claim that thin clients _reduce_ network traffic.
Care to elaborate?
i think you misunderstood.
Know your apps means knowing their bottlenecks and how to alleviate them.
Some apps have high sustained disk reads, some writes.
Some have high amounts of random reads, some randoms writes, some both.
Some apps are I/O bound, some memory bound, some CPU bound.
The source of the app has nothing to do with your ability to monitor the operation of the app and determine its infrastructure needs.
The moon is made of green cheese. -- John Heywood
