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

Thank you for the feedback. Yes - Gemini was a big help but as I also work / train LLM's I know very well how to use them and their limitations. With this, I can use them much more efficiently.


I think it's pretty simple. I'm just focused on the core features right now but I definitely plan to sign it in the next 1-2 weeks. Thanks :)


I wouldn't make the Apple Developer dance a priority unless you intend to sell a commercial signed version.

Few reasons.

1. It's 100$ a year, which isn't pocket change when it's making you no revenue.

2. Apple likes to randomly deny developer accounts.

3. They have no issue with outright rejecting apps with vague reasoning.

4. Plenty of high quality raw editing apps already exist for OSX.

If someone really wants to use it on OSX you've provided clear instructions.


I find it absolutely bizarre that people post about stuff they are seemingly have no idea about. Like, code signing & notarization provides clear quality of life improvement for many users. And your reasons are just plain wrong.

1. 100$ is a pocket change for many people. Depending where you live. I think it is enough of a barrier to force a thoughtful action. Also, to compare, cheapest certificates for signing windows software are like 450$/year. Microsoft has a hosted service now for $15/year, but that is still in beta. Both of those options are significantly more expensive than 99$/year Apple charges.

2. No, Apple does not deny randomly access to developer accounts. Also, this is quite besides the poin.

3. Code Signing has absolutely nothing to do with submitting your app to app store, or anything Apple has to approve of. Like, why even write about something you have no idea about?

4. True. Not sure how it is relevant.


100$ a year is a lot of money if you aren't planning I'm selling anything. The instructions to build from scratch or run it without signing aren't difficult.

I've literally had to argue with Apple for months to get my account approved.

It was not a fun process, eventually they did grant me an account, but then just keep up an old hobbyist game I was wasting that 100$ a month.

I ended up just recompiling for WebGL and uploading to itch.

Going through the hoops for code signing and getting account doesn't make sense if OP isn't going to sell it on the app store.

Finally, it's not like this is the only raw editor.

How many people.

A: Will pick an open source feature lite raw editor which isn't going to be as good as Darktable or Lightroom.

And

B: Aren't willing to build from source or literally run a single terminal command to run the unsigned version.

Now, if OP wants to sell it on the app store then I'm completely wrong. But otherwise it's not a good use of time.

You're free to reach out to OP and offer them 100$ + another 300$ for time spent having to apply for a Developer account.


Yes you are completely right. This part is definitely not optimal yet. I haven't had lots of Tauri / Rust experience before this project.. it's on my todo list to improve. While trying to use the asset localhost protocol I ran into a lot of permission issues.


Its pretty simple to explain: Imagine you have your images in a folder and you rename this folder, without RapidRAW knowing this. It would fail to associate the edits with the image. Lightroom does it the same way. Or imagine you‘re editing on your computer and want to move to your laptop to continue editing - the edits would only be saved on the computer, if it‘s only saved in the app library.


My folders do not have a series of sidecars written by Lightroom. The edits are stored within Lightroom’s library. I have other programs that use sidecar files, but Lightroom does not. Maybe it’s a preference, but I’ve never looked. If I move/rename a folder Lightroom was looking at, it asks me to relink it when I next open Lightroom. It’s not an earth shattering situation to fix.


Thanks for trying out RapidRAW and for the feedback. Currently I optimized the app to load small-medium sized folders (e.g. 1-300 images). Its expected that the app lags for folders with more images.

Its a high priority to optimize the loading speed of large folders and you can expect an improvement in the coming days.

Kind regards, Timon


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

Search: