Jython and IronPython run on platforms where strings are unicode capable by default. Both implementations have chosen to make str essentially an alias for unicode in Python source code. The bytes type, introduced in PEP358 as part of transition to fully unicode Python 3.0, is unambiguously a sequence of single byte values. We can see [...]
Read the rest of this entry »
Earlier today I posted the second article in what is turning out to be a short series in the investigation into why the performance of IronPython is around 100× slower than CPython, when running the front-end of my OWL BASIC compiler.
The most informative comment was from Curt Hagenlocher who works on IronPython in the Visual [...]
Read the rest of this entry »
IronPython 2.0 can be hundreds of times slower than CPython on some microbenchmarks. Jython 2.5 can scale better than CPython on those same benchmarks.
Read the rest of this entry »
IronPython can be slow – 10x to 100x slower than CPython on real-world code and it has been observed to be up to 6000x slower.
Read the rest of this entry »
…higher-order techniques can be used to aid user-interface programming with Swing…
Read the rest of this entry »
… why do programmers continue to subject themselved to working in C++ … ?
Read the rest of this entry »
Recent Comments