Hughes is typically called 'fraudband'- and from the recent implosion Clear's apparently undergoing and the spat with them and Sprint (with rumors of Sprint planning to go LTE here shortly...) they probably ought to be called that as well... >;-D
One defines a popular government. The other defines a publicly controlled government- but one that ultimately the people have less say in things.
For example, if a Republic was truly a Democracy, you'd find the President being elected by popular vote. Something that is not done here in the US.
In and of itself, your rant you link to wanders around and misses the distinction given at the beginning of it:
Democracy: From the Greek "demokratia", meaning "popular government" Republic: From the Latin "res publica", meaning "a public matter"
IF they were synonymous, they'd have similar etymologies to start off with. They DON'T. Who makes decisions in a Republic? Not the People directly. They choose who will represent them in government. In a Democracy, everything is decided by the people. What we have in this country is a Democratically Selected Republic as far as the US Federal government is concerned. Do you get to vote on ANY decisions whatsoever at the Federal level? No? Do you actually get to elect the President and Vice President? No?
It's NOT a Democracy.
More to the point, I think you'll find the classical definition of "Republic", from whom the etymology YOU quoted came from, was NOT Democratically elected- it was more of an oligarchy formed from the aristocrats that they called the Senate. Not a Democracy either, but still a Republic.
Heh...as a hint...don't be so bold as to tell people that they don't know how governments work or accuse them of failing fourth grade civics unless you're going to be correct there.
1) LED's are not harder to manufacture. They're actually on a par with CFLs for ease. 2) The reason the regs "require" a hazmat team is that there's a lot of things that "need" one per those regs- they've set the bar so low that saying this is silly. 3) Until LEDs got cheap enough and high enough performance (just about last year, if you're being honest with yourself...) CFLs were actually lower risk than the pollution (Mercury, Cadmium, etc...) that came from the coal fired plants needed to power the old answers. You exposed the environment and yourself to LESS Mercury with the bulb on an accidental breakage or a landfill mistake than with the incandescents.
Don't think I don't agree with your supposition- but you're not using the right arguments for it.;-)
Indeed. But if you want to avoid Mercury, you only need to spend 3 or so times the price and get the first generation of LED units that'll outlast the CFLs (in a ratio that's similarly priced to the CFLs you'd buy for the application in question) that're instant on, dimmable in many cases, and has the same phosphor issues, but no mercury whatsoever.
Having said this, the mercury in the CFL, while a real and serious problem, is actually less than the Mercury and Cadmium we put into the environment to power the current incarnation of Incandesents (HEI's are a different story, but since money talks and it's a more expensive proposition right now than either CFL or LED, you're not getting those...) is a bigger problem and health risk to everyone than the CFLs present if improperly disposed of or one gets busted.
Those that grouse about the Mercury in CFLs getting into the environment haven't a clue about what the old answer was doing. Yes, we can do better than that- and it looks like the answers might be arriving finally. But to go on and on about them on the basis of Mercury in them and saying they're bad is silly.
That's not wholly true. An incandescent CAN achieve them- the problem is that right at this moment, making one that does is uneconomical compared to CFLs and is a bit of a push with the LED systems that actually DO accomplish the replacements they claim to.
As someone that works in that playground, I can tell you that all of the tools on that page aren't chip design tools. Pretty much all of them are schematic capture for PCBs. You didn't find what you thought you did in your search...
For what he's doing, you'd need something more along the lines of the following links:
To be sure, there's more, but this is more in line with what he's doing. Do keep in mind, though, if he's designing FPGA configs instead of ASICs, you're going to need to use the VENDOR provided tools to do the work. I can assure you few, if any, supply OSX versions of their tools. I know of only one that's mostly supporting Linux in addition to Windows...Xilinx. Pretty much everyone else does Windows and ONLY Windows.
I'd question the wisdom of spending the cash he did for the MBP based on his requirements, but it's do what he's doing or pick up a similarly decked out PC class machine for nearly the same price-point. The only upshot would be that he'd have the OS he needed to run it on as the main OS then.
Shark's nice...but so's those two... So, I'd say not so much of a net gain there. Each to their own, I say... If you're happy with it, great- just don't fool yourself into thinking you've got the only answers in hand.
And don't start with your "I can buy a laptop for $100 at Fry's" bullshit. Because everyone with more than two functioning neurons knows that that laptop will be in the dumpster, broken, in less than a year, whereas the Mac laptop will, by and large, be chugging along at the five to ten year mark.
Heh... I spent $1200 on my latest personal laptop and it's actually more agressive than the $1900 price ranged model.
Sure, you can spend $4k on a laptop (Current employer...) but you're talking an i7 with 16GB of RAM and the top of the line Mobile NVidia Quadro in it. Most of that expense is due to the insane amount of RAM and the Quadro in the thing. Apple doesn't provide that to the best of my knowledge- and if they did, you'd shell out as much as the company did.
Also worth noting: I don't buy your line there on the quality...
The only thing you're paying for is the "stability" that the constrained hardware Apple provides with OSX machines- that and the prestige price of buying Apple.
Heh...the same might be said of either of the other two main OSes out there. Even doing a VM can have it's own set of fun- it's not a magic bullet for everything.
You honestly do want to try to get as close to the target as you can. Less pain. Try doing embedded Linux development on Windows 7...it's...not...fun. The closer you can get to the OS, the better things work for you overall.
It's not QUITE as hard as you're making it out to be. If it were, then the Android hacker crowd would not be able to hack Honeycomb onto the Nook Color with an SD (and now even onto the system flash...) in only a couple month's time.
1) Resistive screen. While it's "okay", it doesn't do multitouch well (if at all) and it's not as responsive as the capacitive ones. Upshot of the resistive screen is that you don't need special gloves or a stylus when it's cold, etc.
2) It's an ARM-9 SoC. The Nook uses an OMAP3 (Cortex-A8...). This means it's ssssslllllooooowww compared to the A8 based stuff- and we won't get into the story with the A9 tablets just beginning to show up.
3) It doesn't do 3D like the Nook does. It doesn't have DSP support for video decode.
For ~$100 less than the Nook, you will have a tablet, yes...but don't kid yourself that you're doing better than you'd do getting a Nook or nabbing a Viewsonic tablet for ~$250-350.
There's probably only about $100 worth of "loss" there since it's similar in nature to the Viewsonic G and they're selling for $350 right at the moment. I think you might be right on a jump overall- but it's not as major as people seem to think it is. And I think most are putting the Nook app onto it when it's been rooted or booted with Froyo or Honeycomb. I know it was the first app I pushed to my SD card boot image.:-D
Little use in rooting a Kobo, I'm suspecting. Limited button space and unless you can talk to it via the WiFi or the USB jack, you're not getting much use past what's already there. The Aluratek's pretty close to the same issues, I suspect (I looked at both, own a Kobo for just reading e-novels, etc...).
If memory serves, it's "locked down", it's just that you can put it into full developer mode without any real jailbreaking on the N900, much like the N8x0 and N770 before it (I've got a Red Pill mode N800 lying around somewhere...).
Past the minor border discrepancies in some things that depend on orientation, and the occasional lag on the accelerometer info, the Honeycomb image works pretty well, all things considered (It's such that I question them holding back the full release of the typically FOSS portions of the distribution for 3.0...seriously...). No, it's not for John Q. Public- but if you're rooting the thing, you're already more technically advanced and can manage with the "pre-release" version on the thing.
Heh... It took all of about 10-15 minutes tops. I've been running Honeycomb on it for a bit now and I must say that while the build's got rough edges, it's good enough to allow me to properly target the games I want to make to the upcoming tablets as well as to phones.
Slashdot Mirror
I think that was the point I was reaching for there... Thanks!
I think that they meant that they're just a bit less concerned with trains being 20 seconds behind as "late".
Hughes is typically called 'fraudband'- and from the recent implosion Clear's apparently undergoing and the spat with them and Sprint (with rumors of Sprint planning to go LTE here shortly...) they probably ought to be called that as well... >;-D
I would contend that the first is a good example of the original assertion and the second is as you claim.
One defines a popular government.
The other defines a publicly controlled government- but one that ultimately the people have less say in things.
For example, if a Republic was truly a Democracy, you'd find the President being elected by popular vote. Something that is not done here in the US.
In and of itself, your rant you link to wanders around and misses the distinction given at the beginning of it:
IF they were synonymous, they'd have similar etymologies to start off with. They DON'T. Who makes decisions in a Republic? Not the People directly. They choose who will represent them in government. In a Democracy, everything is decided by the people. What we have in this country is a Democratically Selected Republic as far as the US Federal government is concerned. Do you get to vote on ANY decisions whatsoever at the Federal level? No? Do you actually get to elect the President and Vice President? No?
It's NOT a Democracy.
More to the point, I think you'll find the classical definition of "Republic", from whom the etymology YOU quoted came from, was NOT Democratically elected- it was more of an oligarchy formed from the aristocrats that they called the Senate. Not a Democracy either, but still a Republic.
Heh...as a hint...don't be so bold as to tell people that they don't know how governments work or accuse them of failing fourth grade civics unless you're going to be correct there.
1) LED's are not harder to manufacture. They're actually on a par with CFLs for ease.
2) The reason the regs "require" a hazmat team is that there's a lot of things that "need" one per those regs- they've set the bar so low that saying this is silly.
3) Until LEDs got cheap enough and high enough performance (just about last year, if you're being honest with yourself...) CFLs were actually lower risk than the pollution (Mercury, Cadmium, etc...) that came from the coal fired plants needed to power the old answers. You exposed the environment and yourself to LESS Mercury with the bulb on an accidental breakage or a landfill mistake than with the incandescents.
Don't think I don't agree with your supposition- but you're not using the right arguments for it. ;-)
Indeed. But if you want to avoid Mercury, you only need to spend 3 or so times the price and get the first generation of LED units that'll outlast the CFLs (in a ratio that's similarly priced to the CFLs you'd buy for the application in question) that're instant on, dimmable in many cases, and has the same phosphor issues, but no mercury whatsoever.
Having said this, the mercury in the CFL, while a real and serious problem, is actually less than the Mercury and Cadmium we put into the environment to power the current incarnation of Incandesents (HEI's are a different story, but since money talks and it's a more expensive proposition right now than either CFL or LED, you're not getting those...) is a bigger problem and health risk to everyone than the CFLs present if improperly disposed of or one gets busted.
Those that grouse about the Mercury in CFLs getting into the environment haven't a clue about what the old answer was doing. Yes, we can do better than that- and it looks like the answers might be arriving finally. But to go on and on about them on the basis of Mercury in them and saying they're bad is silly.
That's not wholly true. An incandescent CAN achieve them- the problem is that right at this moment, making one that does is uneconomical compared to CFLs and is a bit of a push with the LED systems that actually DO accomplish the replacements they claim to.
As someone that works in that playground, I can tell you that all of the tools on that page aren't chip design tools. Pretty much all of them are schematic capture for PCBs. You didn't find what you thought you did in your search...
For what he's doing, you'd need something more along the lines of the following links:
http://www.verilog.net/free.html
http://www.iti.uni-stuttgart.de/~bartscgr/signs/wiki/index.php/Main_Page
To be sure, there's more, but this is more in line with what he's doing. Do keep in mind, though, if he's designing FPGA configs instead of ASICs, you're going to need to use the VENDOR provided tools to do the work. I can assure you few, if any, supply OSX versions of their tools. I know of only one that's mostly supporting Linux in addition to Windows...Xilinx. Pretty much everyone else does Windows and ONLY Windows.
I'd question the wisdom of spending the cash he did for the MBP based on his requirements, but it's do what he's doing or pick up a similarly decked out PC class machine for nearly the same price-point. The only upshot would be that he'd have the OS he needed to run it on as the main OS then.
I chuckled when I read that- I'd have to agree with the sentiment.
(Not that I'm not going to challenge some of the Mac Fan assertions that're off or wrong in this discussion all the same... >:-D)
It didn't look like all that much hard work...they've kind of simplified the whole process as best as I can tell.
Heh...you sure he's not already in the progress with doing that? Seems they're doing stuff with ARM...again... >:-D
Heh...
SysProf
OProfile
Shark's nice...but so's those two... So, I'd say not so much of a net gain there. Each to their own, I say... If you're happy with it, great- just don't fool yourself into thinking you've got the only answers in hand.
Heh... I spent $1200 on my latest personal laptop and it's actually more agressive than the $1900 price ranged model.
Sure, you can spend $4k on a laptop (Current employer...) but you're talking an i7 with 16GB of RAM and the top of the line Mobile NVidia Quadro in it. Most of that expense is due to the insane amount of RAM and the Quadro in the thing. Apple doesn't provide that to the best of my knowledge- and if they did, you'd shell out as much as the company did.
Also worth noting: I don't buy your line there on the quality...
The only thing you're paying for is the "stability" that the constrained hardware Apple provides with OSX machines- that and the prestige price of buying Apple.
Heh...the same might be said of either of the other two main OSes out there. Even doing a VM can have it's own set of fun- it's not a magic bullet for everything.
You honestly do want to try to get as close to the target as you can. Less pain. Try doing embedded Linux development on Windows 7...it's...not...fun. The closer you can get to the OS, the better things work for you overall.
It's not QUITE as hard as you're making it out to be. If it were, then the Android hacker crowd would not be able to hack Honeycomb onto the Nook Color with an SD (and now even onto the system flash...) in only a couple month's time.
Biofuels are largely zero net increasing in CO2 emissions. They're peeling out the CO2 that's already THERE in the environment.
1) Resistive screen. While it's "okay", it doesn't do multitouch well (if at all) and it's not as responsive as the capacitive ones. Upshot of the resistive screen is that you don't need special gloves or a stylus when it's cold, etc.
2) It's an ARM-9 SoC. The Nook uses an OMAP3 (Cortex-A8...). This means it's ssssslllllooooowww compared to the A8 based stuff- and we won't get into the story with the A9 tablets just beginning to show up.
3) It doesn't do 3D like the Nook does. It doesn't have DSP support for video decode.
For ~$100 less than the Nook, you will have a tablet, yes...but don't kid yourself that you're doing better than you'd do getting a Nook or nabbing a Viewsonic tablet for ~$250-350.
There's probably only about $100 worth of "loss" there since it's similar in nature to the Viewsonic G and they're selling for $350 right at the moment. I think you might be right on a jump overall- but it's not as major as people seem to think it is. And I think most are putting the Nook app onto it when it's been rooted or booted with Froyo or Honeycomb. I know it was the first app I pushed to my SD card boot image. :-D
Little use in rooting a Kobo, I'm suspecting. Limited button space and unless you can talk to it via the WiFi or the USB jack, you're not getting much use past what's already there. The Aluratek's pretty close to the same issues, I suspect (I looked at both, own a Kobo for just reading e-novels, etc...).
If memory serves, it's "locked down", it's just that you can put it into full developer mode without any real jailbreaking on the N900, much like the N8x0 and N770 before it (I've got a Red Pill mode N800 lying around somewhere...).
Past the minor border discrepancies in some things that depend on orientation, and the occasional lag on the accelerometer info, the Honeycomb image works pretty well, all things considered (It's such that I question them holding back the full release of the typically FOSS portions of the distribution for 3.0...seriously...). No, it's not for John Q. Public- but if you're rooting the thing, you're already more technically advanced and can manage with the "pre-release" version on the thing.
Heh... It took all of about 10-15 minutes tops. I've been running Honeycomb on it for a bit now and I must say that while the build's got rough edges, it's good enough to allow me to properly target the games I want to make to the upcoming tablets as well as to phones.
...the Judge's decision. I thought only an Appeals Court can do that, not an AGENCY of the Administration.
So, will "modern" OO teach them a quicksort or any other base algorithmic concepts ANY better? No? Might I suggest a bit of restraint on your remarks?
You're being no better than you're accusing of the professors- that of being a bit of a snob.