My biggest turn off with learning to use electron was wiring everything up.
Maybe it’s my fault for thinking things would be as easy as Winform and Xaml, but this sounds promising.
Electron Fiddle: Get started with Electron
91–100 of 104 posts
Re: Electron Fiddle: Get started with Electron
#92Earlier quoted context omitted.
>like right mouse clicks didn't do anything but bring up the built in browser menus. You should try this in slack again...
That UX decision has nothing to do w/ Electron.
If someone brings up a single example they should ensure it aligns to their criticisms, as a rule.
Re: Electron Fiddle: Get started with Electron
#93Earlier quoted context omitted.
You should probably disclose that you're the primary developer. The name seems like a terrible idea, as it's so generic and unsearchable. It will be hard to find help with things, even if it becomes more widely used. The peer-to-peer stuff seems interesting, but the documentation is incomplete. Elsewhere the documentation says "It’s built from scratch, 1000 lines of code", but it's way more than 1000 lines (and it wo…
Electron, Node, and Bun are also pretty generic and unsearchable. As to the rest of your comment, the p2p component is less than 1000 lines of code. And, as I said it hasn't had an official release yet (due on the 15th).
But socket already has a well-established meaning in software. I think even if you succeed with that name, it will be at the unnecessary cost of making network programming more difficult for everyone. It's easy to choose a unique name (even "SocketEngine" might do), and now is the time to do it.
Oh, that component is Whether or not it's officially released, you are already promoting it as an alternative to much more established options, so you should expect people to compare on the same terms.
Re: Electron Fiddle: Get started with Electron
#94Electron Fiddle is cool and the sort of thing that helps Electron maintain its lead over other frameworks, but it doesn't take you all the way through a project to the point of distributing your app. It helps you figure out how to make an app that starts up and does stuff, but, then you're on your own again. That's often where the pain really starts, as the most common tools are mostly thin wrappers that just map JSON to command line flags for the native toolchains on each platform. Or for Electron you end up being pointed at a lot of not fully maintained tools, custom update servers etc. Abstraction and convenience are minimal, cross-packaging painful or outright impossible. This is a problem not only for Electron; Flutter, Tauri, Jetpack Compose for Desktop, JavaFX/Swing etc all suffer the same issues.
There's another way to get started: grab Conveyor [1] (disclosure: my company makes it) and run
conveyor generate electron com.example.my-project
It works for real production-grade apps; there's an example of packaging GitHub Desktop [2] which covers more advanced stuff like registering URL handlers (deep linking), Windows notification callbacks and so on. Also works for Flutter [3] and native apps.
Finally, for people asking "Why Electron", the answers are pretty simple: Google invests a ton of money in Chrome, and the multi-vendor nature of HTML makes it largely immune to rewrites and platform churn of the sort that affects Windows, Linux, macOS, iOS and Android. It's got its problems but stability+investment isn't one of them, which is why there are so many developers who know it.
[1] https://hydraulic.software/
[2] https://hydraulic.software/blog/8-packaging-electron-apps.ht...
Re: Electron Fiddle: Get started with Electron
#95Re: Electron Fiddle: Get started with Electron
#96Earlier quoted context omitted.
Electron, Node, and Bun are also pretty generic and unsearchable. As to the rest of your comment, the p2p component is less than 1000 lines of code. And, as I said it hasn't had an official release yet (due on the 15th).
But socket already has a well-established meaning in software. I think even if you succeed with that name, it will be at the unnecessary cost of making network programming more difficult for everyone. It's easy to choose a unique name (even "SocketEngine" might do), and now is the time to do it. Oh, that component is Whether or not it's officially released, you are already promoting it as an alternative to much more…
make sense to me, node/bun/electron are common words but not so common in software, socket is a well known software term.
I still have no idea how the "socket" magic works, need to be convinced, till then I will stay with flutter for now.
Re: Electron Fiddle: Get started with Electron
#97Earlier quoted context omitted.
golang is also by google the same as dart though
Yes, but unlike Dart, Go has at least modest mainstream adoption.
I had the same thought until one day I tried to use it to do some quick Dart coding, turns out it is very easy comparing to other languages, and it has sound null safety too, all syntax are pretty much the same as C, I like it and I hope its popularity will increase.
Re: Electron Fiddle: Get started with Electron
#98Earlier quoted context omitted.
May I add https://flet.dev Uses python & flutter. And https://wails.io Uses Go.
just played with flet, don't know why it mentions flutter in its home page as I saw nowhere flutter|dart is involved. a helloworld python single binary is 28MB with pyinstaller, c libraries are shared and it is not a static executable. it uses gstreamer underneath? not sure what that means, do I need gstreamer preinstalled on the platforms? this seems like yet another Python based GUI framework to me(e.g. a new Tkint…
The UI is built with Flutter but you don't write any Dart. They ship flutter wheel in python and they plan to support other languages like "Go, C# and others are coming next"[0]
Re: Electron Fiddle: Get started with Electron
#99Earlier quoted context omitted.
just played with flet, don't know why it mentions flutter in its home page as I saw nowhere flutter|dart is involved. a helloworld python single binary is 28MB with pyinstaller, c libraries are shared and it is not a static executable. it uses gstreamer underneath? not sure what that means, do I need gstreamer preinstalled on the platforms? this seems like yet another Python based GUI framework to me(e.g. a new Tkint…
The UI is built with Flutter but you don't write any Dart. They ship flutter wheel in python and they plan to support other languages like "Go, C# and others are coming next"[0] [0] https://flet.dev/roadmap
so this is basically a flutter that does not use Dart? this is something major then.
Re: Electron Fiddle: Get started with Electron
#100Earlier quoted context omitted.
Electron, Node, and Bun are also pretty generic and unsearchable. As to the rest of your comment, the p2p component is less than 1000 lines of code. And, as I said it hasn't had an official release yet (due on the 15th).
But socket already has a well-established meaning in software. I think even if you succeed with that name, it will be at the unnecessary cost of making network programming more difficult for everyone. It's easy to choose a unique name (even "SocketEngine" might do), and now is the time to do it. Oh, that component is Whether or not it's officially released, you are already promoting it as an alternative to much more…
We've set expectations very clearly in that it's pre-release status with the intent to compete with Electron and similar projects. Node is an extremely common word in software for example, but it's not a problem because people generally apply context to their searches.