News for hackers. Stuff that matters.

A comment on Introducing PyScript (summary of PyCon keynote). Parent comment

Re:Introducing PyScript (summary of PyCon keynote) by beebmam on Thursday June 23, 2022 @02:36AM (#31845833)
In C, this loop would get unrolled to a no-op in a release environment. Source: https://godbolt.org/z/1sb5Tb3xv
[ Parent | on HN ]
Re:Introducing PyScript (summary of PyCon keynote) by codedokode on Thursday June 23, 2022 @02:50AM (#31845915)
I used an empty loop just to simplify an example. Obviousy in real code the loop would do domething useful and wouldn't be optimized out.
[ Parent | on HN ]
Re:Introducing PyScript (summary of PyCon keynote) by colejohnson66 on Thursday June 23, 2022 @08:14AM (#31847957)
But if your loop is busy doing stuff that’s hundreds of bytecode ops long, is worrying about the few extra bytecode ops that a for loop takes worth it?
[ Parent | on HN ]
Re:Introducing PyScript (summary of PyCon keynote) by joaommartins on Thursday June 23, 2022 @06:12PM (#31855746)
How else would they feel superior to someone else, if not by comparing Python/JS to C's speed all the while talking about applications where C is never going to be used?
[ Parent | on HN ]
Re:Introducing PyScript (summary of PyCon keynote) by the-smug-one on Thursday June 23, 2022 @11:11AM (#31850205)
It's not like those hundreds of bytecode ops aren't slow as molasses too, for similar reasons.
[ Parent | on HN ]