The Python 'long' type is not a machine type such as a 32 or 64 or perhaps even 128 bit integer/long. It is an arbitrary precision decimal type! That's why Python's scores on the Long test are so much higher (slower) than the other languages. I wonder what Java scores when the benchmark is reimplemented using BigDecimal instead of the 'long' machine type. Python uses a highly efficient Karatsuba multiplication algorithm for its longs (although that only starts to kick in with very big numbers).
VMWare grabs CTRL-ALT-DEL... It pops up a dialog saying that you have to type ctrl-alt-backspace (or whatever it is) to send a CTRL-ALT-DEL to the simulated machine.
Once you installed Executive (http://www.megabaud.fi/~petrin/Executive2.html), which is a replacement for the standard Amiga OS task scheduler, you had terrific multitasking on your Amiga. Executive had a dynamic priority scheduler which boosted interactive apps (that got the focus) and that pushed cpu-hogging apps to lower priorities the longer they were running.
You could choose from a multitude of different scheduling mechanisms, dynamically. And you got a whole bunch of system information tools as a bonus.
Ehm sorry but if you can't get Java to work at all, should you even be trying to build a J2EE application? Getting Java to work is the easy part. The real issues come much later, for instance, trying to figure out why your J2EE app works on one app server and doesn't on another.
Slashdot Mirror
The Python 'long' type is not a machine type such as a 32 or 64 or perhaps even 128 bit integer/long.
It is an arbitrary precision decimal type! That's why Python's scores on the Long test are so much higher (slower) than the other languages.
I wonder what Java scores when the benchmark is reimplemented using BigDecimal instead of the 'long' machine type.
Python uses a highly efficient Karatsuba multiplication algorithm for its longs (although that only starts to kick in with very big numbers).
VMWare grabs CTRL-ALT-DEL...
It pops up a dialog saying that you have to type ctrl-alt-backspace (or whatever it is) to send a CTRL-ALT-DEL to the simulated machine.
Once you installed Executive (http://www.megabaud.fi/~petrin/Executive2.html), which is a replacement for the standard Amiga OS task scheduler, you had terrific multitasking on your Amiga. Executive had a dynamic priority scheduler which boosted interactive apps (that got the focus) and that pushed cpu-hogging apps to lower priorities the longer they were running.
You could choose from a multitude of different scheduling mechanisms, dynamically. And you got a whole bunch of system information tools as a bonus.
Let's stick to Python:
"method cascading":
>>> 'HELLO THERE'.capitalize().swapcase()
'hELLO THERE'
iterators:
mylist=['foo','bar','car']
for item in mylist:
# do something with item
But it starts getting interesting when you start using the 'yield' statement (generators)...
Sure thing. Amazingly powerful and stable, and the search/replace in files is worth the registration fee alone.
Ehm sorry but if you can't get Java to work at all, should you even be trying to build a J2EE application? Getting Java to work is the easy part. The real issues come much later, for instance, trying to figure out why your J2EE app works on one app server and doesn't on another.
Suppose the iceberg houses pinguin colonies or other wildlife? What happens with them. Are they aware they're afloat? Can they reach main land again?
Still not quite right.
A500 OCS had max 32 colors (out of 16 million) + 32 additional 'half bright' colors. 4096 in HAM mode.
ECS changed nothing. AGA gave max 256 out of 16 million, and 250,000+ in HAM8 mode.
Of course, you could use the copper chip to change base pallette each scan line and get thousands more on screen without any cpu load.