@kirk781@discuss.tchncs.de to Technology@lemmy.worldEnglish • 5 days agoJava at 30: How a language designed for a failed gadget became a global powerhousewww.zdnet.comexternal-linkmessage-square89fedilinkarrow-up1366arrow-down10
arrow-up1366arrow-down1external-linkJava at 30: How a language designed for a failed gadget became a global powerhousewww.zdnet.com@kirk781@discuss.tchncs.de to Technology@lemmy.worldEnglish • 5 days agomessage-square89fedilink
minus-square@atomicbocks@sh.itjust.workslinkfedilinkEnglish4•5 days 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-square@jenesaisquoi@feddit.orglinkfedilinkEnglish2•4 days 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.