Hi -- I'm the Chief Architect of the DMF. The problem that we find with Java is the same one encountered by everyone using client-side Java: Write Once, Debug Everywhere. Flash works identically on every platform, and the files are significantly smaller.
Of course, since it's using XML-RPC under the hood, we don't care what language sits at the other end. I did all my testing using Python's xmlrpclib, and xmlrpc.com lists client implementations in just about every language that's widely used (except COBOL and FORTRAN...)
You want to talk to a device running our DMF from a Java (or C++, or LISP) client, that's cool. Dave Winer could control his router from inside Radio Userland. Whatever.
The important thing (to me, as a designer) is that we've implemented a clean, open, simple protocol that lets us and our customers build richer monitor and control interfaces than we can using just HTML.
As an audiophile, I find that statement to be absolutely revolting. It's impossible to get natural sounding music out of a file of such low bitrate. 128 kbps is tough. 192 is getting close to being acceptable. ...and remember that due to the design of the Layer-3 format, throwing more bits at the problem does not give additional fidelity -- at 128 KB/sec, Layer 3 sounds better than Layer 2, but at 256 or 384 KB/s, Layer 2 is significantly better than Layer3. Layer 2 at 384 is perceptually identical to an original linear PCM source.
Also, perceptual encoding doesn't really strip away everything that's not audible -- there's plenty of room under the masking curve to hide things that will be encoded but never heard by humans. I'm not sure how robust any technique based on this idea would be in the face of transcoding through different algorithms, etc., though.
I've been working from home since June of 97 (www.artlogic.com). It was an odd adjustment. If I didn't have a family or other support network in place, I wouldn't have been able to turn work off, so that would be bad. I've also been successful in training my family that when the office door is closed, they need to call on the office line if they need me -- they have to pretend that my office isn't really there in the house.
Another important factor is the culture of the company you're working with -- our office is strictly administrative, and all the programmers telecommute, so there's no penalty. I've heard tales of serious problems where you're the only telecommuter -- being treated as an outsider, ignored, etc. Even more important in this case is choosing a company that has an IT infrastructure that's telecommuting-aware. If you can't get to source code control, etc. from the outside, it's pretty useless.
According to the thread on this topic on c.l.python, python treats all tabs as 8 spaces. Use the '-tt' command line option to give a warning that tabs & spaces are used inconsistently.
People who are not willing to take the heat for their opinions probably don't have opinions worth hearing. No, no, no. There's a difference between 'taking the heat' and putting up with puerile abuse from script kiddies, isn't there?
Skinwalker sez: "I dispute your claim that pornography is a "relatively new concept in human history". "
I think you missed his meaning -- he meant 'pornography' as a pejorative, legal term, not in the sense of just being sexually explicit. The cultures that produced these artifacts didn't interpret or experience them as 'pornography' in that sense.
Slashdot Mirror
Hi --
I'm the Chief Architect of the DMF. The problem that we find with Java is the same one encountered by everyone using client-side Java: Write Once, Debug Everywhere. Flash works identically on every platform, and the files are significantly smaller.
Of course, since it's using XML-RPC under the hood, we don't care what language sits at the other end. I did all my testing using Python's xmlrpclib, and xmlrpc.com lists client implementations in just about every language that's widely used (except COBOL and FORTRAN...)
You want to talk to a device running our DMF from a Java (or C++, or LISP) client, that's cool. Dave Winer could control his router from inside Radio Userland. Whatever.
The important thing (to me, as a designer) is that we've implemented a clean, open, simple protocol that lets us and our customers build richer monitor and control interfaces than we can using just HTML.
Guido has already said that the preferred Python icon should be the 16-ton weight.
As an audiophile, I find that statement to be absolutely revolting. It's impossible to get natural sounding music out of a file of such low bitrate. 128 kbps is tough. 192 is getting close to being acceptable.
...and remember that due to the design of the Layer-3 format, throwing more bits at the problem does not give additional fidelity -- at 128 KB/sec, Layer 3 sounds better than Layer 2, but at 256 or 384 KB/s, Layer 2 is significantly better than Layer3. Layer 2 at 384 is perceptually identical to an original linear PCM source.
Also, perceptual encoding doesn't really strip away everything that's not audible -- there's plenty of room under the masking curve to hide things that will be encoded but never heard by humans. I'm not sure how robust any technique based on this idea would be in the face of transcoding through different algorithms, etc., though.
I've been working from home since June of 97 (www.artlogic.com). It was an odd adjustment. If I didn't have a family or other support network in place, I wouldn't have been able to turn work off, so that would be bad. I've also been successful in training my family that when the office door is closed, they need to call on the office line if they need me -- they have to pretend that my office isn't really there in the house.
Another important factor is the culture of the company you're working with -- our office is strictly administrative, and all the programmers telecommute, so there's no penalty. I've heard tales of serious problems where you're the only telecommuter -- being treated as an outsider, ignored, etc.
Even more important in this case is choosing a company that has an IT infrastructure that's telecommuting-aware. If you can't get to source code control, etc. from the outside, it's pretty useless.
I disagree.
The intent is fused with the actual performance.
How can you suggest that having two channels that can be desynchronized is a good thing?
There the indentation is rather misleading, in a non-obvious way. (The else gets grouped with the inner if, not the outer)
Ahhh, but in Python, it behaves exactly as you'd expect it to -- the else is in fact grouped with the outer if!
case1 = 0
case2 = 0
if case1:
if case2:
print("case 2")
else:
print("Neither 1 nor 2")
prints 'Neither 1 nor 2'
if you change the value of case1 to 1, nothing is printed.
This is why indentation in Python is valuable, once you get past your old C/C++ habits.
According to the thread on this topic on c.l.python, python treats all tabs as 8 spaces. Use the '-tt' command line option to give a warning that tabs & spaces are used inconsistently.
And yes, mixing tabs and spaces is evil.
People who are not willing to take the heat for their opinions probably don't have opinions worth hearing.
No, no, no.
There's a difference between 'taking the heat' and putting up with puerile abuse from script kiddies, isn't there?
...but 'fucker.com' has been issued:
Go, go, Chank Diesel!
Registrant:
CAKE Publications, Inc. (FUCKER-DOM)
2401 University Ave. NE
Minneapolis, MN 55418
US
Domain Name: FUCKER.COM
Administrative Contact:
Anderson, Charles (CA189) chank@FUCKER.COM
(612)781-9178 (FAX) +90 0232 331 31 31
Technical Contact, Zone Contact:
Koppelman, Michael (MK138) lolife@BITSTREAM.NET
(612)321-9290 (FAX) (612)321-9100
Billing Contact:
Anderson, Charles (CA189) chank@FUCKER.COM
(612)781-9178 (FAX) +90 0232 331 31 31
Record last updated on 28-Jul-1999.
Record created on 11-Sep-1995.
Database last updated on 9-Jan-2000 12:57:51 EST.
Domain servers in listed order:
NS.BITSTREAM.NET 204.73.77.77
NS.MR.NET 137.192.240.5
Skinwalker sez: "I dispute your claim that pornography is a "relatively new concept in human history". "
I think you missed his meaning -- he meant 'pornography' as a pejorative, legal term, not in the sense of just being sexually explicit. The cultures that produced these artifacts didn't interpret or experience them as 'pornography' in that sense.