Hacker Newsnew | past | comments | ask | show | jobs | submit | tcoff91's commentslogin

Also, the back 'button' is mostly a thing of the past in Android and it's more similar to iOS now with the predictive back gesture.

The Android back button is legacy.


And on top of that, they're losing the ability to ship hotfixes over the air and will always be at the mercy of apple & google to deliver their updates.

It's incredibly easy nowadays to drop down to native from react native where you need to.

I work on an open source app that uses a shared swift core for the iOS and android apps and I think it's awesome. I think having all your business logic in swift is great.

At work, we use react native, and although the upgrades and stuff are painful, I'd never give up the ability to ship over the air updates.


Over the air updates is SO valuable with react-native. Being able to ship hotfixes instantly to our users has saved our asses multiple times.

I absolutely love jj (just check my HN comment history). One thing I'd love to see in jj though that git does better is copy tracking. If somebody renames a file upstream, and you go to rebase your commit that touches that file onto main, jj doesn't handle this very well compared to git.

Do you have any idea if this is coming to jj soon?


There is active work in this area, yes! https://github.com/jj-vcs/jj/issues/3386 is the bug tracking the feature request, and there have been some recent PRs working on implementing this, see here for one example: https://github.com/jj-vcs/jj/pull/9864

Do you happen to have or know of any good open source projects on any public platform like GitHub, gitlab or Codeberg, that uses Jujutsu/jj?

It's hard to tell since any given dev can just use jj locally, if they want to, while everyone else uses git.

Technically, you can still tell actually - jj writes a "change-id xyz..." in the git commit object header, which remains there as it's pushed around. It's just typically not made visible by regular things. (I wonder what other random garbage has been hidden in git commit headers that noone has seen)

Huh, fortunate for it that GitHub (especially) preserves it then!

I wonder how guaranteed that is, can imagine GH deciding to 'clean' it (how much data can you put there theoretically? Or to close a range of potential security issues) and suddenly relatively niche but genuine uses like jj's change-id are unintentionally not preserved.


Cleaning it would change the commit ID, so a forge cannot clean it even if it wanted to (not without rewriting all descendant commits too and breaking signed commits, at least).

The change-id is exactly as much part of the commit object as the author/committer name/timestamp, description, parent commit ID, tree, and participates in the commit hashing as those do.


Various git commands can drop the metadata, so it’s not guaranteed to stick around.

All my prs are named phil-<hash> and have been for years now. I keep waiting for someone to care/notice, but no one has.

jj uses git as a backend. None of those need to "use" jj. You can use jj in an existing git repo, with your git wielding friends.

If I remember correctly, Mitchell Hashimoto uses it for Ghostty (probably under the git backend).


Even if you don't use the immersive reading feature, it's really nice to be able to switch back & forth from reading to listening. It's nice to be able to start reading right from the sentence where you left off listening to the audiobook. Storyteller is a great e-reader and audiobook player regardless of if you use the immersive reading.

Also, it's just fun to have the audio narration as you read. I typically set the speed to like 2.5x when doing readaloud.


Storyteller works great for this. It even syncs your position across devices. So when I really want to settle in to read, I go ahead and switch from my iPhone where I was listening to my Boox e-ink reader which syncs right to where I left off.

The storyteller mobile apps have supported readaloud for years. You can even set different playback speeds for readaloud vs listening, so when you background the app or lock your phone screen, it will switch from the readaloud speed to the listening speed. I typically use like 2.25x for readaloud and 1.5x for listening.


Yes they have, but they didn't have the ability to align a book _on device_ like Apogee does. It just listens for a few seconds of audio to find where you are in the book and then aligns automatically going forward without having to pre-process.


Could you link to this Apogee app? i'm interested to see other apps in the space.

On-device alignment is coming in Storyteller v3 apps.


You should check out Storyteller. It aligns ebooks with audiobooks to create EPUB3s with media overlays so you can do immersive reading. It also gives you a place to organize your audiobooks and epub library.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: