Common Lisp vs Electron: What are the differences?
Common Lisp and Electron are primarily classified as "Languages" and "Cross-Platform Desktop Development" tools respectively.
"Flexibility" is the top reason why over 13 developers like Common Lisp, while over 50 developers mention "Easy to make rich cross platform desktop applications" as the leading cause for choosing Electron.
Electron is an open source tool with 74.9K GitHub stars and 9.81K GitHub forks. Here's a link to Electron's open source repository on GitHub.
Slack, Intuit, and InVisionApp are some of the popular companies that use Electron, whereas Common Lisp is used by Real Softservice, NG Informática, and Platform Project. Electron has a broader approval, being mentioned in 221 company stacks & 374 developers stacks; compared to Common Lisp, which is listed in 5 company stacks and 3 developer stacks.
What is Common Lisp?
What is Electron?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
The Slack desktop app was originally written us the MacGap framework, which used Apple’s WebView to host web content inside of a native app frame. As this approach continued to present product limitations, Slack decided to migrate the desktop app to Electron. Electron is a platform that combines the rendering engine from Chromium and the Node.js runtime and module system. The desktop app is written as a modern ES6 + async/await React application.
For the desktop app, Slack takes a hybrid approach, wherein some of the assets ship as part of the app, but most of their assets and code are loaded remotely.
Slack's new desktop application was launched for macOS. It was built using Electron for a faster, frameless look with a host of background improvements for a superior Slack experience. Instead of adopting a complete-in-box approach taken by other apps, Slack prefers a hybrid approach where some of the assets are loaded as part of the app, while others are made available remotely. Slack's original desktop app was written using the MacGap v1 framework using WebView to host web content within the native app frame. But it was difficult to upgrade with new features only available to Apple's WKWebView and moving to this view called for a total application rewrite.
Electron brings together Chromium's rendering engine with the Node.js runtime and module system. The new desktop app is now based on an ES6 + async/await React application is currently being moved gradually to TypeScript. Electron functions on Chromium's multi-process model, with each Slack team signed into a separate process and memory space. It also helps prevent remote content to directly access desktop features using a feature called WebView Element which creates a fresh Chromium renderer process and assigns rendering of content for its hosting renderer. Additional security can be ensured by preventing Node.js modules from leaking into the API surface and watching out for APIs with file paths. Communication between processes on Electron is carried out via electron-remote, a pared-down, zippy version of Electron's remote module, which makes implementing the web apps UI much easier.
Our application began as an HTML5 browser game, however we decided to leverage certain native parts of desktop applications by wrapping our client code into Electron. This also allowed us to not have to worry about compatibility across all the various browsers.
Our Web Applications are served on our Desktops by Electron. This allows us to have native apps running on our Workstations without having too many Browser Tabs open at the same time.
Electron is the current preferred method to convert games made in the Game Pencil Editor for desktop support.
Implement a web-service using your favorite tools but sell a desktop application for oblivious windows users.