I see they haven't reversed the horrible misfeature of the "awesome" bar being restricted to whatever's specified in the search bar (e.g., Wikipedia) instead of using your default search engine regardless.
Or is there an about:config setting for that which I don't know about?
That's a serious question. What two (or more) large groups of Americans would organize themselves into armies of any respectable amount of strength?
Anyone trying to fight a loyal US military would get squashed faster than you can say "daisy cutter", I don't care how many M-16s and RPGs you have in your basement bunker. Maybe mutiny, turning the US Army into God's Army? Or how about Walmart and Monsanto *really* putting the competition out of business?
The states that keep threatening secession: Would we go to war to keep them, or just tell them not to let the door hit 'em where the Lord split 'em?
What's most likely is that the next civil war will be manufactured by the people selling arms to both sides.
We're in a similar situation in our build/release group. The problem is that they want senior level talent at junior level wages, and until they can find such a sucker^Wcandidate, we continue to do without.
CO-supplied POE sounds like a tall order. One of the reasons CO-powered POTS works is because the CO supplies 48VDC (90VAC@20Hz ring), but the telephone equipment has to be able to work with much less voltage than that, and serious noise on the line. I suspect most POE devices expect much cleaner power.
Also, large chunks of the switch can go down, but as long as power stays up, existing calls through that switch stay up. New calls may not happen (no dial tone), though. This was true even in the days of mechanical step-switches. The calls always stayed connected until and unless something proactively broke the connection. When they went to electronic switching in the 1970s and 1980s, much effort was spent making sure this was still true. This was one of the weapons on the circuit side of the packet-switching versus circuit-switching wars.
The present issue is the last skirmish in that war. IMO packet-switching won that war the first time a telco installed a VOIP trunk from one CO to another. Everything since has been nuts-and-bolts buildout.
(Claimer: I wrote call processing software for telephone switches in the mid-1980s.)
I have lots of CFLs and their lifespan varies widely. I've had some going for almost five years now, and others didn't last five months, all indoors and on roughly the same duty cycle. I don't have too many LED bulbs yet, the oldest maybe 18 months, but none of them have failed yet. I guess LEDs don't have as much "infant mortality". OTOH, we have some incandescents that were here when we bought this house 17 years ago and are still humming along.
It'd be nice if we could get a nonbiased study of lifespans, changes in output, etc., based on a decent sample size and not connected with any manufacturer.
I'm surprised nobody's mentioned this. I work on a project that's spread across eight countries. The lingua franca is English, which makes me one of the lucky ones as a native English speaker. As you might guess, it's a pretty big project, so things like push-button refactoring aren't any use when someone misspells a variable name, or inadvertently names something after a swear word or a racial slur. (Or, more to the point, did so in acquired code that's now 12 years old and really shouldn't be touched if it's been working fine, and there's no staff for cosmetic changes anyway.)
People have talked about commenting and documentation. It's that much worse when someone's writing in their third language, or they write in their native language and you hope you can translate it well enough to get what they're really trying to say.
And then you've got all the cultural issues surrounding hierarchy, face and the loss thereof, egos, power, seniority, communication formats, and all that.
I'd love to have the luxury of being the lone cowboy, even if the PHBs were constantly jerking me around about what I'm supposed to be doing.
I've spent about half my 30-year career as an employee and half as a contractor (which I am now). When you count benefits and everything else, the difference in net cost to the client isn't as much as you'd think. The advantage to the client is disposability. While it may look like companies fire their employees as easily as they throw out their cafeteria trash, there's more overhead involved in getting rid of an employee (even without tenure, collective bargaining,etc.) and WAY more when hiring an employee than when renting and returning a contractor.
Speaking of net, my net income as a contractor (full-time, on-site) is not a whole lot different from the equivalent employee position. (YMMV, especially if you're an H1-B.) Of course, I bill short-term work much, much higher, but that's because there's less of it. I prefer the (very relative) stability of being on a full-time PSA versus billing a couple hours a week from a dozen different clients.
I'd be delighted if one of my kids told me he or she wanted to be an electrician. There will always be a demand, there are fun toys and interesting tech to play with, there are physical things you can look at and say, "I built that!", and unlike plumbers, you don't often deal with raw sewage.
You don't get vilified as lazy and overpaid by the lumpen like teachers, or publish-or-perish while bowing and scraping for grant money like professors. You're not in college and beyond until your late 20s or longer, like doctors, not to mention the insane student loan debt and crushing malpractice premiums.
And, you're not subject to the whims of either the stock market or PHBs or drunken executives the way we in the corporate world are.
I see they haven't reversed the horrible misfeature of the "awesome" bar being restricted to whatever's specified in the search bar (e.g., Wikipedia) instead of using your default search engine regardless.
Or is there an about:config setting for that which I don't know about?
Who was it who said, "Most scientific discoveries aren't hailed with 'Eureka!', but rather with, 'Hmmm, that's weird.'"?
There once was a babe born in space
The first of the whole human race
But the kid's DNA
Looked like bad macrame
Cos nobody shielded that place
Don't give me none of your aggravation, YIC!
Wouldn't a few humans amount to a small hill of beans pretty well?
Who would fight whom?
That's a serious question. What two (or more) large groups of Americans would organize themselves into armies of any respectable amount of strength?
Anyone trying to fight a loyal US military would get squashed faster than you can say "daisy cutter", I don't care how many M-16s and RPGs you have in your basement bunker. Maybe mutiny, turning the US Army into God's Army? Or how about Walmart and Monsanto *really* putting the competition out of business?
The states that keep threatening secession: Would we go to war to keep them, or just tell them not to let the door hit 'em where the Lord split 'em?
What's most likely is that the next civil war will be manufactured by the people selling arms to both sides.
We're in a similar situation in our build/release group. The problem is that they want senior level talent at junior level wages, and until they can find such a sucker^Wcandidate, we continue to do without.
But does a Cue:Cat count?
This is why for a long time, 50% of your phone bill was the cost of the bill.
CO-supplied POE sounds like a tall order. One of the reasons CO-powered POTS works is because the CO supplies 48VDC (90VAC@20Hz ring), but the telephone equipment has to be able to work with much less voltage than that, and serious noise on the line. I suspect most POE devices expect much cleaner power.
Also, large chunks of the switch can go down, but as long as power stays up, existing calls through that switch stay up. New calls may not happen (no dial tone), though. This was true even in the days of mechanical step-switches. The calls always stayed connected until and unless something proactively broke the connection. When they went to electronic switching in the 1970s and 1980s, much effort was spent making sure this was still true. This was one of the weapons on the circuit side of the packet-switching versus circuit-switching wars.
The present issue is the last skirmish in that war. IMO packet-switching won that war the first time a telco installed a VOIP trunk from one CO to another. Everything since has been nuts-and-bolts buildout.
(Claimer: I wrote call processing software for telephone switches in the mid-1980s.)
How long ago were those lines put in? How often are they inspected? You'd kind of expect an unmaintained 100-year-old sewer line to fail.
Part me out, pull the plug, burn me up, flush me down.
3 is prime, 5 is prime, 7 is prime, 9 is bad data, 11 is prime, 13 is prime...
SWEET16
I stopped flying once I proved that heavier-than-air flight is impossible.
Ham shack? 73? And you don't see the cosmic significance?
I have lots of CFLs and their lifespan varies widely. I've had some going for almost five years now, and others didn't last five months, all indoors and on roughly the same duty cycle. I don't have too many LED bulbs yet, the oldest maybe 18 months, but none of them have failed yet. I guess LEDs don't have as much "infant mortality". OTOH, we have some incandescents that were here when we bought this house 17 years ago and are still humming along.
It'd be nice if we could get a nonbiased study of lifespans, changes in output, etc., based on a decent sample size and not connected with any manufacturer.
Repeat after me: Money is not speech. Corporations are not people.
I'm surprised nobody's mentioned this. I work on a project that's spread across eight countries. The lingua franca is English, which makes me one of the lucky ones as a native English speaker. As you might guess, it's a pretty big project, so things like push-button refactoring aren't any use when someone misspells a variable name, or inadvertently names something after a swear word or a racial slur. (Or, more to the point, did so in acquired code that's now 12 years old and really shouldn't be touched if it's been working fine, and there's no staff for cosmetic changes anyway.)
People have talked about commenting and documentation. It's that much worse when someone's writing in their third language, or they write in their native language and you hope you can translate it well enough to get what they're really trying to say.
And then you've got all the cultural issues surrounding hierarchy, face and the loss thereof, egos, power, seniority, communication formats, and all that.
I'd love to have the luxury of being the lone cowboy, even if the PHBs were constantly jerking me around about what I'm supposed to be doing.
Mint+Mate is just fine for me. Nice to know I can hack it if the need arises, though.
Is 1MB RAM enough for the WinPrinter driver? Trying to rejuvenate my Packard-Bell.
I've spent about half my 30-year career as an employee and half as a contractor (which I am now). When you count benefits and everything else, the difference in net cost to the client isn't as much as you'd think. The advantage to the client is disposability. While it may look like companies fire their employees as easily as they throw out their cafeteria trash, there's more overhead involved in getting rid of an employee (even without tenure, collective bargaining,etc.) and WAY more when hiring an employee than when renting and returning a contractor.
Speaking of net, my net income as a contractor (full-time, on-site) is not a whole lot different from the equivalent employee position. (YMMV, especially if you're an H1-B.) Of course, I bill short-term work much, much higher, but that's because there's less of it. I prefer the (very relative) stability of being on a full-time PSA versus billing a couple hours a week from a dozen different clients.
I'd be delighted if one of my kids told me he or she wanted to be an electrician. There will always be a demand, there are fun toys and interesting tech to play with, there are physical things you can look at and say, "I built that!", and unlike plumbers, you don't often deal with raw sewage.
You don't get vilified as lazy and overpaid by the lumpen like teachers, or publish-or-perish while bowing and scraping for grant money like professors. You're not in college and beyond until your late 20s or longer, like doctors, not to mention the insane student loan debt and crushing malpractice premiums.
And, you're not subject to the whims of either the stock market or PHBs or drunken executives the way we in the corporate world are.
#define X 10000
#define Y -10000
#define Z MAXINT