Email or username:

Password:

Forgot your password?
dansup's posts Post Back to profile
Top-level
F4GRX Sébastien

@dansup i am not familiar with the code base, true, and devil is usually in the details I know, but I am familiar with long term compatibility of evolving products.

A stable versioned api is good. I think most of the work should be on client apps, right? Client apps can test for new versions of APIs and gracefully fall back on previous versions? This sounds like a valid design pattern even if I'm not actually familiar with the implementation details...

2 August at 9:59 | Wall-to-wall | Open on chaos.social
3 comments
dansup

@f4grx No yeah, I understand, and in a perfect world, clients would be able to negotiate that but in reality it's a lot more complicated than that.

For example, clients have to parse the software to know what APIs they are dealing with, and such a complex feature like Comment Controls would need to be implemented carefully so as to not break existing APIs, while gracefully handling clients that can

Now throw in forks like glitch, it's not so easy to determine the API schema and thus, this feat

2 August at 10:02 | Open on mastodon.social
F4GRX Sébastien

@dansup yeah, devil in the details as usual. If that compatibility rule is not baked it from inception it's hard to do later.

I work with smart carts, with long develop/deploy cycles, so we usually think about the future much more than in a web app. Yet this "careful" design is possible everywhere. It's probably also more annoying to design. I understand.

2 August at 10:07 | Open on chaos.social
F4GRX Sébastien
Go Up