There's no particular reason for that though. Rebuild/replacement is not expected to be done frequently so they don't design for that. I have had the transmission out of my car exactly one in its 13 years/230000 miles and that was for a clutch replacement. Having done it myself, I can say that there is exactly nothing that would have prevented it being designed to be an extremely simple process. It would simply have been a waste of time and have been less optimal functionally.
Executive A has to decide whether to source several millions of his investors money into a risky proposition which could, in principle, bomb, leaving the executive's career in ruins. In addition, because of this risk, executive will be tempted to meddle in the creative process.
vs
Many thousands of people willing to risk some money (say 20-30) on a project they would dearly love to come to fruition. Due to low risk and trust in the creative vision of the people proposing the project, the project will get created as it was meant to be with little to no interference.
There aren't really system objects in the same way on Linux since no COM (or whatever Microsoft is calling it this week). Nonetheless, I think something similar could be brought to bear and some of the same benefits could be realized.
Powershell implements a few ideas I'd been wishing for in scripting languages for a while (notably piping objects). I'll still use Perl over it in a heartbeat because those warts, they're of Lemmy from Motorhead stature. Instantiating object is powerful but awkward for simple tasks (And one script I found lists about six different options for which object to complete the same task - see below*) and STDIN and STDOUT handling gives a serious headache for certain tasks.
Still, definitely some good ideas to pick from.
(OK, this isn't powershell but I think it applies equally) *
' Set Http = CreateObject("WinHttp.WinHttpRequest.5.1") ' Set Http = CreateObject("WinHttp.WinHttpRequest.5") ' Set Http = CreateObject("WinHttp.WinHttpRequest") ' Set Http = CreateObject("MSXML2.ServerXMLHTTP") ' Set Http = CreateObject("MSXML2.XMLHTTP")
Set Http = CreateObject("Microsoft.XMLHTTP")
Yep, just what I wanted for a simple three liner script, adjust the security policy of the whole machine. Which I may not even have access to anyway and could necessitate several layers of bureaucracy and will not be worth it for the small benefit my script gives.
I found a work around in the end. So this restriction didn't even provide the security it purported to, it just made my life more needlessly complex. This is the exact opposite of what scripting is supposed to be.
Don't get me wrong. Though I'm not a Windows guy, Powershell is a good step in the right direction and has some quite nifty features. In a generation or two, it might even have been slick. There was just no need for Microsoft to cripple it like that.
King of Swamp Castle: When I first came here, this was all swamp. Everyone said I was daft to build a castle on a swamp, but I built in all the same, just to show them. It sank into the swamp. So I built a second one. That sank into the swamp. So I built a third. That burned down, fell over, then sank into the swamp. But the fourth one stayed up. And that's what you're going to get, Lad, the strongest castle in all of England.
There's always the dead-letter-drop option. Encrypt and leave in a public place. They could still trace to a degree but if there's enough noise to signal...
Border patrol operates quite far from the border these days. I was quite surprised to be stopped on 40 in New Mexico at a checkpoint. As an immigrant, I was glad I had my green card with me (though I had no idea I would be needing it) though I'm sure I could have gotten away with lying about being an American citizen.
I'd watch that "Expected", that's caught people out before. It's quite possible that high mortality rates encourage high breeding rates. Whilst there's bound to be some inertia, knowing that if you only have three kids, there's a good chance they will be around to support you in your own age and more will more likely be a burden in the immediate term might be enough to restrict growth somewhat.
Throwing money at a problem can also make it worse. Particularly where corruption is at play. Congratulations, your food relief just allowed the local warlord to upgrade his automatic weapons.
Slashdot Mirror
There's no particular reason for that though. Rebuild/replacement is not expected to be done frequently so they don't design for that. I have had the transmission out of my car exactly one in its 13 years/230000 miles and that was for a clutch replacement. Having done it myself, I can say that there is exactly nothing that would have prevented it being designed to be an extremely simple process. It would simply have been a waste of time and have been less optimal functionally.
So it's just a question whether it's for the 2nd, 3rd or 4th time.
Even better, compare:
Executive A has to decide whether to source several millions of his investors money into a risky proposition which could, in principle, bomb, leaving the executive's career in ruins. In addition, because of this risk, executive will be tempted to meddle in the creative process.
vs
Many thousands of people willing to risk some money (say 20-30) on a project they would dearly love to come to fruition. Due to low risk and trust in the creative vision of the people proposing the project, the project will get created as it was meant to be with little to no interference.
Our grandkids will tell us "F*ck you" and sell us for rendering for the fat. And serve us right.
There aren't really system objects in the same way on Linux since no COM (or whatever Microsoft is calling it this week). Nonetheless, I think something similar could be brought to bear and some of the same benefits could be realized.
Powershell implements a few ideas I'd been wishing for in scripting languages for a while (notably piping objects). I'll still use Perl over it in a heartbeat because those warts, they're of Lemmy from Motorhead stature. Instantiating object is powerful but awkward for simple tasks (And one script I found lists about six different options for which object to complete the same task - see below*) and STDIN and STDOUT handling gives a serious headache for certain tasks.
Still, definitely some good ideas to pick from.
(OK, this isn't powershell but I think it applies equally)
*
' Set Http = CreateObject("WinHttp.WinHttpRequest.5.1")
' Set Http = CreateObject("WinHttp.WinHttpRequest.5")
' Set Http = CreateObject("WinHttp.WinHttpRequest")
' Set Http = CreateObject("MSXML2.ServerXMLHTTP")
' Set Http = CreateObject("MSXML2.XMLHTTP")
Set Http = CreateObject("Microsoft.XMLHTTP")
FWIW, I think the work-around was calling powershell with my script as the parameter instead of calling my script directly.
Yep, just what I wanted for a simple three liner script, adjust the security policy of the whole machine. Which I may not even have access to anyway and could necessitate several layers of bureaucracy and will not be worth it for the small benefit my script gives.
I found a work around in the end. So this restriction didn't even provide the security it purported to, it just made my life more needlessly complex. This is the exact opposite of what scripting is supposed to be.
Don't get me wrong. Though I'm not a Windows guy, Powershell is a good step in the right direction and has some quite nifty features. In a generation or two, it might even have been slick. There was just no need for Microsoft to cripple it like that.
King of Swamp Castle: When I first came here, this was all swamp. Everyone said I was daft to build a castle on a swamp, but I built in all the same, just to show them. It sank into the swamp. So I built a second one. That sank into the swamp. So I built a third. That burned down, fell over, then sank into the swamp. But the fourth one stayed up. And that's what you're going to get, Lad, the strongest castle in all of England.
I think you two are on the same side but you've crossed wires.
This is like suggesting that SSH should take telnet connections for backwards compatibility.
A kettle costs $10.
Very hard to do. Sooner or later they will be able to tie your identity to your email address and then you're done.
This is essentially how freenet works (for various definitions of "work")
There's always the dead-letter-drop option. Encrypt and leave in a public place. They could still trace to a degree but if there's enough noise to signal...
Exactly, when I was an email admin, our server was set to negotiate TLS when available. The vast majority of the time, emails went in the clear.
Did she get hit by a bus?
(It's Tamm)
Lara Croft is fiction.
50 mile treks through jungle or ultra-marathons
Now, that's going to make a thrilling Bond film.
Border patrol operates quite far from the border these days. I was quite surprised to be stopped on 40 in New Mexico at a checkpoint. As an immigrant, I was glad I had my green card with me (though I had no idea I would be needing it) though I'm sure I could have gotten away with lying about being an American citizen.
There are at least a couple of versions. Including one with a turtle.
http://en.wikipedia.org/wiki/The_Frog_and_the_Mouse
I'd watch that "Expected", that's caught people out before. It's quite possible that high mortality rates encourage high breeding rates. Whilst there's bound to be some inertia, knowing that if you only have three kids, there's a good chance they will be around to support you in your own age and more will more likely be a burden in the immediate term might be enough to restrict growth somewhat.
Yesterday I lost the remote.
That Amiga thingy looked kinda nifty. I never had one myself.
Throwing money at a problem can also make it worse. Particularly where corruption is at play. Congratulations, your food relief just allowed the local warlord to upgrade his automatic weapons.