vmsp (u/vmsp) - Readit News

vmsp commented on Valdi – A cross-platform UI framework that delivers native performance github.com/Snapchat/Valdi... · Posted by u/yehiaabdelm

vmsp · 2 months ago

Snapchat also maintains Djinni, used to generate type-safe bindings for C++ code. With Valdi, it seems like they chose to go another route.

https://github.com/Snapchat/djinni

vmsp commented on Valdi – A cross-platform UI framework that delivers native performance github.com/Snapchat/Valdi... · Posted by u/yehiaabdelm

JaggerJo · 2 months ago

Excellent Points, this is where the answer is "it depends".

> What do you put in the common core? Android does HTTP requests one way. iOS does them another way. You go for the lowest common denominator an implement a third way, using libcurl or something?

If it's really functionality that cannot reasonable be shared don't share it.

It's probably more work to maintain bindings to a single API client in the core and fiddle with all the details of not using the native HTTP client implementations that it is to implement the API client twice.

Writing the API client twice is boring, but that's a good thing.

> Or do you just put business logic in the common core? Is there really that much business logic that doesn't issue requests or access a database?

The shared core is optional. You might have the need for it, then it's a good solution.

For an app like snapchat you'd probably share the video effects and have that in your core library.

vmsp · 2 months ago

That's perfectly reasonable but, at that point, the argument becomes: build 95% natively and maybe there's a 5% "core" that warrants extracting into a common lib. Technically? That's excellent architecture. In terms of saving development time — which is where stuff like React Native comes in? Not so much.

vmsp commented on Valdi – A cross-platform UI framework that delivers native performance github.com/Snapchat/Valdi... · Posted by u/yehiaabdelm

JaggerJo · 2 months ago

Just write 2 native UIs in the 2 platform native languages and share a common core written in any language that offers a C like FFI.

How hard could it be?

vmsp · 2 months ago

I hear this and it makes sense but when I actually go about implementing it, it quickly falls apart.

Most apps are UI, remote requests and maybe some storage. What do you put in the common core? Android does HTTP requests one way. iOS does them another way. You go for the lowest common denominator an implement a third way, using libcurl or something?

Or do you just put business logic in the common core? Is there really that much business logic that doesn't issue requests or access a database?

vmsp commented on Fenster: Most minimal cross-platform GUI library github.com/zserge/fenster... · Posted by u/klaussilveira

vmsp · 4 months ago

There's an accompanying blog post at https://zserge.com/posts/fenster/

This author has some pretty cool stuff, like a tiny alternative to Firebase https://zserge.com/posts/pennybase/

vmsp commented on Ask HN: Is it time to fork HN into AI/LLM and "Everything else/other?" · Posted by u/bookofjoe

vmsp · 5 months ago

No. This is a trend. HN is a tech and startups website so it will show trends. At one point it was VR, eventually it was Web 3.0. Right now it's LLMs but this too will pass and something else will come along.

vmsp commented on Ask HN: Who wants to be hired? (July 2025) · Posted by u/whoishiring

vmsp · 6 months ago

  Location: Portugal
  Remote: Yes
  Willing to relocate: No
  Technologies: Ruby, Rails, Python, Django, Postgres, React, Node, Go
  Résumé/CV: https://0x1.pt/Vitor_Sousa_Pereira_CV.pdf
  Email: vmsousapereira@gmail.com

Currently Lead Engineer at a London-based AI SaaS. Been there from the very start. Looking to switch industries.

vmsp commented on Sapphire: Rust based package manager for macOS github.com/alexykn/sapphi... · Posted by u/adamnemecek

vmsp · 8 months ago

Homebrew was kind of slow, at one point, but I find that it works pretty well these days. Still, this is pretty cool and competitions is always good.

Interestingly, I always imagined that a would-be replacement would come written in Swift. I guess I was wrong.