Re:Proton Native – React Native for the desktop
by inamberclad on Wednesday May 02, 2018 @04:10PM
(#16980731)
Anything that reduces the number of running chrome instances on my poor little laptop would be nice.
[ Parent
| on HN ]
Re:Proton Native – React Native for the desktop
by robrtsql on Wednesday May 02, 2018 @04:56PM
(#16981094)
I tried out the example "Notepad" app in the git repo and it ran at 70MB. Is that good? I don't have any metrics about how much memory a hello world Electron app uses.
Re:Proton Native – React Native for the desktop
by babypuncher on Wednesday May 02, 2018 @06:27PM
(#16981710)
Well just for comparison, I have Notepad++ running right now with 4 medium-sized files open in it, and memory usage is still comfortably under 5 megs.
Re:Proton Native – React Native for the desktop
by DecayingOrganic on Wednesday May 02, 2018 @05:07PM
(#16981168)
Well, that seems a bit too much. For comparison, take a look at this example electron app that I wrote to basically check if you're online using IPC.
https://i.imgur.com/g94LOvE.png
It uses around 35MB.
Re:Proton Native – React Native for the desktop
by c-smile on Wednesday May 02, 2018 @08:55PM
(#16982465)
70MB is too much for mainly native application.
For the comparison, IDE sketch (editor with syntax highlighting) from Sciter (HTML/CSS/script engine) SDK (https://github.com/c-smile/sciter-sdk/tree/master/samples/id...) takes 43 MB.
Screenshot: https://sciter.com/wp-content/uploads/2018/05/idea-ide.png
Re:Proton Native – React Native for the desktop
by zanny on Wednesday May 02, 2018 @05:39PM
(#16981383)
Fresh instance of Kate on my desktop uses 27MB, albeit its way more than a dumb text editor. Still, twice native is still in the same order of magnitude, something most naive electron apps fail to accomplish.
Re:Proton Native – React Native for the desktop
by foota on Wednesday May 02, 2018 @05:05PM
(#16981151)
Another thread quoted 300MB baseline
Re:Proton Native – React Native for the desktop
by nautilus12 on Wednesday May 02, 2018 @04:18PM
(#16980792)
Chrome is like the elephant that comes and sits on my laptop. Would be unusable without the great suspender.
Re:Proton Native – React Native for the desktop
by techbubble on Wednesday May 02, 2018 @07:34PM
(#16982083)
I just declared Chrome bankruptcy and switched to Firefox a few weeks ago. CPU rarely goes over 10% on my 2017 MBP. With Chrome it was almost always above 50%.
Re:Proton Native – React Native for the desktop
by philliphaydon on Wednesday May 02, 2018 @09:41PM
(#16982701)
I swapped when the new FF came out. Was sick of chrome using 3–4gb of memory and bringing my computer to a grinding vault. 3 times the number of tabs in Firefox and I have 0 issues. I recommend FF now.
Re:Proton Native – React Native for the desktop
by jgalentine007 on Thursday May 03, 2018 @12:38AM
(#16983385)
I used Firefox for a couple of years for the same reason, but the new release broke my keyboard shortcuts and VimFx plugin. Now I use opera and cVim, it's even better. Much faster to start than chrome, shortcuts work, syncing works, vim works, developer tools are great, no bloated background services and square tabs!
Re:Proton Native – React Native for the desktop
by sbmthakur on Thursday May 03, 2018 @06:42AM
(#16984734)
I faced the same problem with new FF. Although not as great as Vim-Fx, saka-key does solve the problem to some extent.
Re:Proton Native – React Native for the desktop
by rawland on Friday May 04, 2018 @08:00PM
(#16999393)
Tridactyl works fine in FF. (Vim add-on)
Re:Proton Native – React Native for the desktop
by unphased on Wednesday May 02, 2018 @04:53PM
(#16981068)
I got a recent Great Suspender update that blew away my settings for the plugin. Did this happen to you too? It made me sad.
Re:Proton Native – React Native for the desktop
by nautilus12 on Friday May 04, 2018 @06:00PM
(#16998752)
Yeah that got me too. Small price, although, i'm tempted to switch to firefox after reading comments here.
Re:Proton Native – React Native for the desktop
by kingosticks on Wednesday May 02, 2018 @06:09PM
(#16981587)
How have I never heard of this!? Thank you!