It's rather quite simple, but you have several contributing factors other than electric cars being quite nice.
- Tesla tend to deliver in batches to different markets, so they get some real good months in the statistics.
- Added benefit for electric cars, like free parking in some areas(e.g privately regulated parking). And being alowed to drive in bus lanes(With heavy comuting from wealthy areas, you get many who can afford a Tesla to get an edge in the morning trafic).
- No general road tax and free pasing of toll roads.Norway have lots of those.
- No tax when buying one. Basicly you get it nerly at halve price compared to a gas car.
What country have you worked in where workers are more empowered to make decisions, and trusted to act independently?
Obviusly you have newer worked in scandinavia. From experience it seems the Americans tend to go for more bureaucracy and shuffle all requred descissions up in the system. And you often get the impression it's more important to cover your own ass, than get things done.
Microsoft had tablets before they became popular, too, but they didn't kick off the tablet craze.
They did not become popular, but the major factor for that was simply price. Those tablet was ridicolusly expesive, they cost 3-10 times a similary specced laptop(CPU/RAM/Disk). What was sold, was geared to special user scenarious suporting dedicated use cases. Not general consumer use.
Had affordable devices been avalible, the form factor would have had much more success earlier. Wich again would have led to better touch UI, by evolution. The market side would have ended up close to todays levels, but not with the expolsive growth. But a 5-10 years head start would have evened that out.
For anything designed the last 5 years it's more than likely that those pesky old 8051s have been replaced by ARMs, Coretex M0s, M3s and M4s
Actually, its not. For many applications, this would require rewriting of the software stack, for a chip with roughly the same die size and possibly less funcionality. 8051 is a microcontroller, not a microprocessor.
And that is exactly what those ARMs are, they are microcontrollers. It's several years since the ARM microcontrollers started to dip below the $1 pricetag becoming a valid cometitior in most microcontroller designs. Those cheap ARMs have more or less taken over the market for 16 bit micros, and are doing heavy inroadds in the typical 8bit martkets. If you have started a microcontroller based design the last 5-10 years and not included one or more ARM microcontrollers in the evaluation process, you have not done it right.
I would bet you have more 8051 microcontrollers running *today* than the whole sum of their desktop chips, including the low power, embedded/hardened lines.
Perhaps, depending on the age distributon of the equipment. For anything designed the last 5 years it's more than likely that those pesky old 8051s have been replaced by ARMs, Coretex M0s, M3s and M4s. So a more accurate statement should be"I would bet you have more ARM microcontrollers running *today* than the whole sum of their desktop chips, including the low power, embedded/hardened lines.
Well, what Microsoft is saying here is that FTC might not know how long the data needs to kept for things to work.
If this is the case, the software is completely broken and need to be redesigned or scraped.
Besides from a user point of view Microsoft does not provide any services where where storing of privacy data are needed at all(Apply to Google too). Obviously this does not include a regular customer database, as this is not what the FCC discuss in this case and such databases have already some regulation in place. What FCC discuss in this case is user profiling/spying.
Scrounging for loose change indeed. Seems like Canonical is feeling the effect of a failed and lacing business plan, and start to get desperate. Hype does not generate revenue after all.
Uhm, no. That is not correct RTFA. As it is, the Banshee developers elected to disable the store by default, preferring it to Canonicals split deal. The Banshee developers decided that requiring the users to manually activate the store, but giving GNOME a 100% cut was preferable.
Canonical asked the developers to choose from 2 options, but when their choice was not what Canonical wanted they simply did the opposite anyway.
Lots of interesting stuff out there in the world of micro-controllers, and now lot of it get available at reasonable prices. Not only as those dreaded $999 development kits.
If you look for something more powerful the STM32VLDISCOVERY http://www.st.com/internet/evalboard/product/250863.jsp, is a nice alternative at about $10.
You get a modern and powerful ARM Coretex M3 with 128 KB Flash and 8 KB RAM. With lots of nice peripherals included.
The owner then has 90 days to claim the property. Id. 2080.2. If the true owner fails to do so and the property is worth more than $250, then the police publish a notice, and 7 days after that ownership of the property vests in the person who found it,
Funny thing is, that if he had done that and delivered the phone to a local police station. It would more likely than not have been tossed into a lost and found bin, and become legally his after those 90 days. The phone was already disabled and contained no owner name, and barring the police officer receiving it being a hardcore Apple fan identifying it as a prototype, there was no obvious way to identify the owner. It would be handled like any other found phone, the police registering it and logging the name of the person turning it in. They would not care or bother with any further investigation as they have much more important task to handle. Combined with Apples taste for secrecy, it's not likely they would send people to surrounding police stations asking for the phone.
Seriously, how does this further harm the guy who lost it
Depend on Apples reaction on him loosing the device in the first place, but it's fairly likely he does not work there anymore. Then it's rather harmful.
Not too cool trying to get a new job known as the guy who lost a secret prototype of his former employers in a bar. Not exactly something to highlight on your resume.
You don't have to interact with Plasma all the time. You can have a old fashioned desktop and a taskbar/panel, and not be bothered with widgets and Plasma stuff.(Technically both the desktop and taskbar/panel are Plasma widgets, but that's really only a implementation detail you don't have to bother with).
First set your desktop containment(activity) to be a FolderView rather than Desktop(Desktop Settings->Appearance). Then select lock widgets.
You now have a plain regular desktop where you can put documents, no decoration pop up around widgets and the configuration button in the lower right corner is gone laving the space free for you and fits law.
The weight is not a problem, it's not really something you are going to carry around like a phone. As you say, it weight slightly less than your netbook which is a device with some of the same use cases. A pad like this will be a more stationary device, used for leisure net-surfing and light reading. The people behind the Crunch-pad had the right idea, coach computing. The main use for such a device will be in living room chairs or sofas, flipping trough web pages. For such use the keyboard and mouse/trackpad solutions on laptops/netbooks are just in the way, a good sized touch device will be much more usable.
The biggest problem on this device will be the screen, it's on the small side with it's 10". A 11-12" would be a better fit. And it does not have a very good resolution either.
Of course, building/prototyping hardware CAN be more expensive, but thinking of software development as "cheap" just because you can get a PC for ~$200 - yeah, well, no... not really.
You got it, building and prototyping hardware is more expensive period. Software development will always be cheaper on matching complexity levels. Even disregarding the ~$200 PC, going for a ~$1000 and adding a ~$50000 for development tools, you will still always come out ahead with SW development. Decent tools for hardware development does not come cheap, and considering the free tools for sw development its easier to cut cost there.
And after the initial investment, you only burn man hours with sw development. The compile-debug-compile cycles only cost time, where in hardware development each successive round of prototypes add the cost of parts and production. Not to mention the delay after the prototype design is finished until you get the produced part. If you think a 20min compile time is bad, try waiting one to eight weeks for your prototype before you can start testing and debugging it.
As CentOS is a repackage of RHEL, you should have at least one RHEL license if you are doing anything close to mission critical. If you get a problem on one of your CentOS servers, you can recreate it on your RHEL server, and get support from RedHat. Subsequently when the bug gets fixed, also get the fix for your CentOS servers.
For anything mission critical it's insane not to do that, otherwise you are gambling that not only some random RedHat customer get the same problem as you, but also that they report it so it has a chance to get fixed.
And in case you get a problem on CentOS that do not exist on RHEL, I'm betting the CentOS developers are
quick to help fix the issues.
What about the PyGTK and GTK websites. According to the download links the latest stable and updated PyGTK are for GTK 2.14, and GTK 2.16 has been out since the middle of March. For PyQt you don't find many minor releases of Qt that has not been followed by a updated PyQt release inside a week or two, for the last 5 years or so.
As for being comprehensive, the Qt bindings(at least PyQt) has a close to full coverage of the Qt classes. Last I checked PyGTK did not offer the same. And since Qt are not only a GUI library, the difference gets even larger as the bindings provide so much more.
My main issue is that Qt is pretty strongly tied to C++
This is repeated over and over again and even if people believe it, it' still not true. That is pure FUD.
Whereas GTK in C may be horrible, but the bindings to Python, Ruby and C# are all excellent
Fact is, the Qt bindings for those languages are more comprehensive and more up to date than the GTK counterparts. The Qt bindings all have powerful automatic tools for generating bindings for those languages, making it easy to keep up to date.
Slashdot Mirror
It's rather quite simple, but you have several contributing factors other than electric cars being quite nice.
- Tesla tend to deliver in batches to different markets, so they get some real good months in the statistics.
- Added benefit for electric cars, like free parking in some areas(e.g privately regulated parking). And being alowed to drive in bus lanes(With heavy comuting from wealthy areas, you get many who can afford a Tesla to get an edge in the morning trafic).
- No general road tax and free pasing of toll roads.Norway have lots of those.
- No tax when buying one. Basicly you get it nerly at halve price compared to a gas car.
What country have you worked in where workers are more empowered to make decisions, and trusted to act independently?
Obviusly you have newer worked in scandinavia. From experience it seems the Americans tend to go for more bureaucracy and shuffle all requred descissions up in the system. And you often get the impression it's more important to cover your own ass, than get things done.
Or the TI LAUNCHPAD boards, they are Cortex-M4Fs and quite capable.
And yoy have the Acorn NewsPAD from '96, you know from the gang that created the ARM :-)
http://acorn.chriswhy.co.uk/Co...
Microsoft had tablets before they became popular, too, but they didn't kick off the tablet craze.
They did not become popular, but the major factor for that was simply price. Those tablet was ridicolusly expesive, they cost 3-10 times a similary specced laptop(CPU/RAM/Disk). What was sold, was geared to special user scenarious suporting dedicated use cases. Not general consumer use.
Had affordable devices been avalible, the form factor would have had much more success earlier. Wich again would have led to better touch UI, by evolution. The market side would have ended up close to todays levels, but not with the expolsive growth. But a 5-10 years head start would have evened that out.
For anything designed the last 5 years it's more than likely that those pesky old 8051s have been replaced by ARMs, Coretex M0s, M3s and M4s
Actually, its not. For many applications, this would require rewriting of the software stack, for a chip with roughly the same die size and possibly less funcionality. 8051 is a microcontroller, not a microprocessor.
And that is exactly what those ARMs are, they are microcontrollers. It's several years since the ARM microcontrollers started to dip below the $1 pricetag becoming a valid cometitior in most microcontroller designs. Those cheap ARMs have more or less taken over the market for 16 bit micros, and are doing heavy inroadds in the typical 8bit martkets. If you have started a microcontroller based design the last 5-10 years and not included one or more ARM microcontrollers in the evaluation process, you have not done it right.
I would bet you have more 8051 microcontrollers running *today* than the whole sum of their desktop chips, including the low power, embedded/hardened lines.
Perhaps, depending on the age distributon of the equipment. For anything designed the last 5 years it's more than likely that those pesky old 8051s have been replaced by ARMs, Coretex M0s, M3s and M4s. So a more accurate statement should be"I would bet you have more ARM microcontrollers running *today* than the whole sum of their desktop chips, including the low power, embedded/hardened lines.
Or you could just skip the EEPROM and use a FRAM insted, they are just as cheap an have a quite nice 10^15 or higer write limit.
Well, what Microsoft is saying here is that FTC might not know how long the data needs to kept for things to work.
If this is the case, the software is completely broken and need to be redesigned or scraped.
Besides from a user point of view Microsoft does not provide any services where where storing of privacy data are needed at all(Apply to Google too). Obviously this does not include a regular customer database, as this is not what the FCC discuss in this case and such databases have already some regulation in place. What FCC discuss in this case is user profiling/spying.
Scrounging for loose change indeed. Seems like Canonical is feeling the effect of a failed and lacing business plan, and start to get desperate. Hype does not generate revenue after all.
Uhm, no. That is not correct RTFA. As it is, the Banshee developers elected to disable the store by default, preferring it to Canonicals split deal. The Banshee developers decided that requiring the users to manually activate the store, but giving GNOME a 100% cut was preferable. Canonical asked the developers to choose from 2 options, but when their choice was not what Canonical wanted they simply did the opposite anyway.
Lots of interesting stuff out there in the world of micro-controllers, and now lot of it get available at reasonable prices. Not only as those dreaded $999 development kits.
If you look for something more powerful the STM32VLDISCOVERY http://www.st.com/internet/evalboard/product/250863.jsp, is a nice alternative at about $10. You get a modern and powerful ARM Coretex M3 with 128 KB Flash and 8 KB RAM. With lots of nice peripherals included.
I wish Nokia provided some better alternatives to C++ for development on Symbian.
That is exactly what they just did! The way Qt extends C++ gives you a fast and powerful development environment, surpassing plain C++ big time.
The owner then has 90 days to claim the property. Id. 2080.2. If the true owner fails to do so and the property is worth more than $250, then the police publish a notice, and 7 days after that ownership of the property vests in the person who found it,
Funny thing is, that if he had done that and delivered the phone to a local police station. It would more likely than not have been tossed into a lost and found bin, and become legally his after those 90 days. The phone was already disabled and contained no owner name, and barring the police officer receiving it being a hardcore Apple fan identifying it as a prototype, there was no obvious way to identify the owner. It would be handled like any other found phone, the police registering it and logging the name of the person turning it in. They would not care or bother with any further investigation as they have much more important task to handle. Combined with Apples taste for secrecy, it's not likely they would send people to surrounding police stations asking for the phone.
Seriously, how does this further harm the guy who lost it
Depend on Apples reaction on him loosing the device in the first place, but it's fairly likely he does not work there anymore. Then it's rather harmful.
Not too cool trying to get a new job known as the guy who lost a secret prototype of his former employers in a bar. Not exactly something to highlight on your resume.
You don't have to interact with Plasma all the time. You can have a old fashioned desktop and a taskbar/panel, and not be bothered with widgets and Plasma stuff.(Technically both the desktop and taskbar/panel are Plasma widgets, but that's really only a implementation detail you don't have to bother with).
First set your desktop containment(activity) to be a FolderView rather than Desktop(Desktop Settings->Appearance). Then select lock widgets.
You now have a plain regular desktop where you can put documents, no decoration pop up around widgets and the configuration button in the lower right corner is gone laving the space free for you and fits law.
Or open System Settings and select Default Applications. Choose file manager and select Konqueror, then press Apply.
The weight is not a problem, it's not really something you are going to carry around like a phone. As you say, it weight slightly less than your netbook which is a device with some of the same use cases. A pad like this will be a more stationary device, used for leisure net-surfing and light reading. The people behind the Crunch-pad had the right idea, coach computing. The main use for such a device will be in living room chairs or sofas, flipping trough web pages. For such use the keyboard and mouse/trackpad solutions on laptops/netbooks are just in the way, a good sized touch device will be much more usable. The biggest problem on this device will be the screen, it's on the small side with it's 10". A 11-12" would be a better fit. And it does not have a very good resolution either.
You got it, building and prototyping hardware is more expensive period. Software development will always be cheaper on matching complexity levels. Even disregarding the ~$200 PC, going for a ~$1000 and adding a ~$50000 for development tools, you will still always come out ahead with SW development. Decent tools for hardware development does not come cheap, and considering the free tools for sw development its easier to cut cost there.
And after the initial investment, you only burn man hours with sw development. The compile-debug-compile cycles only cost time, where in hardware development each successive round of prototypes add the cost of parts and production. Not to mention the delay after the prototype design is finished until you get the produced part. If you think a 20min compile time is bad, try waiting one to eight weeks for your prototype before you can start testing and debugging it.
The "finally" is a bit strong, since it has been there for a while.
Using zypper dup worked flawlessly upgrading my 11.0 installs to 11.1. So I'll say you are at least one release to late with that one.
Privacy issues and other consideration does not matter, it boils down to one simple rule, never trust a insurance company!
As CentOS is a repackage of RHEL, you should have at least one RHEL license if you are doing anything close to mission critical. If you get a problem on one of your CentOS servers, you can recreate it on your RHEL server, and get support from RedHat. Subsequently when the bug gets fixed, also get the fix for your CentOS servers.
For anything mission critical it's insane not to do that, otherwise you are gambling that not only some random RedHat customer get the same problem as you, but also that they report it so it has a chance to get fixed.
And in case you get a problem on CentOS that do not exist on RHEL, I'm betting the CentOS developers are quick to help fix the issues.
For simulation, you can get Spice versions for all platforms.
For the CAD part, there is the EAGLE Light Edition from CadSoft http://www.cadsoftusa.com/freeware.htm It runs on Linux, Windows and Mac.
Do you have a source for that statement?
What about the PyGTK and GTK websites. According to the download links the latest stable and updated PyGTK are for GTK 2.14, and GTK 2.16 has been out since the middle of March. For PyQt you don't find many minor releases of Qt that has not been followed by a updated PyQt release inside a week or two, for the last 5 years or so.
As for being comprehensive, the Qt bindings(at least PyQt) has a close to full coverage of the Qt classes. Last I checked PyGTK did not offer the same. And since Qt are not only a GUI library, the difference gets even larger as the bindings provide so much more.
My main issue is that Qt is pretty strongly tied to C++ This is repeated over and over again and even if people believe it, it' still not true. That is pure FUD. Whereas GTK in C may be horrible, but the bindings to Python, Ruby and C# are all excellent Fact is, the Qt bindings for those languages are more comprehensive and more up to date than the GTK counterparts. The Qt bindings all have powerful automatic tools for generating bindings for those languages, making it easy to keep up to date.