My first intro to computing spent about 2 weeks what was affectionately referred to as the knob and switch computer, which was a set of simple virtual machines that were controlled by knobs and switches or a simple pseudo-assembly. It gave an interesting introduction to what computers do behind the scenes prior to actually introducing a programming language. I thought it was clever and there was enough visual feedback during execution that it could hold your attention.
I would have assumed the plants kept their evolutionary advantages against herbivores because there is insufficient pressure to remove the spines on the leaves. Kind of like why we still have an appendix. Its useless, but appendicitis is sufficiently uncommon that there isn't enough evolutionary pressure to do away with it completely.
I think they have a right to feel slighted as I think they have built compelling apps. Tomboy is kind of a toy that I never really found that useful, but I think F-Spot and Banshee are both worthy of being called "Pretty Damn Good." I'd be cranky if people kept trying to beat down something I'd created with the sweat of my brow due to some vague association to Microsoft.
Mars is closer to earth gravity and once had an atmosphere which could conceivably make terraforming easier. Colonizing the moon would mean whoever lives there will always spend their time in giant glass bubbles.
Except for the part where there are numerous public facing documents on the web by microsoft saying that they are legally binding. Thus, if they later try and claim they aren't, I wouldn't think that would fly in court.... obligatory IANAL.
I think op meant not so much as the original distribution but rather the code drop. i.e. microsoft "committed" code into the kernel but aren't actually distributing the program themselves. Thus, microsoft could have inserted some chunk of code they have a patent claim on in order to look like the good guys (releasing stuff under the gpl) but make it so that no one can actually distribute the drivers in question without actually running afoul of the gpl
But at least Google/Microsoft have solutions in place for collaboration and other fun things. Some are even self-hosted if you want to fork over cash. What has OO.o got going for it? A free price tag is about it.
I seem to remember Solaris being able to outperform Linux on certain workloads, but I can't actually remember which ones. Also, I think the current solaris is still ABI compatible with versions released in the early 90s which could be beneficial to some people.
You do realize that connect takes a const char * for its signal and slot parameters right? The C++ macros just hide the stringified names. I guess there wasn't a clever way of doing that in C#.
I/O multiplexing is a technique by which you can examine file handles to determine if a read or write will actually block on that particular call. For instance, does the input buffer for a network socket have enough data that you can read from it without blocking. When dealing with multiple streams you essentially loop and repeatedly check which input sources are ready to read from. The actual structure is very similar to the main-loop in gui applications which must repeatedly check for input from the mouse, keyboard, etc. For POSIX systems, it is generally the select function which allows this behavior.
I would agree it is poorly defined. I recently saw a talk by someone from IBM and he basically said. Cloud Computing is the successor to Grid computing. I think of it in those terms and it works for me.
Really? You've doubled the size of all your pointers and ints in 64-bits. This is not necessarily a good thing and you can theoretically run into performance problems when you run out of cache due to the enlarged data types. It depends on workload. This isn't even theoretical, it is the motivation behind the introduction of the -XX:+UseCompressedOops option for the java vm.
Even moreso, it depends on which desktop environment. I think KDE keeps its autorun scripts under.kde while everyone else keeps them somewhere under.local.
But it vexes me off that we are so focused on CO2. Considering there are a whole plethora of things we are dumping into the ecosystem that have measurable health effects now. Maybe we should be worried about industrial byproducts causing heavy metal toxicity. Mercury in the fish anyone? Thats been a known problem for ages. Industrial run-off causing red tides? While I'm sure dumping billions of tons of CO2 into the atmosphere isn't good in the long term, your argumen doesn't hold weight with me because if we are going to focus on human caused problems there are more immediate concerns than CO2 output.
Yes he does. Microsoft astroturfing... maybe. Destroying Web 2.0... unlikely (especially since its a buzzword anyway and probably should be destroyed).
Could that long term warming trend possibly the one that has been occurring since the last ice age which ended shortly before the dawn of human civilization?
The approach is still that the same objects and methods/interpretations are available to every element in the powershell pipeline because the "interpretation" is inherent to the data being passed. When piping video around, the individual program has to have knowledge of the data type. In powershell, it is conceivable that someone could write an object for a video frame object and suddenly, all elements of the pipeline can perform actions on the video instead of simple those which inherently know how to interpret a byte stream as video data.
Even if all they are doing is the same thing (which I'm not entirely convinced they are), I still think the syntactic niceties of powershell make it more intuitive.
Yes, you are. All curl is doing is writting a stream of bytes to stdout and ffmpeg is reading a stream of bytes from stdin et cetera and so forth. On the other hand. Pretend that I wanted to kill 5 instances of iexplorer that have stopped responding but leave the other 2 alone. I could write something like:
Get-Process iexplorer | Where-Object { !$_.Responding } | Foreach-Object { $_.Kill() }
I'm actually accessing properties/calling methods on objects that are flowing through the pipeline. And I think that is cool. Obviously, sometimes you get strings that are flowing through the pipeline, but you can even call methods on those to perform formatting.
Well, I guess the only reason to not compile with ICC is that "0h N0es! iNtel is t3h unfr33!" because every piece of literature I'v ever read suggests ICC produces slightly larger binaries which are greatly faster when compared to GCCs output. In fact, for this reason I seem to remember a whole bunch of guides from the olden days on Gentoo for how to install ICC.
And thus, the lesson we have learned is that when you have the engineers who designed the architecture on hand, you can write a kickass compiler.
Actually, there is a difference, Powershell pipes serialized objects and you can call methods on the output of powershell commands. bash and co. are just pushing characters.
Slashdot Mirror
You can get cut by that little dandy anywhere unless you control the whole platform top to bottom.
My first intro to computing spent about 2 weeks what was affectionately referred to as the knob and switch computer, which was a set of simple virtual machines that were controlled by knobs and switches or a simple pseudo-assembly. It gave an interesting introduction to what computers do behind the scenes prior to actually introducing a programming language. I thought it was clever and there was enough visual feedback during execution that it could hold your attention.
I would have assumed the plants kept their evolutionary advantages against herbivores because there is insufficient pressure to remove the spines on the leaves. Kind of like why we still have an appendix. Its useless, but appendicitis is sufficiently uncommon that there isn't enough evolutionary pressure to do away with it completely.
I think they have a right to feel slighted as I think they have built compelling apps. Tomboy is kind of a toy that I never really found that useful, but I think F-Spot and Banshee are both worthy of being called "Pretty Damn Good." I'd be cranky if people kept trying to beat down something I'd created with the sweat of my brow due to some vague association to Microsoft.
Your soul is mine!
Mars is closer to earth gravity and once had an atmosphere which could conceivably make terraforming easier. Colonizing the moon would mean whoever lives there will always spend their time in giant glass bubbles.
I also think the bad ones are the ones that have a tendency to go into politics.
Except for the part where there are numerous public facing documents on the web by microsoft saying that they are legally binding. Thus, if they later try and claim they aren't, I wouldn't think that would fly in court. ... obligatory IANAL.
I think op meant not so much as the original distribution but rather the code drop. i.e. microsoft "committed" code into the kernel but aren't actually distributing the program themselves. Thus, microsoft could have inserted some chunk of code they have a patent claim on in order to look like the good guys (releasing stuff under the gpl) but make it so that no one can actually distribute the drivers in question without actually running afoul of the gpl
But at least Google/Microsoft have solutions in place for collaboration and other fun things. Some are even self-hosted if you want to fork over cash. What has OO.o got going for it? A free price tag is about it.
I seem to remember Solaris being able to outperform Linux on certain workloads, but I can't actually remember which ones. Also, I think the current solaris is still ABI compatible with versions released in the early 90s which could be beneficial to some people.
That may definitely be a disadvantage, but the fact remains that P/Invoke is so much better than JNI that it's not even funny.
You do realize that connect takes a const char * for its signal and slot parameters right? The C++ macros just hide the stringified names. I guess there wasn't a clever way of doing that in C#.
I/O multiplexing is a technique by which you can examine file handles to determine if a read or write will actually block on that particular call. For instance, does the input buffer for a network socket have enough data that you can read from it without blocking. When dealing with multiple streams you essentially loop and repeatedly check which input sources are ready to read from. The actual structure is very similar to the main-loop in gui applications which must repeatedly check for input from the mouse, keyboard, etc. For POSIX systems, it is generally the select function which allows this behavior.
I would agree it is poorly defined. I recently saw a talk by someone from IBM and he basically said. Cloud Computing is the successor to Grid computing. I think of it in those terms and it works for me.
In Vista, you would only select the root folder and then when you change permission select the "And all subfolders..." option.
Really? You've doubled the size of all your pointers and ints in 64-bits. This is not necessarily a good thing and you can theoretically run into performance problems when you run out of cache due to the enlarged data types. It depends on workload. This isn't even theoretical, it is the motivation behind the introduction of the -XX:+UseCompressedOops option for the java vm.
Even moreso, it depends on which desktop environment. I think KDE keeps its autorun scripts under .kde while everyone else keeps them somewhere under .local.
But it vexes me off that we are so focused on CO2. Considering there are a whole plethora of things we are dumping into the ecosystem that have measurable health effects now. Maybe we should be worried about industrial byproducts causing heavy metal toxicity. Mercury in the fish anyone? Thats been a known problem for ages. Industrial run-off causing red tides? While I'm sure dumping billions of tons of CO2 into the atmosphere isn't good in the long term, your argumen doesn't hold weight with me because if we are going to focus on human caused problems there are more immediate concerns than CO2 output.
Yes he does. Microsoft astroturfing... maybe. Destroying Web 2.0... unlikely (especially since its a buzzword anyway and probably should be destroyed).
Could that long term warming trend possibly the one that has been occurring since the last ice age which ended shortly before the dawn of human civilization?
The approach is still that the same objects and methods/interpretations are available to every element in the powershell pipeline because the "interpretation" is inherent to the data being passed. When piping video around, the individual program has to have knowledge of the data type. In powershell, it is conceivable that someone could write an object for a video frame object and suddenly, all elements of the pipeline can perform actions on the video instead of simple those which inherently know how to interpret a byte stream as video data.
Even if all they are doing is the same thing (which I'm not entirely convinced they are), I still think the syntactic niceties of powershell make it more intuitive.
Yes, you are. All curl is doing is writting a stream of bytes to stdout and ffmpeg is reading a stream of bytes from stdin et cetera and so forth. On the other hand. Pretend that I wanted to kill 5 instances of iexplorer that have stopped responding but leave the other 2 alone. I could write something like:
Get-Process iexplorer | Where-Object { !$_.Responding } | Foreach-Object { $_.Kill() }
I'm actually accessing properties/calling methods on objects that are flowing through the pipeline. And I think that is cool. Obviously, sometimes you get strings that are flowing through the pipeline, but you can even call methods on those to perform formatting.
Well, I guess the only reason to not compile with ICC is that "0h N0es! iNtel is t3h unfr33!" because every piece of literature I'v ever read suggests ICC produces slightly larger binaries which are greatly faster when compared to GCCs output. In fact, for this reason I seem to remember a whole bunch of guides from the olden days on Gentoo for how to install ICC.
And thus, the lesson we have learned is that when you have the engineers who designed the architecture on hand, you can write a kickass compiler.
Actually, there is a difference, Powershell pipes serialized objects and you can call methods on the output of powershell commands. bash and co. are just pushing characters.