It looks like an open source project. Makes a hell of a lot more sense to implement using that than rolling your own? If it’s missing something you need, write it for them.
Writing your own implementation is extremely unlikely to differentiate your app/product. There is a spec, either you implement it and it works, or you don’t and it doesn’t. Using a maintained library is by far the better option.
Focus your time on the product you are building not the tech.
tofu@lemmy.nocturnal.garden 4 weeks ago
I’m not sure about that. Sometimes it’s more about properly applying libraries. Thinking of database handling or cryptography
rimu@piefed.social 4 weeks ago
Imagine you want to write a competitor to PostgreSQL and you start out by importing SQLite into your project and building on top of that. To you it seems like a good idea because you've never written a DB app before and the only DB you've ever seen before is SQLite. You'll get a prototype real fast but you'll never build a PostgreSQL equivalent because you never learned the foundational knowledge of how a DB works and because SQLite forecloses all the pathways you need to get there.
Same thing.
sorrybookbroke@sh.itjust.works 4 weeks ago
I’d argue this is more like “I want to build a competitor to spotify so let’s decide between using mariaDB or writing an SQL compliant database from scratch”
In your example, a database is the end goal and you can either start with a premade or make your own.
Here, a social media platform is the end goal. Activitypub is a very important part of it but it’s not the entire piece.
If we replace the parts of your analogy with the original your example would parse out to “I want to make a competitor to lemmies ActivityPub integration, so let’s start with fedify” which is not the same as the article states.
Now, should you re-impliment a protocol yourself or use a generic library is the real question. Both have their benefits. With option A you have full code ownership and can wrap your solution around your end goal without the issue of dealing with the original to get needed changes accepted. You don’t have to worry about code not written by or understood by you. With option B, you get a more robust and almost certainly more accurate implementation. Along with, for free, better integration with any service using the same library. Very useful for a federated service when talking about cross platform.
Both have many more positives and negatives of course and each person should decide on their own how to proceed.
My opinion? I think it’s usually best to own anything which could feasibly be understood by a single dev. Even if each dev doesn’t. Anything larger shouldn’t be internal in my strong opinion. Most negatives of an external library also apply at that point with enough time.
Jesus_666@lemmy.world 4 weeks ago
Of course you wouldn’t use an existing database engine as the foundation of a new database engine. But you would use an existing database engine as the foundation of an ERP software, which is a vastly different use case even if the software does spend a lot of time dealing with data.
If I want to build an application I don’t want to reimplement everything. That’s what middleware is for. The use case of my application is most likely not to speak a certain protocol; the protocol is just the means to what I actually want to do. There’s no reason for me to roll my own implementation from scratch and keep up with current developments except if I’m unhappy with all current implementations of that protocol.
Of course one can overdo it with middleware (the JS world is rife with this) but implementing a communication protocol is one of the classic cases where it makes sense.
rglullis@communick.news 4 weeks ago
That’s a complete apple/oranges comparison. Fedify is an application framework.
Try “Imagine you want to write a competitor to {Mastodon/PixelFed/Lemmy/PieFed/Pleroma/WriteFreely}”, and see where your analogy takes you.
tofu@lemmy.nocturnal.garden 4 weeks ago
Not same thing. I’m not talking about a postgres competitor. The other two replies already phrased it pretty good IMHO. I don’t think that, when building a fedi app, impending AP is the core of your app.