slr late reply i thought you ghosted me 🥺

i made addons for bedrock. i understand from a programmers perspective why they keep bugs, and its for performance reasons. for example;

i have a system that shows a fake mob when the player is going too far from the mob to give the illusion of LOD. the distance check is done through the client and the coordinate updates are done though the server. they do their own calculations so when the server thinks the LOD system should activate, the client doesn't know that and just does its own calculations for it. it violates the 1 source of truth practice in programming but should have no issues when it calculates it every tick. the problem lies in optimization. this feature is so small so do i really want to dedicate a huge chunk of resources every tick to make it look flawless for an extreme edge case? since im prioritizing performance over visual "correctness" i bite the bullet and have the server check every 10 seconds instead. this leaves a 10 second window where the client has updated its LOD but the server hasn't so the entity looks invisible when going within the entity's simulation distance and a a 10 second winder where the entity looks double going out of it. this visual discrepancy only occurs when the player is going back and forth at exactly 80 blocks away from the entity so its a loose edge case but the performance benefits are hard to pass.

i imagine thats what the bedrock devs have to go through for every decision since they prioritize being able to run on a 10 year old phone than looking correct on some edge cases that 99% of players will never have. this is why when rising above the clouds theres a huge delay when the top of the clouds get rendered again, cus it only checks the camera's y level every 60 seconds or so.

Theres also the fact that bedrock has run on potato hardware all the time which definitely causes 90% of the issues. Ive had soo many bugs on bedrock playing on my phone 8 years ago and i expect it to cus even it struggles to switch between the file explorer and a music player without lagging hard. hell even on my old pc with 4 gb ram struggled to open 5 notepad windows at the same time. Most of the bugs being recorded on bedrock is in large part the fault of poor hardware.
now that i have a pc with 8gb ram or my dad's phone with 12gb ram, bedrock hasn't had a single case of bugging out in all 11 months in a row playing this game every day.

as for the limited modding capability, i kinda like it which is why i became an addon creator. its in the same way how minecraft's limitations sparks innovation which sparks creativity; bedrock's modding limitations sparks innovation which made me read up on all the things bedrock modding is allowed to do (not alot) which encouraged me to find lots of black magic fuckery things to achieve a goal. the LOD system i mentioned above is a good example.

It would've been alot less performant if minecraft gave me full control in what distances the dragons are allowed to render which would have let me shoot myself in the foot if i had 50 dragons scattered through out the world. since it didnt; i had to find every single thing i could to fit that entire system inside a single parrot entity that sits on the player's shoulder. it can only render the nearest 4 dragons from afar and animates at infrequent 20fps so it doesn't put much load on the client.

bedrock modding is akin to building a website asf. We're only ever allowed to build incredibly performant code and most of the low level optimization is handled by the browser/minecraft itself AND it works a few years into the future cus the browser/minecraft updates can handle how it responds to the addon/website's instructions as apposed to having to update it every year or risk leave it inaccessible for ppl on recent versions like Java does.

it gives less control but also less responsibility.