Proton-Native instead of Electron

atom-archive / xray

An experimental next-generation Electron-based text editor

MIT License

8.48k stars 235 forks source link

Proton-Native instead of Electron #91

Closed kanishkarj closed 6 years ago

kanishkarj commented 6 years ago

Wouldn't having the UI built using Proton-Native be better that using Electron js? Because Proton-Native claims that it we can create native components using it.

ForsakenHarmony commented 6 years ago

Proton native is very limited and has basically no customisability

Read up on stuff

as-cii commented 6 years ago

I think this question is similar in spirit to #12, #28 and #41, and I believe the same answer applies here too. Specifically, we want to use more standardized/robust technologies and we think Electron provides us with everything we need to ship a powerful text editor like Xray. That said, we could revisit this decision in the future if there are compelling reasons to switch to a different framework like proton-native.