AlamofireXmlToObjects VS AEXML

Compare AlamofireXmlToObjects vs AEXML and see what are their differences.

AlamofireXmlToObjects

Fetch a XML feed and parse it into objects (by evermeer)

AEXML

Swift minion for simple and lightweight XML parsing (by tadija)
Our great sponsors
  • Appwrite - The Open Source Firebase alternative introduces iOS support
  • SonarLint - Deliver Cleaner and Safer Code - Right in Your IDE of Choice!
  • Scout APM - Less time debugging, more time building
  • OPS - Build and Run Open Source Unikernels
AlamofireXmlToObjects AEXML
0 1
65 938
- -
0.0 2.1
about 5 years ago 4 months ago
Swift Swift
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

AlamofireXmlToObjects

Posts with mentions or reviews of AlamofireXmlToObjects. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning AlamofireXmlToObjects yet.
Tracking mentions began in Dec 2020.

AEXML

Posts with mentions or reviews of AEXML. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-01-09.
  • Lessons learned from migrating a native iOS app to Flutter
    2 projects | news.ycombinator.com | 9 Jan 2022
    In the article, he mentions the need for a DOM parser dependency for his app, as Swift “does not have one.”

    > AEXML was needed to parse some XHTML files as the native iOS SDK does not provide a DOM parser.

    I have used Foundation XML parsers[0] for many years, but they are general-purpose; not specifically modeled on DOM or HTML, which probably limits usefulness on some Web content.

    That said, if he has control of the content (don’t know the app, so I am not sure), then there should be no reason that they couldn’t render it in XHTML, so the Foundation parser could be used reliably. In the article, he mentions that the content is XHTML. I have to assume that AEXML[1] is easier to use than the built-in parser. It uses Foundation parsing (it actually seems to be a lightweight wrapper for the built-in parser(, under the hood (and seems to be a well-written dependency).

    So, it could be posited that he would only need one dependency for his native version, if he wanted to handle the XHTML parsing, himself.

    [0] https://developer.apple.com/documentation/foundation/archive...

    [1] https://github.com/tadija/AEXML

What are some alternatives?

When comparing AlamofireXmlToObjects and AEXML you can also consider the following projects:

Fuzi - A fast & lightweight XML & HTML parser in Swift with XPath & CSS support

SWXMLHash - Simple XML parsing in Swift

XMLCoder - Easy XML parsing using Codable protocols in Swift

SwiftyXML - The most swifty way to deal with XML data in swift 5.

XMLParser - A lightweight XMLParser for assembling and parsing XML values written for iOS 8+ in Swift 2.

HTMLKit - An Objective-C framework for your everyday HTML needs.

XMLMapper - A simple way to map XML to Objects written in Swift

XMLText - Generate styled SwiftUI Text from strings with XML tags.

SwiftyXMLParer - Simple XML Parser implemented in Swift

CheatyXML - CheatyXML is a Swift framework designed to manage XML easily