When comparing libGDX vs Blender, the Slant community recommends Blender for most people. In the question“What are the best 100% free and easy game engines for beginners?” Blender is ranked 15th while libGDX is ranked 19th. The most important reason people chose Blender is:
Blender is licensed under the GPL. Some Blender modules such as the Cycles rendering engine are licensed under the Apache 2.0 license.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Lots of resources to learn from
Lots of references, tutorials and open source code to learn from.

Pro Great performance across devices
While it may not always have the best performance for a particular device or system, it's one of the few engines which consistently performs very well across different platforms.
Pro Fantastic UI toolkit (scene2d)
scene2d is a 2D scene graph, scene2d.ui is a UI toolkit on top of that. It enables very complex mobile and desktop UIs.
Pro Can use any JVM language
Since it's built with Java and runs on the JVM, any language that compiles to Java bytecode can be used to develop games with libGDX.

Pro Uses Box2D
A Java port of the Box2D physics engine is included in libGDX.

Pro Allows you to migrate from 2D to 3D within same framework
LibGDX supports both 2D and 3D game development. Allowing developers to migrate from 2D to 3D with ease without having to switch the engine they are using or having to learn a new API.
Pro Doesn't force a specific design
Unlike some engines, which only allow you to make your game in a few specific ways, libGDX allows you to design any type of game you wish as it is extremely customisable.

Pro Active and helpful community
The libGDX community, in the official libGDX forum is extremely helpful and approachable for any kind of question regardless of the its quality or difficulty.
The forums themselves are a very helpful resource for any issue or guide simply by searching past posts in there.
In addition to the forums, there's also the official #libgdx IRC channel on Freenode.
Pro Interfacing with platform specific code
Sometimes it is necessary to access platform specific APIs, e.g., adding advertisement services or leaderboard functionality provided by frameworks.
Pro Free, open source & permissive license
libGDX uses the Apache License 2.0.
Not only is libGDX free and open source but also it's license gives you a lot of power over the engine. As long as you provide a copy of the license, give credit, do not hold devs liable and do not use libGDX logo in any engine forks you can do pretty much anything you want.
Pro Kotlin support
It is written in Java so you can easily make games using Kotlin and Ktx project will help you get all advantages of this language.
Pro Very easy to customize
Pro Constantly improved
LibGDX itself is pretty mature, and get updates not quite frequently, but various libraries for it are actively updated.
Pro Across platform support
You can write once and run anywhere (Android, IOS, Desktop, Browser) also lately came with lib to deal with VR.
Pro Support for 3rd party tools
libGDX has built in support for many 3rd party tools, including (but not limited to) Bullet Physics, Box2DLights and the well-praised Tiled Map Editor.
Pro Lots of tutorials to get you going
Even though the official documentation might be lacking, there are many tutorials on YouTube for libGDX.
Pro Excellent font rendering support
Very good tools for rendering fonts.
Pro Similar to the Microsoft XNA framework
Old XNA users may like libGDX since it's API is actually very similar to XNA's.
Pro Focusing on object pool patterns, to control memory without pointers
Unlike Unity or other engine, it allows to optimize a language that uses garbage collector when using patterns of objects you can control the use of memory without needing a language like C / C ++, getting the same speed in a more productive language.


Pro Free and open source
Blender is licensed under the GPL. Some Blender modules such as the Cycles rendering engine are licensed under the Apache 2.0 license.

Pro Wide import and export format support
Support lots of modern 3D formats including DAE and FBX - ideal for game developers.
Pro Has a powerful rendering engine
Blender runs the Cycles path tracing engine under the hood. Cycles is a very powerful rendering engine capable of full path tracing (light fall off, caustics, volumetrics). It is mostly compatible with OpenCL and CUDA rendering, and is implementing mycropolygon displacement features. The upcoming release has a viewport engine called EEVEE whereby you can see and interact with your work in render mode in real time!

Pro Python extensibility
Blender embeds Python 3, which can be used to write add-ons, tools, extend the interface, rig characters and automate tasks.

Pro Powerful animation suite
Blender provides a full rigging system, and automates animation by interpolating between keyframe positions.
Pro Supports both low-poly and hi-poly modeling

Pro Regular release schedule
Releases are made every ~3 months.
Pro Sculpting and 3D painting features
Although Blender's 3d painting and sculpting tools (mostly painting) are not at par with specialized software like Substance Painter, ZBrush, or Mari, it is more than capable of getting most jobs done if the user takes the time to learn and understand it.

Pro Includes video editing & compositing tools
Blender's node-based compositor has comprehensive video sequencing and post-processing features.
Pro Node based modeling support
Pro Keyboard shortcuts
Good keyboard shortcuts for everything. Keep your left hand on the keyboard and your right hand on the mouse.
Pro Very useful for a freelancer
It offers a round solution (it covers many areas and professional fields) for a freelancer, for free, constantly updated, very polished, and allowing high quality results that clients do require. After some learning, it becomes very useful for professional work.
Pro Has a large community
There's a huge community to help you get started immediately.
Pro Coherent and streamlined workflow / internal use logic
The trick with Blender is to get used to its usage philosophy, as it keeps consistent through all the application. Once you get it, every feature or addition is learnt naturally, almost effortlessly.
Pro Very versatile
You don't have to switch between software when you want to do different things. Because modeling, sculpting, composting, video editing etc can all be done in blender.
Pro Generative geometry using nodes
Cons
Con Not starter friendly
Even default applications fail to load in Android. It doesn't have any documentation on errors either.
Con Documentation could be better
Other than a brief installation / getting started overview, libGDX's documentation consists of an official wiki with several incomplete pages, and automated Javadocs. The community recognizes these shortcomings, and new users are encouraged to ask for help.

Con The project slowed down in development
The number of active developers has decreased, many open issues and pull requests.
Con Build system is clunky
LibGDX uses Gradle, which is very demanding of memory and makes IDEs freeze on anything if your computer is not powerful enough.

Con Does not create compiled code
LibGDX runs entirely on Java and does not create executable binaries.
Con A bit difficult to use
This engine is not well put together. Is made from various free modules each with their own peculiarities. At times it feels you need to learn a couple of libraries rather than just one. Is not an engine for beginners as it requires coding. Lots of coding. You need to be intermediate to advanced in Java to develop in LibGDX.
Con Too many possibilities, no unified workflow
The operations are not optimized enough for specific tasks.
Con The physics engine is a bit lagging behind, especially the destruction physics
Con Difficult learning curve
Blender has a history of being unintuitive, but the 2.8 overhaul made the program far easier for beginners to pick up, and changes continue to be made to further improve the experience. However, there is still a learning curve.
Con Not good for Industrial Design because it uses average vertex normals
You can not create a hard surface with a radius continuity degree along a surface using a specific radius value.
Con Vertex normal issues on edges after boolean operations.
After creating a simple boolean operation the vertex normals are broken. A lot of work to fix the issue and you loos surface continuity.
Con Bad vertex normal after boolean operations
Does not handle well polygon intersections. And need tweaking by hand points or adding average vertex normals via modifiers.
Con Does not handle NURBs
Is not capable of real hard surface for industrial design because is not able to reproduce surface continuity degree as a NURBs does and average vertex normal destroy surface radius.
Con Poor particle system
The Blender particle system can at times be a little limiting and finicky (and buggy) to get working. Even if it can get most straight forward jobs done, it is far from the most advanced system, and could benefit largely from advancements.
