Being part of PSTN may not be any more privat than being part of internet. An T1 is like an VPN.
A black fiber is "fully-private" until someone hook an sniffer on it.
On PSTN you switch ATM-cells, on internet you switch IP-packets, same-same...
HP openview is a framework, so is tivoli. Those two have functions far beyond opennms and shouldn't be compared.
Compare opennms functionallity with HP Openview NNM and IBM Tivoli Netview.
Btw, Netview and HPOV NNM is almost same product when ibm bought an old license and forked.
Though if they could somehow manipulate the dna to create brainless bodies, those could be used as warming bags. You would put a few of them here and there in your home to heat it up. They would be connected to a food and waste facility. And with an intact immune-system and other body functions they would be maintainance free.
Homo Sapiens is a true parasitic specie.
Unlike other species it totally lacks the ability to adapt and interact with the environment in a durable way.
Maybe it is time for us to step down and let evolution rectify this mistake.
Actually, threads is something perl has got right, compared to most other languages. Perl threads is also very easy to understand. Simply put, nothing is shared between threads. If you want to share data between perl threads you must explicitly say so: my $foo : shared = 1;
though if you're stuck with perl version 5.6.0, dont use threads.
Erlang already support multiple cores, it used to be that you had to start an erlang node
for every core/cpu. Today a single erlang os-process will scale to the cores available.
But from the programming point of view, erlang has supported multiple cores for as long as it has existed.
In erlang when you send a message to another process, you don't know if that other process is executing within the same OS-process or is executing in another OS-process, or even running on an distant machine. That is very good, because you don't have to rewrite anything to support distribution.
Concurrency is one of many features where erlang makes things easier for you.
On the other hand.. if you look at java or perl, those green processes or real threads (pthread) is just slapped on, like any other library. The language doesn't have any support for processes/threads nor is it oriented around processes/threads. This doesn't exclude
you from doing erlang like stuff. It is just that an 10 line erlang-hello will expand
to an 100 line pthread beast with sharp mutexes slashing around.
I've played with "mplayer -v -vo null -ao null udp://224.1.2.3" as a frontend for analyzation of live streams. Pipe the stuff to a script. Put it in an loop so it restarts if mplayer dies. Its coarse, but it works.
Slashdot Mirror
Being part of PSTN may not be any more privat than being part of internet. An T1 is like an VPN. A black fiber is "fully-private" until someone hook an sniffer on it. On PSTN you switch ATM-cells, on internet you switch IP-packets, same-same...
> 3. Can I obfuscate my code (e.g. encode it)?
use perl.
Welcome to psdoom !
/dev/null beats them all in time and space.
HP openview is a framework, so is tivoli. Those two have functions far beyond opennms and shouldn't be compared.
Compare opennms functionallity with HP Openview NNM and IBM Tivoli Netview.
Btw, Netview and HPOV NNM is almost same product when ibm bought an old license and forked.
more of this..
How is the wetware-diy scene doing ?
The muscle has a efficiency far below 30%.
Though if they could somehow manipulate the dna to create brainless bodies, those could be used as warming bags. You would put a few of them here and there in your home to heat it up. They would be connected to a food and waste facility. And with an intact immune-system and other body functions they would be maintainance free.
To an scientist everything is an object with properties.
that is Safe Computing For the Elderly.
v java-compiler
p java-compiler-sun
p java-compiler-gcc
p java-compiler-kaffe
Homo Sapiens is a true parasitic specie.
Unlike other species it totally lacks the ability to adapt and interact with the environment in a durable way.
Maybe it is time for us to step down and let evolution rectify this mistake.
with duke nukem where you would often find testosterone ampuls..
Actually, threads is something perl has got right, compared to most other languages.
Perl threads is also very easy to understand.
Simply put, nothing is shared between threads.
If you want to share data between perl threads you must explicitly say so:
my $foo : shared = 1;
though if you're stuck with perl version 5.6.0, dont use threads.
Was dice first game. Those were the days, small studio, great games.
GNU should be the happiest.
Erlang already support multiple cores, it used to be that you had to start an erlang node for every core/cpu. Today a single erlang os-process will scale to the cores available.
s .html
/ part_frame.html
But from the programming point of view, erlang has supported multiple cores for as long as it has existed.
In erlang when you send a message to another process, you don't know if that other process is executing within the same OS-process or is executing in another OS-process, or even running on an distant machine. That is very good, because you don't have to rewrite anything to support distribution.
Concurrency is one of many features where erlang makes things easier for you.
On the other hand.. if you look at java or perl, those green processes or real threads (pthread) is just slapped on, like any other library. The language doesn't have any support for processes/threads nor is it oriented around processes/threads. This doesn't exclude you from doing erlang like stuff. It is just that an 10 line erlang-hello will expand to an 100 line pthread beast with sharp mutexes slashing around.
References:
New smp feature in erlang:
http://www.erlang.org/doc/doc-5.5.1/doc/highlight
Look at chapter 3, you don't have to understand erlang to follow:
http://erlang.org/doc/doc-5.5/doc/getting_started
or find out what smalltalk or even prolog is really about...
$a = sub { "yes"; }; print &$a;
I rather program in an modern language that has invented closures and anonymous functions, like perl.
has definitely taken over Slashdot As We Know It.
my native wrist watch tells me its time for lunch.
thats because you receive 90V that is powering the bell.
thats what i'm going to call long island ice tea from now on.
I've played with "mplayer -v -vo null -ao null udp://224.1.2.3" as a frontend for analyzation of live streams. Pipe the stuff to a script. Put it in an loop so it restarts if mplayer dies. Its coarse, but it works.
Building windows ontop of command, from windows 3.11 to todays windows XP has finally payed off!