3 ms·
To have an educated opinion on whether it's the right choice for us, one must know: 1. How much existing code is there to integrate with, and what language is
by freedomben 8y ago
To have an educated opinion on whether it's the right choice for us, one must know:
1. How much existing code is there to integrate with, and what language is it in?
2. What is the experience level of the existing team, and in what platforms?
3. Who is the target market? How will they use the product?
4. What capabilities will the app need? Will it be graphics intensive?
5. What will the maintenance story need to look like?
6. How much time/money can be thrown at this? (ties into how long we can spend working on it)
7. When must it ship? (Also speaks to iteration speed)
8. How hard will shipping updates be?
And probably more that I couldn't think of just now. In order to have a productive discussion about whether electron is the right choice, I would need to detail all of that. Unless of course you just want to use the "electron is never the right choice" argument without knowing anything about our situation, which is what I see on HN a lot every time electron comes up, and what I was pre-emptively hoping to avoid. I might also say that I am not a fan of electron apps, and only use them when I have to (mostly due to huge size and memory requirements, which I don't fault electron for, but rather I fault the developers that are not conservative with resources and memory allocations). That said, I'm glad it's around because there are apps I don't think would exist without it.
I would actually really enjoy having the discussion about whether it's a good choice or not, but it would be good to have that separate from my original question. It likely would have be drowned out in the noise.