-Fan content is easier to get access to, no marketplace to speak of
-Old versions are completely accessible from Mojang's server to download and play whenever you want and mod if you know how to mod old versions.
-May not run as well as Bedrock but with performance mods (OptiFine, Sodium) or the right tweaking of the game (using Java arguments or other means) you can get it to run well instead of the bad job Mojang has made the game version to version, then fixing it and breaking it however many times Modders can point out.
-Command system is better. The OP system while not as UI accessible as Bedrock before launching the world, isn't in your way and it's in commands instead. That and commands don't prefer achievements.
-Redstone, don't need to say more those that know, know.
-As weird as it is I like the creative mode flight drift, Bedrock doesn't have it (whether for nausea or not which is a fair reason to not have it so a mod is required in Java to prevent it). It also goes for the swimming controls to since 1.13 I don't like it in Bedrock and it's like the auto-step feature in Vanilla compared to mods it just doesn't work very well.
-Multiplayer can be alright. Though people can go with Realms if they want but otherwise if you don't know how to set up a server for yourself then good luck. But depending on that of course it will be a fine or rough time. I did a few modded server playthroughs to test datapacks, record a modded server play as recent examples but I'm not a multiplayer person really or ever tried minigame/PVP person so can't say for those experiences.
-Seed sharing is more clear on Java I find than Bedrock other than version to deal with it may or may not work while with Bedrock no older version access means that seeds may not work but otherwise it may or may not be down to whatever console/Windows 10/Pocket Edition version of the game possibly. In more so a case for legacy edition
Bedrock:
-Marketplace for fan content is easiest way but fan content exists on MCPEDL.com for example which is where I get Behaviourpacks as you can't get them on the marketplace and of course other content exists there too that like Curseforge and the Java method is 'free' and 'open to anyone no storefront' even if yes the creators do get a cut on the marketplace and that MCPEDL can be awkward like the Forum days of adfly and so on annoying it's still something.
-Can't use old version only moving forward as the option unless you don't connect to the Internet I guess.
-Performance is better than Java Vanilla.
-Controller support without a need for a behaviourpack
-Redstone isn't as great due to the bugs used in Java not being present besides the C++ or C# and Java differences in coding language too.
-I don't like the lack of creative mode drift or the swimming in Bedrock.
-I assume multiplayer may be better and of course crossplay is a thing with all versions of Bedrock. I have only used the Legacy Console versions for multiplayer whether split-screen on Xbox 360/One versions of the game or invites for the Diamonds To You trophy on my Vita (where there is no split-screen of course).
Those are what comes to mind.
Bedrock has it's place but I can make Java my playground Bedrock not so much.
Rollback Post to RevisionRollBack
Niche Community Content Finder, Youtuber, Modpack/Map Maker, Duck
Forum Thread Maintainer for APortingCore, Liteloader Download HUB, Asphodel Meadows, Fabric Project, Legacy Fabric/Cursed Fabric, Power API, Rift/Fabric/Forge 1.13 to 1.17.
What are the actual gameplay differences though? My understanding is that farming is very different, especially with mobs, there's obviously the sweep function that is missing for swords, but what others exist that are pretty defining?
-Redstone isn't as great due to the bugs used in Java not being present besides the C++ or C# and Java differences in coding language too.
None of the differences in editions have anything to do with Java being unable to do what C++ can do or vice-versa; it is all down to the development teams deciding how to implement things, for one reason or another (for example, for whatever reason diamond ore is about twice as common on Bedrock (Java = 6 veins of 0-5 + 1/9 chance of a vein of 0-23; Bedrock = 7 veins of 0-5 + 1/9 chance of a vein of 0-23 + 4 veins of 0-10), especially in light of the efforts for "feature parity". Likewise, they have refused to fix bugs on Bedrock that were fixed on Java, like fossils overwriting end portal frames (compare to the report for Java Edition); their claim of "can't be done because it will break world generation" is literally the weakest excuse possible - just do what I did and check that the block being replaced is not an end portal (frame) block. Similarly, MCPE-19426 can easily be fixed by porting over the simple loop that Java uses to ensure an end portal has been placed - C++ supports loops as does virtually every programming language so I have no idea why they haven't done this, even closing the report as "works as intended" for years).
Of course, they are seemingly unable to fix bugs in Java that have been fixed by the community for many years - the fix I used for MC-2025, the most upvoted bug for Java Edition, and which is nearly a decade old, couldn't be simpler and seems to be reliable - and many of the other bugs I've fixed used code examples on their bug tracker, or open-source mods.
Java is smoother on PCs while being more grindy and much grittier. Bedrock has differences in how you move about while giving you mob drops, bonus chest loot, and some other things + blocks are a bit different e.g. snow can fall rather than break.
Bedrock feels designed for consoles with how it seems to focus on animation and resources while Java feels more of a serious MMO style despite being indie.
So Bedrock likes to despawn and respawn animals very often...yeah, Java wins then. I don't want to find sheep for a bed and then when I come back with shears they're gone.
"Better" is a subjective term; it always only depends on the individual. Also, everything has pros and cons, so nothing is wholly "perfect" (a word that's just a human concept).
Personally, I've an inclination toward Java Edition because it's the only version I've ever played, but have seen videos and read comments or articles about both Java and Bedrock, and the above statement remains true, in my opinion.
Java:
-Fan content is easier to get access to, no marketplace to speak of
-Old versions are completely accessible from Mojang's server to download and play whenever you want and mod if you know how to mod old versions.
-May not run as well as Bedrock but with performance mods (OptiFine, Sodium) or the right tweaking of the game (using Java arguments or other means) you can get it to run well instead of the bad job Mojang has made the game version to version, then fixing it and breaking it however many times Modders can point out.
-Command system is better. The OP system while not as UI accessible as Bedrock before launching the world, isn't in your way and it's in commands instead. That and commands don't prefer achievements.
-Redstone, don't need to say more those that know, know.
-As weird as it is I like the creative mode flight drift, Bedrock doesn't have it (whether for nausea or not which is a fair reason to not have it so a mod is required in Java to prevent it). It also goes for the swimming controls to since 1.13 I don't like it in Bedrock and it's like the auto-step feature in Vanilla compared to mods it just doesn't work very well.
-Multiplayer can be alright. Though people can go with Realms if they want but otherwise if you don't know how to set up a server for yourself then good luck. But depending on that of course it will be a fine or rough time. I did a few modded server playthroughs to test datapacks, record a modded server play as recent examples but I'm not a multiplayer person really or ever tried minigame/PVP person so can't say for those experiences.
-Seed sharing is more clear on Java I find than Bedrock other than version to deal with it may or may not work while with Bedrock no older version access means that seeds may not work but otherwise it may or may not be down to whatever console/Windows 10/Pocket Edition version of the game possibly. In more so a case for legacy edition
Bedrock:
-Marketplace for fan content is easiest way but fan content exists on MCPEDL.com for example which is where I get Behaviourpacks as you can't get them on the marketplace and of course other content exists there too that like Curseforge and the Java method is 'free' and 'open to anyone no storefront' even if yes the creators do get a cut on the marketplace and that MCPEDL can be awkward like the Forum days of adfly and so on annoying it's still something.
-Can't use old version only moving forward as the option unless you don't connect to the Internet I guess.
-Performance is better than Java Vanilla.
-Controller support without a need for a behaviourpack
-Redstone isn't as great due to the bugs used in Java not being present besides the C++ or C# and Java differences in coding language too.
-I don't like the lack of creative mode drift or the swimming in Bedrock.
-I assume multiplayer may be better and of course crossplay is a thing with all versions of Bedrock. I have only used the Legacy Console versions for multiplayer whether split-screen on Xbox 360/One versions of the game or invites for the Diamonds To You trophy on my Vita (where there is no split-screen of course).
Those are what comes to mind.
Bedrock has it's place but I can make Java my playground Bedrock not so much.
Niche Community Content Finder, Youtuber, Modpack/Map Maker, Duck
Forum Thread Maintainer for APortingCore, Liteloader Download HUB, Asphodel Meadows, Fabric Project, Legacy Fabric/Cursed Fabric, Power API, Rift/Fabric/Forge 1.13 to 1.17.
Wikis I Maintain: https://modwiki.miraheze.org/wiki/User:SuntannedDuck2
What are the actual gameplay differences though? My understanding is that farming is very different, especially with mobs, there's obviously the sweep function that is missing for swords, but what others exist that are pretty defining?
None of the differences in editions have anything to do with Java being unable to do what C++ can do or vice-versa; it is all down to the development teams deciding how to implement things, for one reason or another (for example, for whatever reason diamond ore is about twice as common on Bedrock (Java = 6 veins of 0-5 + 1/9 chance of a vein of 0-23; Bedrock = 7 veins of 0-5 + 1/9 chance of a vein of 0-23 + 4 veins of 0-10), especially in light of the efforts for "feature parity". Likewise, they have refused to fix bugs on Bedrock that were fixed on Java, like fossils overwriting end portal frames (compare to the report for Java Edition); their claim of "can't be done because it will break world generation" is literally the weakest excuse possible - just do what I did and check that the block being replaced is not an end portal (frame) block. Similarly, MCPE-19426 can easily be fixed by porting over the simple loop that Java uses to ensure an end portal has been placed - C++ supports loops as does virtually every programming language so I have no idea why they haven't done this, even closing the report as "works as intended" for years).
Of course, they are seemingly unable to fix bugs in Java that have been fixed by the community for many years - the fix I used for MC-2025, the most upvoted bug for Java Edition, and which is nearly a decade old, couldn't be simpler and seems to be reliable - and many of the other bugs I've fixed used code examples on their bug tracker, or open-source mods.
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
Java is smoother on PCs while being more grindy and much grittier. Bedrock has differences in how you move about while giving you mob drops, bonus chest loot, and some other things + blocks are a bit different e.g. snow can fall rather than break.
Bedrock feels designed for consoles with how it seems to focus on animation and resources while Java feels more of a serious MMO style despite being indie.
Java is better in absolutely every way
I really prefer java ! it's much more better
So Bedrock likes to despawn and respawn animals very often...yeah, Java wins then. I don't want to find sheep for a bed and then when I come back with shears they're gone.
"Better" is a subjective term; it always only depends on the individual. Also, everything has pros and cons, so nothing is wholly "perfect" (a word that's just a human concept).
Personally, I've an inclination toward Java Edition because it's the only version I've ever played, but have seen videos and read comments or articles about both Java and Bedrock, and the above statement remains true, in my opinion.