24yo French web dev

Main fediverse account (Mastodon) : @KaKi87@mamot.fr

  • 2 Posts
  • 4 Comments
Joined 1 year ago
cake
Cake day: June 25th, 2023

help-circle
  • The advantage of being Ubuntu-based is faster updates.

    The drawback is Snap, but it can be disabled.

    Therefore, I think Pop and Mint should continue being so and doing that.

    On a side note :

    CalVer might be better for a more general audience

    I disagree with this nevertheless, because when users learn what major/minor/patch mean, they can better understand how developers work and why should they upgrade.

    Also, coincidentally but relevantly, CalVer is an homonym of the French calvaire which means misery.



  • dictionary/array hybrid

    That’s a name, thanks !

    Serialization might not behave as you would expect (JSON.stringify)

    Actually, my implementation idea relying on Proxy don’t have this issue.

    As for other implementations, they do have this issue, but as they say, hybrid array use cases don’t generally involve the need to stringify, and even when they do, using Object.defineProperty with { enumerable: false } (or replacing the toJSON method) would fix it.

    3rd-party functions might not be able to deal with your data structure properly (again, potentially unexpected behavior). You can’t easily access array methods (find, filter, map etc).

    Actually, it would still be an Array, so no, there shouldn’t be any problems, and yes, those methods definitely work, which is precisely what said I want to achieve.

    How do you distinguish between ID access and index access?

    If your IDs are integers then there is no need for an hybrid at all, precisely because all you have to do is put each item at the same position as their ID.

    It’s harder to reason about access time of lookups. However, this might not be a concern of yours.

    I’ll definitely run benchmarks so that users would be aware of performance losses, if any. But use cases of hybrid arrays are mostly small datasets so it usually shouldn’t be a concern indeed.

    It may cause confusion if you’re working with other developers.

    If I implement this, it will be as a documented and commented package, so it shouldn’t be that much of a problem.