When comparing Allegro vs SFML, the Slant community recommends Allegro for most people. In the question“What are the best 2D game engines?” Allegro is ranked 19th while SFML is ranked 30th. The most important reason people chose Allegro is:
The Allegro community has produced a lot of great tutorials and resources. Allegro [Wiki](https://wiki.allegro.cc/index.php?title=Main_Page), Mike Geig's Allegro [Tutorials](http://fixbyproximity.com/2d-game-development-course/), Rachel Morris' [Tutorials](https://www.youtube.com/watch?v=E4RqHtEAAds), CodingMadeEasy's [Tutorials](https://www.youtube.com/playlist?list=PL6B459AAE1642C8B4&feature=plcp).
Ranked in these QuestionsQuestion Ranking
Pro Supports desktop and mobile
Support for Windows, Mac OS X, Linux, iPhone, and Android
Pro Good engine architecture
Allegro is well designed, easy to use and has many useful features.
Pro Good documentation and lots of tutorials
Since it has been in development since mid-90s with hundreds of people contributing to both the engine and documentation, it has all of its bases covered when it comes to standard support.
Pro Per-platform library optimization
Allegro uses DirectX for Windows, and OpenGL for other targets.
Pro Freedom to implement your own game engine
You are not bound to the limits of existing game engines, and you can actually implement your own engine.
Pro Very efficient and usable
Pro Zlib/PNG license
In short, SFML is free for any use (commercial or personal, proprietary or open-source). You can use SFML in your project without any restriction. You can even omit to mention that you use SFML -- although it would be appreciated.
Pro Can be combined with OpenGL
If you hate something about the way SFML handles graphics, you can just combine it with OpenGL. It's completely smooth and works as expected, without any additional dependencies.
Pro Active community and wiki
You can ask questions on their own personal forum which is full of users, and their wiki is constantly being maintained. They even have an IRC.
Pro Works on every platform
SFML 2.2 brought forth Android & iOS functionality, and SFML games work on Linux, Mac and Windows out of the box, since SFML is written with OpenGL.
Pro Great documentation
SFML is very well documented, even with short examples of use for many functions and modules. Furthermore, there are books like 'SFML essentials' and 'SFML for game development' which teach you how to use this library to its fullest.
Pro Good for OpenGL
If you are thinking about using OpenGL, look no further, you can open a window, and handle events in less than 15 lines, and it provides input, time, and even networking, plus alot more. It has become my favorite c++ library :D
Pro Great library
SFML is a collection of modular, well designed libraries you can implement an engine or game on top of. The API provides tons of good documentation and is very straightforward to use. You can get a game up and running with SFML quite quickly and with minimal effort.
Pro Clean code
An SFML project's code-base is usually clean and easy to read. All public SFML classes are under the namespace "sf" so it is easy to tell which code is yours and which belongs to SFML (of course you can stop this by typing
using namespace sf;).
Pro Available in many languages
There's support for many languages besides C++, current supported languages are: C, .NET, Crystal, D, Euphoria, Go, Java, Julia, Nim, OCaml, Pascal, Python, Ruby and Rust, and this list is constantly growing.
SFML is extremely beginner friendly and even provides pre-built libraries for your IDE of choice on Windows. Besides the fact that it's extremely well documented, they also have a set of tutorials that walk you through every module.
Pro Modern C++11 implementation
SFML is one of the few good C++ frameworks out there to actually make full use of the language. It's extremely well optimized and it plays well with anything you throw at it.
Con Learning curve for hobbyist developers
Hobbyist developers coding alone may experience a learning curve with Allegro of about 200 hours (if you are rusty on C++). To learn quickly, see Mike Geig's tutorials at Fix By Proximity. This learning curve may be fine if you are considering going professional, but are still unsure.
For hobbyist developers not planning on going professional, you may want to look into a complete 2D game engine, rather than a coding library. For example, there are "non-coding" engines that provide support for coded plugins or scripting. But, if you are a dedicated hobbyist planning to use Allegro as your coding library of choice, you can still develop great games as a hobbyist.
Con Isn't great for C++
If you are a fan of object oriented programming, and want to use this library, then the chances are that you are going to be creating a lot of wrappers for functions in this library.
In short, if you're a C++ person, it could be recommended to check out SFML instead.
Con Relatively slow
Compared to SDL2, GLFW, it is slow.
Con No GUI editor or IDE
Does not include any IDE or media editor. It's purely source code.
Con May take longer to learn and understand
Con Messy sprite management
Sprites retain all of the operations applied to them, whether that be a new position or a rotation. This makes sprite management somewhat annoying.
Con Not specifically a 2D game engine
It isn't really an engine, more of a collection of modular, well designed libraries you can implement an engine or game on top of.