I know for a fact (and I have the email correspondence with Intel engineers to prove it) that it's been ready for at least two years!! I'm still f*cking waiting, guys.
I have major projects in the pipeline that could be Linux/x86 projects if this library was available NOW. C'mon Intel, get off your g*dd*amn ass and RELEASE the Linux version of this damn thing!!! These projects could just as easily be PPC based. At least I can get optimized signal processing libraries for PPC processors.
All we do here is embeded systems. I'm feeling a lot of pressure to stay the course and stick with VxWorks, rather than make the switch to Linux (this, despite the fact that WRS gets you coming and going with maintenance contracts and run-time royalties).
Continued efforts to optimize Linux for the server space isn't going to help my cause very much.
My understanding is that Intel does have these libraries ready to go for Linux (and have for at least a year), but for some reason, refuse to release them.
Well I'm also sort of leary about any Perl article that goes into talking about "Schwartzian Transformers". Say what?!
Aw, c'mon. Schwartzian Transforms have been around for as long as Perl 5 has been.
my @output =
map { $_->[0] }
sort { $a->[1] cmp $b->[1] }
map { [$_, expensive_func($_)] }
@input;
A sort between two maps. Doesn't get much simpler than that.
At the risk of showing my ignorance, (and I haven't looked real hard, either), does XML (and by extenstion SOAP/XML-RPC) have any support for shipping binary data?
Since we're in the remote sensing business, we regularly build systems that ship around a lot (as in GB) of binary data. Obviously, conserving bandwidth in our comms streams is very important.
My take on XML is that it's all text. That's probably a good thing, but converting a single I/Q data point (2 - four-byte floats == 8 bytes) into ASCII (say 12 characters each for I and Q == 24 bytes) for inclusion in an XML message is, to say the least, a waste of bandwidth. Especially, when we need to ship tens of thousands of data points per second over a comm link that may be much slower than even 10-base ethernet.
Otherwise, XML would serve us very well. If there were some way to ship binary data in XML, then SOAP/XML-RPC might prove ideal for our purposes.
If there is a way inclucde binary data in XML, then **please** send me or post a pointer.
Otherwise, we'll probably continue to use straight CORBA.
While Derek Burney didn't have a whole lot to say of substance to CNBC's Bill Griffeth, he did have the following nugget when it came to Linux, Microsoft, and.NET:
"As we looked at moving our applications to the Web, it became clear that.NET is the way to go. By incorpoating.NET servicves into our own applications, including Linux, we can strengthen them."
Slashdot Mirror
But when the HELL is Intel going to release their signal processing library for Linux?
I know for a fact (and I have the email correspondence with Intel engineers to prove it) that it's been ready for at least two years!! I'm still f*cking waiting, guys.
I have major projects in the pipeline that could be Linux/x86 projects if this library was available NOW. C'mon Intel, get off your g*dd*amn ass and RELEASE the Linux version of this damn thing!!! These projects could just as easily be PPC based. At least I can get optimized signal processing libraries for PPC processors.
All we do here is embeded systems. I'm feeling a lot of pressure to stay the course and stick with VxWorks, rather than make the switch to Linux (this, despite the fact that WRS gets you coming and going with maintenance contracts and run-time royalties).
Continued efforts to optimize Linux for the server space isn't going to help my cause very much.
No suprise that Micro-Soft was so very vocal about putting an end to Information Anarchy.
They must have seen this one coming....
I could stand to use Intel's Signal Processing Library on Linux right now.
My understanding is that Intel does have these libraries ready to go for Linux (and have for at least a year), but for some reason, refuse to release them.
Anyone have any clues about this?
I consider its use as a programming lanugage the mark of a rank amateur.
Don't believe me? Try this.
I'd get a different provider. My current one has no problems with my hiding dozens of machines behind a single IP address. I checked our TOS.
If they suddenly started to raise a fuss about it, I'd ask them for the phone number of their nearest competiter.
OO perl that doesn't depend on my client coders being able to read my source to be sure they don't trample over my member objects?
Use closures. Run perldoc perltoot , and then read the section Closures as Objects
Well I'm also sort of leary about any Perl article that goes into talking about "Schwartzian Transformers". Say what?!
Aw, c'mon. Schwartzian Transforms have been around for as long as Perl 5 has been.
my @output =
map { $_->[0] }
sort { $a->[1] cmp $b->[1] }
map { [$_, expensive_func($_)] }
@input;
A sort between two maps. Doesn't get much simpler than that.
Who is Scott Nudds?
Gotta love assembly!! Makes you wonder why we ever bothered inventing higher level languages....
compress your XML doc with zip or the like
Yeah, we considered that, but then we'd be wasting CPU cycles (and time) compressing and uncompressing data.
Guess we'll stick to CORBA. All this nifty IT gunk is useless for our purposes.
At the risk of showing my ignorance, (and I haven't looked real hard, either), does XML (and by extenstion SOAP/XML-RPC) have any support for shipping binary data?
Since we're in the remote sensing business, we regularly build systems that ship around a lot (as in GB) of binary data. Obviously, conserving bandwidth in our comms streams is very important.
My take on XML is that it's all text. That's probably a good thing, but converting a single I/Q data point (2 - four-byte floats == 8 bytes) into ASCII (say 12 characters each for I and Q == 24 bytes) for inclusion in an XML message is, to say the least, a waste of bandwidth. Especially, when we need to ship tens of thousands of data points per second over a comm link that may be much slower than even 10-base ethernet.
Otherwise, XML would serve us very well. If there were some way to ship binary data in XML, then SOAP/XML-RPC might prove ideal for our purposes.
If there is a way inclucde binary data in XML, then **please** send me or post a pointer.
Otherwise, we'll probably continue to use straight CORBA.
Perl?
Ruby?
Python?
Haskell?
E-Lisp? :-)
What else can be said? Simply stunning.
While Derek Burney didn't have a whole lot to say of substance to CNBC's Bill Griffeth, he did have the following nugget when it came to Linux, Microsoft, and .NET:
"As we looked at moving our applications to the Web, it became clear that .NET is the way to go. By incorpoating .NET servicves into our own applications, including Linux, we can strengthen them."
Yes it is.
http://www.perl.com/pub/n/Perl_5.6.0_is_ out!
The link is right there in the "What's new?" section of the www.perl.com home page.