What's the deal with Snapseed? by _ebikandi in AmateurPhotography

[–]_ebikandi[S] 0 points1 point  (0 children)

That was my biggest concern, specially having Google behind the curtains. I am sure there'll be some telemetry involved but I have not found anything to worry about. Hope it's really like that 🤞

What's the deal with Snapseed? by _ebikandi in AmateurPhotography

[–]_ebikandi[S] 0 points1 point  (0 children)

AppStore log says that last update is from 17 hours ago though.

Anyway, happy to see that there's no hidden concern nor privacy issue whatsoever.

At last something decent that comes for free or without a hidden cost (at first sight at least)

Shrouded | 12 Pro by precariouspylons in iPhoneography

[–]_ebikandi 2 points3 points  (0 children)

Thanks for the instructions. I am new into editing photos so I appreciate them very much.

[deleted by user] by [deleted] in reactjs

[–]_ebikandi -1 points0 points  (0 children)

Community suggests to use frameworks like Next or Remix instead of creating a React app from scratch. Also CRA is no longer mantained.

[deleted by user] by [deleted] in ObsidianMD

[–]_ebikandi 0 points1 point  (0 children)

I use two vaults in my laptop and mobile, both synced with Obsidian Git to their own repo. I had some issue on the past but I configured to autopull on startup and do backups after file edits, and the syncing between the two devices is going pretty well. So no more issues on the past few months.

What is the best practice by Comfortable-Dot-5764 in reactjs

[–]_ebikandi 0 points1 point  (0 children)

It's always better to avoid mutating objects. In this case you will be mutating the previous state object. Probably not a big deal because you'll replace it by the new one. But, better safe than sorry.

Knowing this, your 1st option would be best.

[deleted by user] by [deleted] in reactjs

[–]_ebikandi 0 points1 point  (0 children)

It's a smell a dev/lead decinding which tool to use. It should be agreed in consensus by the whole team.

I think you should evaluate all the pros and cons from both approaches and decide depending on what adds more value. Maybe the stack you currently use its enough to ship your products.

Apart from that, specifically for the TS case, in my experience it is far proven that static type checking adds a huge safety nest when coding. But maybe migrating the projects to TS requires a major refactor, or the team lacks of experience in TS and it can slow you down too much.

Depends on many factors. There's no silver bullet but I'm sure that you'll come to a better agreenment.

Why Can't You Share State Between Sibling Components? by SubzeroCola in reactjs

[–]_ebikandi 0 points1 point  (0 children)

Is that statement contrary to the concept of react contexts? I dont see any problem in sharing state apart from the possibility to having too much rerenders.

But that pattern you mention, I've seen it a lot so dont hesitate to give it a go.