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.
Based on our record, Composer should be more popular than NeutralinoJS. It has been mentiond 143 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
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 / 6 months ago
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 / 11 months ago
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 / about 1 year ago
There's always https://neutralino.js.org/ which uses native WebView components to keep itself rather smaller than Electron. - Source: Hacker News / over 1 year ago
I've been drawn to NeutralinoJS as it looks like it will do what I want, but I'm willing to hear some other recommendations and maybe tutorials on how to do the objectively simple things I've outlined above. Source: almost 2 years ago
There is also no requirement to follow the PHP-FIG standards. The best thing that is build because of those standards is Composer. The most plugins I downloaded while writing use composer. The problem is that the plugins ship with their own vendor directory. While the standard is to have one vendor directory for the whole project. This results in different packages with the same or different version of it in the... - Source: dev.to / about 1 month ago
“Extensions are now very close to being like packages; they basically look like Composer packages. It’s still open to discussion whether PIE will be part of Composer someday. It’s not decided yet, but I hope it will be,” Roman added. - Source: dev.to / about 2 months ago
Dependencies are managed by Composer (like npm, cargo, etc) for more than 10 years now. https://getcomposer.org. - Source: Hacker News / about 2 months ago
Composer and Packagist have become key tools for establishing the foundations of PHP-based applications. Packagist is essentially a directory containing PHP code out of which Composer, a PHP-dependency manager, retrieves packages. Their ease of use and exceptional features simplify the process of importing and managing own and third-party components into our PHP projects. - Source: dev.to / 3 months ago
Simplicity: Getting started is a breeze—install via Composer, define some routes, and you’re off. Scaling up? Add middleware or libs like Twig or Eloquent as needed. - Source: dev.to / 3 months ago
Electron - Build cross platform desktop apps with web technologies
jQuery - The Write Less, Do More, JavaScript Library.
NW.js - nwjs
React Native - A framework for building native apps with React
Flutter - Build beautiful native apps in record time 🚀
Babel - Babel is a compiler for writing next generation JavaScript.