This is what really annoys me about the Ethereum VM, there was no need for turing completeness. Bitcoin has a perfectly good scripting system that they keep adding opcodes to, and is not vulnerable to some of these kind of attacks.
It's a giant pain in the ass to code Bitcoin. In a few years, all of these kinds of attacks will have been tried against various Ethereum contracts and it will be hardened and still easy. It will still be very cumbersome to code Bitcoin.
Could you point me to some resources showing recently added opcodes?
Last time I looked at the Bitcoin code they had actually disabled some of the original opcodes due to security concerns. I'd be interested to see that this trend had reversed.
Sorry, I should probably edit my comment to say "over the years" and not necessarily recently.
I think my point was more that the conservative approach Bitcoin takes works better on the long term, and there's still proposals that slowly get implemented.
I first got into Bitcoin in 2011, and since then there's been plenty of new opcodes, and as you say some original ones that got disabled as they presented risks.
Latest one I can think of that got implemented would be OP_CHECKLOCKTIMEVERIFY in 2014/15 (?), but I haven't really kept up with the BIPs that much with all the infighting
