that the citizens of the USA don't have a name that uniquely identifies them - "Canadians" come from Canada, "New Zealanders" come from New Zealand... but "Americans" come from America which happens to be a couple of continents containing dozens of countries ALL of whom can and do identify themselves as "Americans" - and in fact many are offended when citizens of the USA claim that title for just themselves - it's sort of the worst sort of cultural imperialism - taking someone's identity.
So, since the people from the USA wont come up with their own name for just themselves, the rest of the world has to do it for them, be it "USAians" or "Yanks" or "Starbucks" (I actually heard that one a while back) or "'merkins". The problem is that if you don't come up with the name yourselves there's a good chance you'll get saddled with one you don't like
Yup - of course - it's why I love programming (and quit doing chip design) - it's also why I do my best work at home and at 2am when no one's around (hint IRC is a bad thing:-).
I think it happens when you get enough of a project into your head so that you can see it all - you have to continue 'till it's all down - I find that my coding speed almost perfectly hits my typing speed (I'm a VERY fast hunt&peck typist - learned on a card punch)
I don't write perfect-the-first-time code, I spend some time during compile fixing silly typos, and tend to put off declaring simple variables like loop iterators and let the compiler 'remind' me - on the other hand I seem to get the architecture right because I can 'see it all'.
What I don't do is write really large things all at once - I like to write maybe 1-5000 lines then test them, get some simple functionality working, a place to stand and then continue with the next chunk. Debugging really big programs all at once is a bad idea.
Documentation is something you really have to work at, I tend to write small notes to myself as I work, then a few days later when the code is not so fresh go back make a pass through the code doing a better job - this gives me a small code review (I always find something stupid when I do this) and forces me to re-understand how everything works.
As I mentioned above I've spent a lot of time designing chips - as an experienced programmer coming to logic-design (now I have about 10-15 years of each) I've found I write much higher-level Verilog (looks like C) than those around me (most people in that space are experienced logic-designers who do some programming) - I find I can often turn out almost twice as many timed-tested gates than the others I work with - partly I think because working at a high level I can get my whole design in 'the zone' often my whole year's work would actually get designed in under a week (followed by all the back end testing, timing, routing, etc etc for the rest of the year). Historically logic designers have designed at a very low level - gates (kinda like coding in assembly), this is changing, but I think it tends to hide control structures (which are harder to design and debug) and stress data paths (which tend to be regular). The code-a-little-debug-a-little model is also really usefull for gates - write some simple test fixtures as you go (and do quick incremental timing runs on small chunks to make sure you're close to where you want to go). Of course the down side of finishing your gates first is that you always end up pioneering the backend layout flows:-(
It may also mean that many of the really interesting systems are running linux rather than windows - defacing a govt web server may be more interesting than hitting Joe Schmo's windows box
I agree - the book was a good read but the ending kinda sucked - I felt it was a cop-out - sure a twist, but kind of understated and not the grand explanation that the rest of the book seemed to be leading up to
don't forget TLG - he helped break the back of the original closed internet run by the big boys by helping make it possible for people to resell packets which lead to the mom&pop isp and lots of little customers rather than a few big ones which had been the 'net biz model up untill then. And of course one mustn't forget the WPS toilet-cam maybe one of the first web-trolls
Then you ought to be able to search those listings specifiying any number of parameters like TIME, SHOW, EPISODE, CHANNEL, etc... Sadly the basics of implementing this are covered by the "gemstar patent" nowdays owned by TV Guide.....
mind you I have my own threads package - you need to if you want 1,000,000+ really small threads running together, with totally minimal stack space (4 bytes not the 1Mb that pthreads gives you). The only hard part was making gprof use SIGALTSTACK (which was broken in the kernel when I started).
Of course this worked because from gprof's point of view I was running in one kernel thread - apart from that oprofile rocks:-)
how about a large US state school system, or some other country's national system?.... this would not only get them out from under the BSA/M$ threat but save them big bucks on both hardware and software long-term
As someone rightly said, the children in school mostly cannot grasp the significance of these words, so them saying "under God" isn't a big deal.
As athiests with children in the US school system we're very aware of all the "god stuff" that's thrown at them - on purpose we chose a primary school that didn't say the pledge so that they wouldn't be exposed to it and made to feel outsiders.
Kids see stuff in a very black-and-white way - it's hard to deal with this subject in the sensitive way that it needs to be dealt with - the ideas that we want to teach them which boil down to something like "religion is a silly thing that other people care about deeply, it's been the cause of countless war and suffering over the years and the world would be a better place if no one believed in it - HOWEVER it's also a very sensitive topic, people you have to deal with every day, who may be your friends have very deep beliefs and are overly sensitive about them, you have to be very carefull not to offend people you care about no matter how silly you may think their beliefs are"
Little kids will walk up to strangers on the street and tell them to stop smoking because it's bad for them - they have no social tact - teaching them how to live with the religious is hard. Having the govt. muddy the playing field makes it even harder
If you're not religious, you can deal with saying God, right?
well only without the capital "g" after all it's only a false meme
actually the issue has to do with dropping stuff on other countries, diplomatic incidents etc etc
Checking up I see I was slighly wrong - the organization was folded into the FAA a few years back. It's still independant of the people we normally have to get a permit for high-power flights under 100k ft
HPR people have been scaling up solids (using AP&rubber - basicly the same stuff the shuttle boosters use) for over a decade now - big AP rockets are not that unusual these days and have been flown to at least 100k ft (20 miles) - they are just expensive to build (propellent can cost several $1000).
100kft is a magic number - at that point the FAA loses juristiction (we fly the smaller stuff with FAA waivers) and you have to apply to a different part of the federal govt. - the paper work is pretty intimidating - it's designed to stop people dropping dangerous things on other countrys and causing international incidents.
Building amateur liquid propellent motors is hard - you have to get the fuel and oxidiser into the combustion chamber - that means a pressure higher than the chamber pressure - either a turbo pump - or a pressure system of some kind (for example gaseous O2 as an oxidiser at a high pressure, or an inert gas say N2 at pressure pushing a liquid say LOX or kerosene) pressure systems mean more weight.
One system we have been flying with recently is a hybrid based system - a liquid oxidiser with a solid fuel (basicly the combustion chamber's wall burn). It turns out that nitrous oxide (yes laughing gas) is a room-temp cryogenic liquid that self-pressurizes at above chamber pressure - this means it self-pumps and can be throttled. Paint ball tanks make great light-weight pressure vessels and nitrous is available at your local speed shop, flights are cheap. It does have some downsides - it burns so efficiently that rockets make no smoke and are hard to track, it's also hard to light (of course it gets real cold when it expands).
visitors are welcome, you come at your own risk of course, and we'll try and hit you up for a few bucks (because the BLM will make us pay for you, and we have to rent porta-potties). You can drive to the launch site in a street car and camp on the playa. We only do 3 launches a year so check the website for the right date.
While Ky's launch will probably be pretty private (if only for safety reasons) - AeroPac is having our first launch of the year at the same spot (BlackRock ) - Northern Nevada this weekend.
Sat and Sun mornings are the best time for launching (low winds) - the playa is BIG lots of room for recovery.... and camping
yeah but regional still means within country boundaries.... radio waves don't care - think about the city-pairs along the US-Mexico border where you can't just toss a cell tower up unless you known the freq is managed at a higher level - esp. on bands that have long propagation (for example the US band allocation is for some reason different from the rest of the world - as some people mentioned US hams step on other people broadcast SW bands - and vice versa) - countries do need to talk and that's in part why there's an ITU
it was only 20 odd years ago I was involved in a memory purchase for out B6700 - we paid roughly 1 million $$ for 1.5Mbytes of ram (core). And that came without any information in it.....
just because something can be done doesn't mean it should be done. what if they budgeted for exactly 5000 hours?
but you knew it was GPL'd up front when you decided to use it right? if so then you budgeted for it - either to replace it with your own or to negotiate a non-GPL license from the author. If you didn't do either then you're lying to yourself (or your boss) and you are going to screw yourself.
In the real world there are good reasons to use GPL and LGPL - it depends on what your goals are - GPL tends to encourage other people to add to your code and give it back to the greater community (Linux, KDE, Gnome etc)- long term you get back your stuff in a better state (and other stuff from other people) and you win - you help create a community of people who want to make stuff and share it with you - humans have been coming together in communities for all of recorded history because it's in our individual interests to live and work together.
On the other hand LGPL addresses a wider audience - you might have different reasons for using it - you like the idea of more people using your stuff, you want to be able to say "my code's running in that game/app/whatever", lots of people lent on you to LGPL it and you caved, you feel that with a wider audience more people will use it and you feel that forcing people to publish their changes to it will cause it to become better faster.
My point is of course that neither of these are necessarily "good" or "bad" but that they are vehicles of their authors and because those authors put their time and effort into the project thay get to choose the goals (and as a result the license) for their code - as a user you have the choice - either agree to the license or do it yourself
exactly - it's up to the writer of the 100 hour bit to decide how he/she wants to license it - GPL doesn't mean you HAVE to use someone's code - it just describes a particular set of conditions under which you can.
BTW 100 hours is a ridiculously small number - certainly below the threshold where even if you're considering licensing a commercial package it's probably not worth the lawyer time to write a contract
The run regular TDRs down cable segments which lets them know when something has changed (like you removed/added filters to get a service you didn't pay for)
They also have sniffers on their cable trucks - but not for the reason you think - they use frequencies on the cable that are used by other people in broadcast - if they radiate too much the FCC comes a knocking - a few years back they tried to shut down a TX cable plant that was interfering with air traffic control
IPC vs. MHz in Transmeta's world view is even more confusing - remember they are recompiling x86 instructions into their own native ones (somewhat) on the fly, assuming their code is doing good stuff (and I guess they are if they think it's worth upping the VLIW instruction size for future chips) - so an x86 instruction is being broken down into 1-3 micro-ops which are being packed spread over several 256-bit vliw instructions....
IBM is a BIG company, they not only have a research arm (who it seems do VLIW research - like many companies and universities - ILP research has been very popular the past decade or so) - but they also own fabs and build chips for people - I'm pretty sure they were building TM's first chips and that's what that article was really about.
Slashdot Mirror
So, since the people from the USA wont come up with their own name for just themselves, the rest of the world has to do it for them, be it "USAians" or "Yanks" or "Starbucks" (I actually heard that one a while back) or "'merkins". The problem is that if you don't come up with the name yourselves there's a good chance you'll get saddled with one you don't like
I think it happens when you get enough of a project into your head so that you can see it all - you have to continue 'till it's all down - I find that my coding speed almost perfectly hits my typing speed (I'm a VERY fast hunt&peck typist - learned on a card punch)
I don't write perfect-the-first-time code, I spend some time during compile fixing silly typos, and tend to put off declaring simple variables like loop iterators and let the compiler 'remind' me - on the other hand I seem to get the architecture right because I can 'see it all'.
What I don't do is write really large things all at once - I like to write maybe 1-5000 lines then test them, get some simple functionality working, a place to stand and then continue with the next chunk. Debugging really big programs all at once is a bad idea.
Documentation is something you really have to work at, I tend to write small notes to myself as I work, then a few days later when the code is not so fresh go back make a pass through the code doing a better job - this gives me a small code review (I always find something stupid when I do this) and forces me to re-understand how everything works.
As I mentioned above I've spent a lot of time designing chips - as an experienced programmer coming to logic-design (now I have about 10-15 years of each) I've found I write much higher-level Verilog (looks like C) than those around me (most people in that space are experienced logic-designers who do some programming) - I find I can often turn out almost twice as many timed-tested gates than the others I work with - partly I think because working at a high level I can get my whole design in 'the zone' often my whole year's work would actually get designed in under a week (followed by all the back end testing, timing, routing, etc etc for the rest of the year). Historically logic designers have designed at a very low level - gates (kinda like coding in assembly), this is changing, but I think it tends to hide control structures (which are harder to design and debug) and stress data paths (which tend to be regular). The code-a-little-debug-a-little model is also really usefull for gates - write some simple test fixtures as you go (and do quick incremental timing runs on small chunks to make sure you're close to where you want to go). Of course the down side of finishing your gates first is that you always end up pioneering the backend layout flows :-(
It may also mean that many of the really interesting systems are running linux rather than windows - defacing a govt web server may be more interesting than hitting Joe Schmo's windows box
I agree - the book was a good read but the ending kinda sucked - I felt it was a cop-out - sure a twist, but kind of understated and not the grand explanation that the rest of the book seemed to be leading up to
don't forget TLG - he helped break the back of the original closed internet run by the big boys by helping make it possible for people to resell packets which lead to the mom&pop isp and lots of little customers rather than a few big ones which had been the 'net biz model up untill then.
And of course one mustn't forget the WPS toilet-cam maybe one of the first web-trolls
Then you ought to be able to search those listings specifiying any number of parameters like TIME, SHOW, EPISODE, CHANNEL, etc... .....
Sadly the basics of implementing this are covered by the "gemstar patent" nowdays owned by TV Guide
mind you I have my own threads package - you need to if you want 1,000,000+ really small threads running together, with totally minimal stack space (4 bytes not the 1Mb that pthreads gives you). The only hard part was making gprof use SIGALTSTACK (which was broken in the kernel when I started). :-)
Of course this worked because from gprof's point of view I was running in one kernel thread - apart from that oprofile rocks
how about a large US state school system, or some other country's national system? .... this would not only get them out from under the BSA/M$ threat but save them big bucks on both hardware and software long-term
As someone rightly said, the children in school mostly cannot grasp the significance of these words, so them saying "under God" isn't a big deal.
As athiests with children in the US school system we're very aware of all the "god stuff" that's thrown at them - on purpose we chose a primary school that didn't say the pledge so that they wouldn't be exposed to it and made to feel outsiders.
Kids see stuff in a very black-and-white way - it's hard to deal with this subject in the sensitive way that it needs to be dealt with - the ideas that we want to teach them which boil down to something like "religion is a silly thing that other people care about deeply, it's been the cause of countless war and suffering over the years and the world would be a better place if no one believed in it - HOWEVER it's also a very sensitive topic, people you have to deal with every day, who may be your friends have very deep beliefs and are overly sensitive about them, you have to be very carefull not to offend people you care about no matter how silly you may think their beliefs are"
Little kids will walk up to strangers on the street and tell them to stop smoking because it's bad for them - they have no social tact - teaching them how to live with the religious is hard. Having the govt. muddy the playing field makes it even harder
If you're not religious, you can deal with saying God, right?
well only without the capital "g" after all it's only a false meme
ummm - you just posted to slashdot .... which runs on GPL'd software ...
actually the issue has to do with dropping stuff on other countries, diplomatic incidents etc etc
Checking up I see I was slighly wrong - the organization was folded into the FAA a few years back. It's still independant of the people we normally have to get a permit for high-power flights under 100k ft
you mean like these guys who fly from (roughly) the same spot?
gee I think you got each of them pegged exactly as I had (even Ky)
HPR people have been scaling up solids (using AP&rubber - basicly the same stuff the shuttle boosters use) for over a decade now - big AP rockets are not that unusual these days and have been flown to at least 100k ft (20 miles) - they are just expensive to build (propellent can cost several $1000).
100kft is a magic number - at that point the FAA loses juristiction (we fly the smaller stuff with FAA waivers) and you have to apply to a different part of the federal govt. - the paper work is pretty intimidating - it's designed to stop people dropping dangerous things on other countrys and causing international incidents.
Building amateur liquid propellent motors is hard - you have to get the fuel and oxidiser into the combustion chamber - that means a pressure higher than the chamber pressure - either a turbo pump - or a pressure system of some kind (for example gaseous O2 as an oxidiser at a high pressure, or an inert gas say N2 at pressure pushing a liquid say LOX or kerosene) pressure systems mean more weight.
One system we have been flying with recently is a hybrid based system - a liquid oxidiser with a solid fuel (basicly the combustion chamber's wall burn). It turns out that nitrous oxide (yes laughing gas) is a room-temp cryogenic liquid that self-pressurizes at above chamber pressure - this means it self-pumps and can be throttled. Paint ball tanks make great light-weight pressure vessels and nitrous is available at your local speed shop, flights are cheap. It does have some downsides - it burns so efficiently that rockets make no smoke and are hard to track, it's also hard to light (of course it gets real cold when it expands).
visitors are welcome, you come at your own risk of course, and we'll try and hit you up for a few bucks (because the BLM will make us pay for you, and we have to rent porta-potties). You can drive to the launch site in a street car and camp on the playa. We only do 3 launches a year so check the website for the right date.
While Ky's launch will probably be pretty private (if only for safety reasons) - AeroPac is having our first launch of the year at the same spot (BlackRock ) - Northern Nevada this weekend.
.... and camping
Sat and Sun mornings are the best time for launching (low winds) - the playa is BIG lots of room for recovery
yeah - besides I'm pretty sure I went on a maglev shuttle in Berlin at least 10 years ago - none of this is new
yeah but regional still means within country boundaries .... radio waves don't care - think about the city-pairs along the US-Mexico border where you can't just toss a cell tower up unless you known the freq is managed at a higher level - esp. on bands that have long propagation (for example the US band allocation is for some reason different from the rest of the world - as some people mentioned US hams step on other people broadcast SW bands - and vice versa) - countries do need to talk and that's in part why there's an ITU
8b) when you do 90 mph wearing a cape on one of those flying motorcycle thingies it flaps slowly in the breeze rather than trying to strangle you
it was only 20 odd years ago I was involved in a memory purchase for out B6700 - we paid roughly 1 million $$ for 1.5Mbytes of ram (core). And that came without any information in it .....
just because something can be done doesn't mean it should be done. what if they budgeted for exactly 5000 hours?
but you knew it was GPL'd up front when you decided to use it right? if so then you budgeted for it - either to replace it with your own or to negotiate a non-GPL license from the author. If you didn't do either then you're lying to yourself (or your boss) and you are going to screw yourself.
In the real world there are good reasons to use GPL and LGPL - it depends on what your goals are - GPL tends to encourage other people to add to your code and give it back to the greater community (Linux, KDE, Gnome etc)- long term you get back your stuff in a better state (and other stuff from other people) and you win - you help create a community of people who want to make stuff and share it with you - humans have been coming together in communities for all of recorded history because it's in our individual interests to live and work together.
On the other hand LGPL addresses a wider audience - you might have different reasons for using it - you like the idea of more people using your stuff, you want to be able to say "my code's running in that game/app/whatever", lots of people lent on you to LGPL it and you caved, you feel that with a wider audience more people will use it and you feel that forcing people to publish their changes to it will cause it to become better faster.
My point is of course that neither of these are necessarily "good" or "bad" but that they are vehicles of their authors and because those authors put their time and effort into the project thay get to choose the goals (and as a result the license) for their code - as a user you have the choice - either agree to the license or do it yourself
BTW 100 hours is a ridiculously small number - certainly below the threshold where even if you're considering licensing a commercial package it's probably not worth the lawyer time to write a contract
The run regular TDRs down cable segments which lets them know when something has changed (like you removed/added filters to get a service you didn't pay for)
They also have sniffers on their cable trucks - but not for the reason you think - they use frequencies on the cable that are used by other people in broadcast - if they radiate too much the FCC comes a knocking - a few years back they tried to shut down a TX cable plant that was interfering with air traffic control
IPC vs. MHz in Transmeta's world view is even more confusing - remember they are recompiling x86 instructions into their own native ones (somewhat) on the fly, assuming their code is doing good stuff (and I guess they are if they think it's worth upping the VLIW instruction size for future chips) - so an x86 instruction is being broken down into 1-3 micro-ops which are being packed spread over several 256-bit vliw instructions ....
IBM is a BIG company, they not only have a research arm (who it seems do VLIW research - like many companies and universities - ILP research has been very popular the past decade or so) - but they also own fabs and build chips for people - I'm pretty sure they were building TM's first chips and that's what that article was really about.