11–20 of 24 posts
Flickr's API is still the best. Does everything you want it to. Has a few fun surprises that you didn't expect that make it even more fun to make things with. Simple to use. Well documented. Test playground at your fingertips to experiment with any call you like. One of the first APIs ever released and you can still count the number of other available APIs that positively compare on one hand.
QT5.. It's so well documented, and just a pleasure to work in. I'm almost never using it though.. I mostly work with the Node API, and some of the larger libraries in the infrastructure, it's fairly okay too.
... but they have a magnificent 'context' problem: Qt is complicated and you never really know where you are in the architecture. There are 8 'Window' classes and you don't know if it's for Widgets, QML/Quick, QGraphics, or legacy or what.
I double-dare you to go and figure out what JS engine they currently use and for what. Because it's evolved so much over the years, and they keep legacy stuff around, StackExchange comments are poorly noted with versioning, it's a labrynth of disinformation.
There are neat articles you can find if you dig, but my god, you shouldn't have to dig.
I learn 'foundational' things about QT all the time, and to add salt they have an article where they dare to indicate it's 'our' problem for their incoherent documentation, they literally state 'Dunning-Kolberg' effect on one of their pages! Total gaslighting.
The desperately need 'overview' documentation that are accessible and put everything in context - and especially it needs to be just presented in an organized way - literally the Left Hand Menu of their docs jumps around and you have no context. You're looking at Qt5 classes, search for something and only Qt6 variations come up, you have to flip to Google etc..
Some Qt classes are well documented, but there are serious problems. I honestly think Qt would be 25% more popular if they just explained things more clearly.
Spotify API - well documented, straight foward to use, and has made it easier for manage my library and make playlists for myself.
I really like Telegram's bot API. https://core.telegram.org/bots/api Helps me automate stuff around my life with a few small apps that connect to Telegram message threads. Summaries from other APIs, smart home functionality, family errands and shopping list reminders with my spouse and more.
QT5.. It's so well documented, and just a pleasure to work in. I'm almost never using it though.. I mostly work with the Node API, and some of the larger libraries in the infrastructure, it's fairly okay too.
It's interesting how many people say this. Much of it is great compared to an abysmal baseline of terrible APIs often in C++ ... ... but they have a magnificent 'context' problem: Qt is complicated and you never really know where you are in the architecture. There are 8 'Window' classes and you don't know if it's for Widgets, QML/Quick, QGraphics, or legacy or what. I double-dare you to go and figure out what JS engi…
I really like Telegram's bot API. https://core.telegram.org/bots/api Helps me automate stuff around my life with a few small apps that connect to Telegram message threads. Summaries from other APIs, smart home functionality, family errands and shopping list reminders with my spouse and more.
This sounds interesting. What does it look like in reality? For example, the errands and shopping list reminders.