i have already mentioned the changes. ive mentioned the opcodes used and also the changes such as to the max_script_length went from 520b, 10kb, maxweight
these things are easy for you to find in cores github and things you can search for using google in seconds.. TRY IT
learn how do do research
i know the max script size became unbounded up to the entire blocksize but who is going to really do that though franky? how many times did it actually get done? not many right? you're worrying about a non-event. now if someone came along and filled up block after block with a single transaction that might be a cause for concern but that's not happening. so chill out.
what you should be asking is why did they do that and i don't think the answer is it is just something they overlooked.
i know you want to ignore code. ignore who caused exploits and instead BLINDLY pretend those that caused the exploits are the best authority and no one should independently review, question or scrutinise them.. ok i got it you love centralised authoritarianism with no accountability.. i get it. you are one of those type of idiots..
the bitcoin development process is similar to the linux kernel one. not exactly the same but similar. i don't see an issue with either. they both have developed very successful products which are standing the test of time.
.. but take a chance on yourself. really push yourself out of your blind comfort zone and try to learn something
i did read the part of that BIP and they addressed the unlimited script size explaining why there didn't need to be a hard cap on it. so for you to suggest it was just an oversight on their part, no it's in the BIP. i'm not sure if they realized monkeys might be the end result but i hardly think it was a surprise to them when it happened.
your the type of guy that would next be promoting to close the source code to not be publicly readable because you think the core devs should not be accountable for their code changes so there is no need for public readable code to review/scrutinise them..
i'm a big believer in open source/free software franky. you should know that. but part of that belief means having an attitude of appreciation to the people that wrote the software and maintain it. if i don't like the direction they're going in, i can pay someone to modify it or do it myself if i know how or i can just use something else. but what i can't do is sit there and act like a baby and crying. waiting for someone to come clean things up for me. be an adult franky. fix your own problems. fix bitcoin yourself instead of waiting for someone else to do it for you. if it's that important to you.
you are already close minded about independent review by your admission that you think core devs shouldnt listen to the community..
they should listen to their employer the person that pays their bills. and if they're really nice, waste some time to consider what others have to say like yourself. but don't expect any promises.
but here is a tip
dont waste years being doomads echo chamber. and instead dare yourself to learn, discover, research bitcoin for yourself without being spoonfed empty promises that get broken
if you think being a core dev is easy franky then why don't you try and be one? you could then put in the changes you wanted and fix everything. you yourself said you know how to program so it should be a breeze. you might need to change your username though so they don't figure out what your real motive is...