It's a balance - personally I think apps that focus on a specific platform is exclusionary. So accepting some non-native feel means more people can use my app.
I agree that browsers make it hard though.
7,555 karma · joined May 7, 2009
It's a balance - personally I think apps that focus on a specific platform is exclusionary. So accepting some non-native feel means more people can use my app.
I agree that browsers make it hard though.
Unfortunately since I can't rewrite my project entirely, I'm going to need something that reduces bloat by using a local webview instead, so it's still web-based.
However, if something were to come along that uses the user's local webview instead and provided a way to bundle a node server with it, I could absolutely switch to it.
In fact, I've played with the idea of providing an app that only sits in your menubar and runs the server, and opening the app just opens a tab in your browser. But most users don't care as much about all this as we think and would find that odd.
You're right though - if something is working well enough it probably will end up sticking. Slack just goes to show that it's probably Good Enough despite what we feel about it.
The main reason to use Electron is that I can have happy macOS, Windows, and Linux users. Apps that focus on a single platform are exclusionary.
It's the same thing with any app, as you go further along development you will want to optimize in more advanced ways.
I'm not arguing that Electron doesn't have bloat though: https://news.ycombinator.com/item?id=20274725
Slack does not use the OS webview, it is Electron. I don't think it's a 3MB download - if it is it must just be an installer that installs the real thing? I haven't looked recently.
I see it as a stop-gap until I can invest more resources into something more lean. But I'm focused on the product right now, not rewriting the world and wasting time because of engineering ideals.
It goes on to say that there's a memory-intensive piece that I haven't even optimized yet and will rewrite into Rust which should bring the memory down a lot more.
If you only use a single local app, all of your data is entirely local to your device.
All other apps that host your data in the cloud have access to it, whether it's encrypted internally or not. What encryption buys you is the case if a hacker happens to get some of your data, they might not be able to decrypt it. But considering that the backend of the app itself must be able to read the data, the backend must be able to decrypt it, so a hacker could probably end up decrypting the data anyway.
End-to-end encryption in Actual will be better than all other cloud apps: I, even as someone with full access to the server, will not be able to read your messages. Only your device can.
It sounds like what you're really worried about is storing banking passwords unencrypted. We don't do anything like that at all.
This was back in 2014 though and sweet has changed a ton since then, so the output is probably different
It's a completely local and free app. Sign up and I'll be sending the beta out in the next couple weeks.
It embraces the envelope-style of budgeting, and does it in a way that makes it easy. I think this style of budget makes it really easy to see what's going on with your money without much work.
In addition to that, reports are important and we'll provide the ability to write any custom reports to tailor the system to your lifestyle. Everybody's life is different so we all have different needs, so it's important to allow flexibility.
Let me know if you're interested, or have any questions!
I retract my comment about "no matter what", but it still just boils down to running sqlite on a separate thread. In my opinion it's probably a lot easier to run sqlite in a separate thread (or process) yourself at the app-level. The code for writing async native bindings in node is very complicated (not even considering the thread pool), and you probably don't need every single operation to be async. That just adds a lot of overhead, when you probably just need a higher-level layer that says "execute these queries on the sqlite process and give me the results".
It's definitely a good example of buying into the "hype" of async without really understanding what's going on. Async is helpful when you need to wait on something in the future (like new packets come in from a socket) but don't want to block the whole process while waiting. It doesn't make sense at all for CPU work that's going to block it regardless.
I've lightly contributed to both better-sqlite3 and node-sqlite3 and the latter's async implementation makes it much more confusing and difficult to work with. And it slows things down considerably.
I switched node-sqlite3 with better-sqlite3 in my Electron app and found non-trivial performance gains. Make sure to run it in a separate process - never run sqlite in the main thread or the same renderer process as your app. If you run it in the main thread, it still blocks the renderer process. I wrote an article about this: https://medium.com/actualbudget/the-horror-of-blocking-elect...
I'm glad somebody finally made a robust synchronous API to sqlite.
There's just no way around it. If your managers won't freeze the project until you make meaningful progress, you're going to be stuck working with this ugly code for a long time. Try to convince them that in the long-term a cleanup will pay dividends. Without their support though, you won't get anywhere.
If you're able to freeze the code for a bit, it sounds like it might just be quicker to rewrite some parts like the CSS. Don't take on the whole project at once - find pieces that can be rewritten individually, even if it's a large part like all the styling.
I think you'll find that any code that deals with foreign function interfaces and interop with the host environment is ugly in any language.