NeutralinoJS Reviews

1. Thomas

   almost 5 years ago
   A very lightweight alternative to electronJS or NWJS

   I have previously created small desktop apps in electron and NW. These were functionally strong, but extremely large and had long load times. With neutralino JS I was able to create the same tools with less effort (both in creation and compilation). I was able to reduce the size of the tools from >300 MB to under 3 MB. Neutralino JS is clearly the better choice for me.

   🏁 Competitors: Electron, NW.js

   👍 Pros:    Very lightweight|Easy to use

   👎 Cons:    Documentation could be stronger|Limited functionality, at the moment

Prerender Reviews

NeutralinoJS mentions (22)

• Claude is an Electron App because we've lost native

  Https://neutralino.js.org/ But I think even there it’s possible to encounter platform-dependent bugs - starting from view issues (you know, different OS can use different browser engines) and up to those related to system APIs. - Source: Hacker News / 5 months ago

• Electrobun: Cross-platform desktop applications written in TypeScript

  So is it a yet another webview-based framework like NeutralinoJS (https://neutralino.js.org), Electrino (https://github.com/pojala/electrino)? What's their advantage apart from using Bun instead of Node? For relly lightweight cross-platform desktop apps better use a non-webview-based native framework like Qt, GTK, wxWidgets or even recently released FLTK 1.4. - Source: Hacker News / over 1 year ago

• Writing GUI apps for Windows is painful

  I've been eyeing https://neutralino.js.org/ since if I'm going to make the app render right on browsers then relying on the same code via webviews likely isn't (much) more portability effort. - Source: Hacker News / about 2 years ago

• Show HN: Pywebview 5

  We tried using pywebview for a cross-platform desktop app when it was version 3.x and some of the features were limited, especially when it came to systray interactions. Will have to try it out again. In the end, for that specific project, we ended up settling on NeutralinoJS. Wails was another big contender but due to limited GoLang resources in-house, we decided not to use it. Reference: https://neutralino.js.org/. - Source: Hacker News / over 2 years ago

• This year in Servo: over 1000 pull requests and beyond

  There's always https://neutralino.js.org/ which uses native WebView components to keep itself rather smaller than Electron. - Source: Hacker News / over 2 years ago

Prerender mentions (40)

• Help needed with Vue website and Google indexing

  What framework or service are you using to pre-render your content? Check out https://nuxt.com and https://prerender.io if you're not using something like this already. Source: about 3 years ago

• What are the challenges of creating a search engine friendly website in React?

  The best option is going to be using SSR using Next.js/Vite SSR/similar as others have mentioned. If you do want to stick to an SPA though (vanilla React + Vite/CRA), make sure your meta tags are set dynamically, and you can definitely pre-render (using prerender.io for example) as well. Source: over 3 years ago

• What are the challenges of creating a search engine friendly website in React?

  If you don't go with Next, you'll want to make sure that you're properly setting all your page titles, meta descriptions, and tags with something like react-helmet (or whatever the newer fork of it is called) and prerendering with prerender.io or something. Source: over 3 years ago

• Is there a workaround for a client side react app and search engine indexing?

  Thank you for the comment. I'll investigate prerender.io. I think we'll most likely change the architecture, but if we continued the developers recommended next.js. Source: over 3 years ago

• Is there a workaround for a client side react app and search engine indexing?

  Depending on how many pages you have, that can get expensive. You can get around the cost by implementing prerender.io as a stopgap (to start getting your pages indexed again -- this can take precious time) and then work your way towards a node instance that handles the static rendering for you. There are lots of tutorials on this, but they depend on which instance of React you're working in. Source: over 3 years ago