kirk781@discuss.tchncs.de to Technology@lemmy.worldEnglish · 2 months agoJava at 30: How a language designed for a failed gadget became a global powerhousewww.zdnet.comexternal-linkmessage-square124fedilinkarrow-up1373arrow-down115cross-posted to: [email protected]
arrow-up1358arrow-down1external-linkJava at 30: How a language designed for a failed gadget became a global powerhousewww.zdnet.comkirk781@discuss.tchncs.de to Technology@lemmy.worldEnglish · 2 months agomessage-square124fedilinkcross-posted to: [email protected]
minus-squareatomicbocks@sh.itjust.workslinkfedilinkEnglisharrow-up4·2 months agoPython is interpreted where Java is compiled. They aren’t going to be able to be used in the same cases all the time.
minus-squarejenesaisquoi@feddit.orglinkfedilinkEnglisharrow-up2arrow-down2·2 months agoNot true. They use the same model, executing compiled bytecode. It just feels like directly running a script because Python compiles it to bytecode on the fly, and because it is embarrassingly slow.
Python is interpreted where Java is compiled. They aren’t going to be able to be used in the same cases all the time.
Not true. They use the same model, executing compiled bytecode. It just feels like directly running a script because Python compiles it to bytecode on the fly, and because it is embarrassingly slow.