That said, these particular fuses were from the 60s and are pretty much obsolete by todays standards. Taiwan almost certainly has their own fuses that are more sophisticated already.
Man, people sure are quick to write off Obama after the preacher thing. Did you not listen to his speech on the matter? It was probably the most well thought out speech on race from a politician ever. Also, listening to his preacher in context (not just the out of context Youtube clips) is important if you want to get the full story.
Also, people aren't judging McCain by his age, but by his stated dislike of computers. He still prefers handwritten memos to email for instance.
Hillary would never get votes from people who never vote Democratic anyway, so it's not exactly a major blow to her that die hard Republicans will never vote for her.
I've never understood why people find them so confusing in the first place. The concept is dirt simple: You tell the computer to look for X (usually the example here is a fixed string match) in your data. When it finds X, it tells you where it is. Magic!
Then you go on and explain wildcards, character classes, and subexpressions and you've covered 95% of what a regular person will use in day to day life, all in the span of about 5 minutes. The hardest part about using regular expressions is usually setting up all of the support stuff that the language makes you go through before using them (even the PCRE library has a fair bit of stuff you have to do to make a single match). That's the big reason they didn't take off until Perl came around IMHO, because they were just too much work for the payoff in pretty much every language up until then. Perl integrated them nicely at the core of the language and suddenly everybody stated using them.
To be fair, regular expressions in emacs lisp in 1997 were not exactly something for the faint of heart. Heck, the POSIX C regular expression library is a nightmare syntactically (all of the support code you need for a single expression is unbelievable). Hard as it is to believe, Perl actually made the syntax cleaner.
Despite being less self-documenting, I have never met a person who prefers to type [[:alnum:]] over \w.
That and getting into that kind of depth is usually a good way to find the bugs in your regular expression library. It's also an easy way to write code that will drive maintainers crazy.
Unless you're a hard core mathhead, that's probably not a good place to start with regexes IMHO. That's just going to scare people off from a highly useful tool. One generally does not need to rigorously prove that his regexes are going to work to use them. One does not have to use every feature of a language to make good use of it.
It all depends on if they have some family in with a business somewhere that would let them get dumped into management or if they're going to be asking "do you want fries with that"? Life is unfair like that. The good thing about an engineering degree is that you're almost guaranteed to be able to find a job somewhere. Engineers have useful skills that companies are looking for. Someone who majors in Women's studies and gets all As is going to have a tough time finding work unless they have a network already in place.
One gets the impression that the author of the article doesn't particularly like math though. I've gotta say he should probably consider switching majors now, because it's not going to be any better after he graduates if he continues on with the engineering degree. There is a lot of math in his classes because there will be a lot of math in his job in the real world with that degree.
Also, he has a point about the textbooks sucking. A lot of them are written by engineers and really do suck. I recommend not missing any classes and try to correlate what the professor teaches with the book as much as possible. A lot of the time those seemingly incomprehensible sections will actually be fairly simple once the professor explains it, but be warned that some professors are not above pulling test material straight from the book, so you better understand how the author thinks too.
I thought the point of the D-Block was to get the emergency responders out of the communication infrastructure business. They would buy basically cell phones (and stuff like cell phones repackages to work like walkie-talkies), and use them instead of their regular radios. In the event of an emergency, they would get first access to the cell network. This would also foster interoperability because you wouldn't have waveform/frequency mismatches between departments.
That said, it's a pretty scary requirement, which is one reason the FCC attached it to the otherwise highly desirable D block (one stop shopping for a "nationwide network"). I don't know how it was supposed to work, but at some level you have to have a "red line" in your NOC that can be called by emergency responders to tell you to start throttling call from regular joes (your customers!) who are probably trying to figure out if a loved one is safe in whatever disaster has just happened.
But that doesn't answer any of my practical questions. If you don't malloc it, how do you tell the OS you want it? Is it statically assigned to applications somehow? What happens when you need a whole lot of it, is there a way to give the OS a hint as to which one needs to be fast and which one can be slow? How would you tell the OS you don't need it anymore? Garbage collection? How do you tell the OS you want to keep that memory around after your application shuts down (or crashes!)? I know my feeble brain has not taken part of this revolution, but it seems oh so very magical right now to have all of this memory but no way of actually getting at it that I see (no OS calls, no malloc like device, I guess you could statically define everything but that would be like a straightjacket and would almost certainly be wildly wasteful as people over-allocated constantly).
This is an interesting point. I think most bittorrent users would agree that their websurfing doesn't seem to suffer much when BT is running, despite what you might expect.
Frankly, I think this article is a dirty trick. The author is talking about making the internet more "fair", but the ramification of his change is that ISPs will be able to charge more for "better" service if they want. In an attempt to make the network more fair, he could make it inherently unfair.
Back in 2000 I was buying different brands of CFLs to see how they would handle. The ones I bought from Wal*Mart (American Bulb or something) were absolutely terrible. The two bulbs together had noticeably different colors, they were slow to start, and they burnt out after only a few months. The bulbs that replaced them (Commercial Electric from Home Depot) are still running today, and all put out the same color light. Several of them (sadly not all) come up to 100% or near 100% right when you flick the switch too, although some of them start slow too.
The GE bulbs I have all take a second to turn on and are very dim before ramping up. Every fixture in my house where I can put one I have one of those CFLs. I rather enjoy not having to replace them. I still have a handful of incandescents (Oven light, Fridge light, a couple of recessed lights with sockets too small to fit the CFL bases, some of the candelabra bulbs (although I replaced the ones in our dining room because the design of the lamp overheated regular bulbs and caused them to burn out in only a couple of months), and the microwave.
Out of memory? You obviously failed to comprehend my previous post. The idea is that disk and memory are one and the same to the applications. Single level storage addressed exactly the same way. It can be made to run out of storage but you have to be malicious in intent to do so.
Isn't this called "Virtual Memory" or just "swap"? What's so special about it? I guess there's no such thing as a "file", you just malloc memory to get it, and your memory is automatically saved somehow? I guess that's a bit more convenient (although you would have to mark which memory you don't want saved), but not something I'd call revolutionary. I must be missing something here.
Stealing someone's internet bandwidth (their porn came down slower than usual!) is now worth up to three years in the slammer? I always thought wardriving was a silly little crime like jaywalking, not something on the order of grand theft auto. Why is the punishment so steep in that bill?
Read the rest of my post. While there is an electrical infrastructure in the US, there's not (yet) a system of stations where you can pay to recharge an electrical car. You will forever be driving into a store or something and asking the shopkeeper if you can plug into an outlet. It's just not very practical.
He also has to drive like a total asshole to do it. I appreciate his dedication to gaming the MPG counter on his car, but he's going to kill someone eventually, and if I was in his neighborhood I'm sure he'd drive me crazy when I end up behind him while he's creeping home at 15mph.
I thought the Tesla Motors cars were all electric? How do you intend to go cross country with an all electric car? I don't think the rules will allow for you to chase it with a big generator truck to recharge the car every 200 miles. The way the rules are written, it sounds to me like your car is pretty much going to have to be gasoline or diesel powered because that's the only way you're going to be able to refuel it when you're 1000 miles from home. Sneaking in behind shopping malls or something every 200 miles and plugging it into an outside wall outlet is probably not going to work.
I wish P2P designers would take a cue from the internet worm designers and prioritize "nearby" IP addresses first when choosing from a list (IE, if someone is in the same/16 as you, choose them over someone in a totally foreign network). My guess is that it would improve your throughput enough to make it worth the effort, and it would be really simple to add the logic.
If $500 is too much then it's probably not a great time to be trying to upgrade your machine anyway, at least not if you want a gaming rig. But I have to point out that if you shop around you don't have to pay top dollar like that. For instance, the Asus P5B is a perfectly workable motherboard equipped with Socket 775 (for your Core2Duo) for
$120. The lower end Core2Duos can easily be had for another $120, Memory is cheap. And you can even get a pretty good graphics card for under $200. Granted, this isn't top of the line parts (you have a lot of headroom on the C2D), but it would last for years assuming you don't want to run whatever the next Crytech-based game is.
Because chances are "Windows 7" is going to be Windows Server 2009, and basically Vista with some server stuff tossed in (and a much higher price tag).
Slashdot Mirror
That said, these particular fuses were from the 60s and are pretty much obsolete by todays standards. Taiwan almost certainly has their own fuses that are more sophisticated already.
Man, people sure are quick to write off Obama after the preacher thing. Did you not listen to his speech on the matter? It was probably the most well thought out speech on race from a politician ever. Also, listening to his preacher in context (not just the out of context Youtube clips) is important if you want to get the full story.
Also, people aren't judging McCain by his age, but by his stated dislike of computers. He still prefers handwritten memos to email for instance.
Hillary would never get votes from people who never vote Democratic anyway, so it's not exactly a major blow to her that die hard Republicans will never vote for her.
I've never understood why people find them so confusing in the first place. The concept is dirt simple: You tell the computer to look for X (usually the example here is a fixed string match) in your data. When it finds X, it tells you where it is. Magic!
Then you go on and explain wildcards, character classes, and subexpressions and you've covered 95% of what a regular person will use in day to day life, all in the span of about 5 minutes. The hardest part about using regular expressions is usually setting up all of the support stuff that the language makes you go through before using them (even the PCRE library has a fair bit of stuff you have to do to make a single match). That's the big reason they didn't take off until Perl came around IMHO, because they were just too much work for the payoff in pretty much every language up until then. Perl integrated them nicely at the core of the language and suddenly everybody stated using them.
To be fair, regular expressions in emacs lisp in 1997 were not exactly something for the faint of heart. Heck, the POSIX C regular expression library is a nightmare syntactically (all of the support code you need for a single expression is unbelievable). Hard as it is to believe, Perl actually made the syntax cleaner.
Despite being less self-documenting, I have never met a person who prefers to type [[:alnum:]] over \w.
That and getting into that kind of depth is usually a good way to find the bugs in your regular expression library. It's also an easy way to write code that will drive maintainers crazy.
Unless you're a hard core mathhead, that's probably not a good place to start with regexes IMHO. That's just going to scare people off from a highly useful tool. One generally does not need to rigorously prove that his regexes are going to work to use them. One does not have to use every feature of a language to make good use of it.
I fixed that for you.
Wow, that is some violent agreement there. I think I still have the bruises.
It all depends on if they have some family in with a business somewhere that would let them get dumped into management or if they're going to be asking "do you want fries with that"? Life is unfair like that. The good thing about an engineering degree is that you're almost guaranteed to be able to find a job somewhere. Engineers have useful skills that companies are looking for. Someone who majors in Women's studies and gets all As is going to have a tough time finding work unless they have a network already in place.
One gets the impression that the author of the article doesn't particularly like math though. I've gotta say he should probably consider switching majors now, because it's not going to be any better after he graduates if he continues on with the engineering degree. There is a lot of math in his classes because there will be a lot of math in his job in the real world with that degree.
Also, he has a point about the textbooks sucking. A lot of them are written by engineers and really do suck. I recommend not missing any classes and try to correlate what the professor teaches with the book as much as possible. A lot of the time those seemingly incomprehensible sections will actually be fairly simple once the professor explains it, but be warned that some professors are not above pulling test material straight from the book, so you better understand how the author thinks too.
I thought the point of the D-Block was to get the emergency responders out of the communication infrastructure business. They would buy basically cell phones (and stuff like cell phones repackages to work like walkie-talkies), and use them instead of their regular radios. In the event of an emergency, they would get first access to the cell network. This would also foster interoperability because you wouldn't have waveform/frequency mismatches between departments.
That said, it's a pretty scary requirement, which is one reason the FCC attached it to the otherwise highly desirable D block (one stop shopping for a "nationwide network"). I don't know how it was supposed to work, but at some level you have to have a "red line" in your NOC that can be called by emergency responders to tell you to start throttling call from regular joes (your customers!) who are probably trying to figure out if a loved one is safe in whatever disaster has just happened.
But that doesn't answer any of my practical questions. If you don't malloc it, how do you tell the OS you want it? Is it statically assigned to applications somehow? What happens when you need a whole lot of it, is there a way to give the OS a hint as to which one needs to be fast and which one can be slow? How would you tell the OS you don't need it anymore? Garbage collection? How do you tell the OS you want to keep that memory around after your application shuts down (or crashes!)? I know my feeble brain has not taken part of this revolution, but it seems oh so very magical right now to have all of this memory but no way of actually getting at it that I see (no OS calls, no malloc like device, I guess you could statically define everything but that would be like a straightjacket and would almost certainly be wildly wasteful as people over-allocated constantly).
It's a pretty good example of a company not learning from the past IMHO.
Raise your hands, how many of you have ever seen an actual real-life CD-i?
This is an interesting point. I think most bittorrent users would agree that their websurfing doesn't seem to suffer much when BT is running, despite what you might expect.
Frankly, I think this article is a dirty trick. The author is talking about making the internet more "fair", but the ramification of his change is that ISPs will be able to charge more for "better" service if they want. In an attempt to make the network more fair, he could make it inherently unfair.
Back in 2000 I was buying different brands of CFLs to see how they would handle. The ones I bought from Wal*Mart (American Bulb or something) were absolutely terrible. The two bulbs together had noticeably different colors, they were slow to start, and they burnt out after only a few months. The bulbs that replaced them (Commercial Electric from Home Depot) are still running today, and all put out the same color light. Several of them (sadly not all) come up to 100% or near 100% right when you flick the switch too, although some of them start slow too.
The GE bulbs I have all take a second to turn on and are very dim before ramping up. Every fixture in my house where I can put one I have one of those CFLs. I rather enjoy not having to replace them. I still have a handful of incandescents (Oven light, Fridge light, a couple of recessed lights with sockets too small to fit the CFL bases, some of the candelabra bulbs (although I replaced the ones in our dining room because the design of the lamp overheated regular bulbs and caused them to burn out in only a couple of months), and the microwave.
Alright, what did you guys do 7.5 million years ago to piss off some aliens halfway across the known universe? I'm looking at you holmedog.
Stealing someone's internet bandwidth (their porn came down slower than usual!) is now worth up to three years in the slammer? I always thought wardriving was a silly little crime like jaywalking, not something on the order of grand theft auto. Why is the punishment so steep in that bill?
Read the rest of my post. While there is an electrical infrastructure in the US, there's not (yet) a system of stations where you can pay to recharge an electrical car. You will forever be driving into a store or something and asking the shopkeeper if you can plug into an outlet. It's just not very practical.
He also has to drive like a total asshole to do it. I appreciate his dedication to gaming the MPG counter on his car, but he's going to kill someone eventually, and if I was in his neighborhood I'm sure he'd drive me crazy when I end up behind him while he's creeping home at 15mph.
I thought the Tesla Motors cars were all electric? How do you intend to go cross country with an all electric car? I don't think the rules will allow for you to chase it with a big generator truck to recharge the car every 200 miles. The way the rules are written, it sounds to me like your car is pretty much going to have to be gasoline or diesel powered because that's the only way you're going to be able to refuel it when you're 1000 miles from home. Sneaking in behind shopping malls or something every 200 miles and plugging it into an outside wall outlet is probably not going to work.
Maybe they're going to try an "all you can eat" model with a music selection that doesn't completely suck?
I wish P2P designers would take a cue from the internet worm designers and prioritize "nearby" IP addresses first when choosing from a list (IE, if someone is in the same /16 as you, choose them over someone in a totally foreign network). My guess is that it would improve your throughput enough to make it worth the effort, and it would be really simple to add the logic.
If $500 is too much then it's probably not a great time to be trying to upgrade your machine anyway, at least not if you want a gaming rig. But I have to point out that if you shop around you don't have to pay top dollar like that. For instance, the Asus P5B is a perfectly workable motherboard equipped with Socket 775 (for your Core2Duo) for $120. The lower end Core2Duos can easily be had for another $120, Memory is cheap. And you can even get a pretty good graphics card for under $200. Granted, this isn't top of the line parts (you have a lot of headroom on the C2D), but it would last for years assuming you don't want to run whatever the next Crytech-based game is.
Yeah, but that sounds like a killer idea. It drives me crazy that there isn't a central searchable repository for C modules like there is for Perl.
Because chances are "Windows 7" is going to be Windows Server 2009, and basically Vista with some server stuff tossed in (and a much higher price tag).