4 ms·
Going to be starting a new electron app very soon (please, no comments about whether it's the correct choice and we should be using ${favoriteLibrary}. We disc
by freedomben 8y ago
Going to be starting a new electron app very soon (please, no comments about whether it's the correct choice and we should be using ${favoriteLibrary}. We discussed the pros and cons extensively, and we believe it is the best choice for us and our domain).
Are the breaking changes here significant enough as to render existing tutorials and such obsolete/inaccurate? If so, are there newer tutorials that would be better?
- farnsworth 8y ago> Are the breaking changes here significant enough as to render existing tutorials and such obsolete/inaccurate? That's not likely, the breaking changes are in the details of API. The fundamentals are the same.
- postalrat 8y agoYou believe it's the best choice and don't want to hear anything different. That's nice.
- fortyseven 8y agoAnd?
- freedomben 8y agoTo 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.
- cobar 8y agoThey should be pretty minor. I've found that it's rare you need to rely on any of the Electron APIs. For the most part, Electron just provides a shell to load HTML/JS/CSS and that's where the overwhelming majority of the code lives. The only time you need to access Electron APIs is to create and manage windows, system menus, etc. For all the hate against it, we've been very happy with Electron. There's no way we'd have been able to afford to offer Windows and OS X given our limited budget without it.
- murukesh_s 8y agoEven with large budget it's pain to keep two codebase with different issue trackers etc..
- WorldMaker 8y agoTo add to the other answers here, Electron recently switched to an approach to semver where major dependencies (in this both Node and Chromium) are always considered themselves a semver major/breaking change. This aligns with Node's similar, less recent switch to semver major for all V8 upgrades. The biggest breaking changes here are very much that Chromium and Node were both upgraded. These are particularly breaking changes if you are using and/or building native Node libraries. Skimming through the rest I didn't see anything that directly impacted any of the apps that I've worked on or any of the tutorials I've seen.