Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror

Comment Re:Speed it up! (Score 2) 11

Where did I say I was expecting similar performance? But Python is slow even for an interpreted language especially given its usually compiled to bytecode first. I would expect similar performance to Java , not run at approx 1/100th the speed of compiled C!

1/100 the speed of compiled languages is typical for interpreted languages.

Non-ancient implementations of Java are fully compiled. Toy benchmarks and Java programs carefully written as if there were no automatic memory management (and don't call standard libraries) can run just as fast ac C code.

Java can't directly support features that depend on dynamic typing and similar flexible run-time behavior that interpreted languages. However, many Java developers sorely miss those features, so they heavily use the reflection APIs and various "beans" frameworks to work around the pre-compilable static typing. This can actually end up running *slower* than Python because many of those Java features are dog slow.

You can already get implementations of Python that do JIT compiling like Java. They often run in the ballpark of about 1/10 the speed of C.

Comment Re:Heh (Score 1) 284

Back in the day, I remember the local Bell main switching center being a very non-descript, completely unmarked mysterious building.

I imagine that also was for security reasons.

Yeah, the enemy would never guess that a large office building completely devoid of windows might possibly be a telephone switch.

Comment Re:Despite (Score 1) 277

It has been a while since I've used Word, but I remember it was really good at propagating tiny changes through a document that made it important that you keep an extra copy around because some seemed to have no easy way back to what you wanted.

This "feature" actually saved me quite a bit of work at a job I had a few years back. The documentation people were so afraid that anyone who was not a full-time Word expert would irrecoverably screw up the corporate branding (IOW, formatting) of their docs, they didn't want developers to directly edit them. So I was often able to get away with emailing a quick text summary to them, and they had to do all the fidgety proof reading, formatting, etc.

I don't know how they managed to get their jobs done, given that they had no real source control and mainly juggled each update amongst themselves over email and random impoossible-to-find folders on Sharepoint.

Since all the docs had the same basic layout and they were mainly trying to make them look consistent with whatever corporate branding was being promulgated that week, it could easily have been done by writing them in "markdown" and having a script that converted them directly to PDF. Or maybe even learn LaTeX. Then the docs could all be maintained and diffed in github like all the other project artifacts. I didn't even bring that up because I knew that their heads would explode.

Slashdot Top Deals

How much net work could a network work, if a network could net work?

Working...