3 ms·
You say it like Electron documentation is any better, for one, the scope of a project like electron is many orders of magnitude smaller than the Apple ecosystem
by omeid2 7y ago
You say it like Electron documentation is any better, for one, the scope of a project like electron is many orders of magnitude smaller than the Apple ecosystem APIs and second, it is barely any better. This comes from someone who has done a fair share of developing in both.
What I hate most about electron is the never ending pointless churn in quest for "modern".
Breaking changes like this that provide no real value is standard modus operandi:
https://github.com/electron/electron/pull/16570 https://github.com/electron/electron/pull/16570
Something as simple and fundamental for desktop applications, Instance Management, changes every release or so, and is primitive at best (a simple mutex and event, with no way to pass metadata other than the instance flags).
The portable builds are half-ass too, can't build a separate 64bit and 32bit version for windows without building twice and cleaning up.
Many many other issues like that, it is a case of torture by a thousand cuts and forever trying to keep resource consumption under control.
Electron sounds good in theory, but in practice it barely scratches "good-enough".
- Klonoar 7y agoCore Electron documentation is akin to wondering where the docs for NSApplication are. They exist and are easy to find, but they might be confusing at points if you don't get it, or it's not documented - but it's a smaller surface area. How you build things in Electron is akin to the web rendering API, which has ~20 years of backwards compatible guides and documentation. There is, full stop, not a single thing out there that is as well documented as HTML/CSS/JS. (Edited to note that parent comment significantly edited since my reply. I'm not debating in this format.)
- auggierose 7y agoI'd say that AutoLayout is much better documented than CSS; because it is a much better concept in the first place.
- Klonoar 7y agoAutoLayout is amazing. I love it and personally think it's better too... ...however, when it first got added to iOS, Apple notably had crappy documentation for it, and the performance was abysmal so it had uptake issues where people would still resort to manually judging frames. Moreover, it doesn't matter. CSS is a juggernaut and it's not going away anytime soon.
- deleted 7y ago[deleted]
- TazeTSchnitzel 7y agoHTML, CSS and JS, as open standards with multiple vendors, have the amazing advantage that if you can't find good developer docs you can just read the spec and it will tell you precisely how something works.
- omeid2 7y ago> if you can't find good developer docs you can just read the spec and it will tell you precisely how something works. Or rather, how it is supposed to work, but good luck with anything non-trivial. Though the state of things is much better recently than it used to be, but still a long way between implementations and spec.
- TazeTSchnitzel 7y agoAre you reading W3C or WHATWG?
- Klonoar 7y agoI've been doing this for 10+ years and the absolute last thing I'd do is stop and read a spec from them. Not that I don't think it's useful, it just (in practice) ends up with edge cases per-browser that I'd rather find out upfront. Edit: The above probably sounded more harsh than intended, haha... don't take it as derision please. Just noting my thoughts on specs.