8 ms·
Can't we just make a proper, easy to use portable desktop application framework please? I really don't care what language is used so log as JS is avoidable (It
by alkonaut 9y ago
Can't we just make a proper, easy to use portable desktop application framework please? I really don't care what language is used so log as JS is avoidable (It can still be a compilation target so it could even be JS), and I can make a snappy desktop app that takes 10 not 100mb.
I'm not even sure which one I'm hoping for at the moment. Xamarin seems to have bet fully on mobile. Avalonia looks nice but feels like it would need some enterprise backing.
- headmelted 9y agoStandard WinForms and/or Java isn't too far off what you're describing if you're willing to install runtimes, but I know that's not what you're looking for and I see your point. The difficulty is that people used to agree (and at varying times, sue each other) over which metaphors to use. The desktop platforms are growing further apart on this front. Linux has so much work-in-progress happening at any one time that sustainable fusion is closer than a finished and implemented Wayland. Windows is still pushing a "modern" UI metaphor that no-one can stand. Apple has to my knowledge never shown any interest in what you're proposing at all. That leaves the option of creating another UI layer on top for the app to sit in, and Electron/HTML5 isn't a terrible fit for that. Maybe trying to get rolling with LLVM and emscripten to run the Electron logic is your answer, or Typescript if it helps ameliorate some of the JS qualms for you.
- egeozcan 9y agoYeah, if Electron had just one advantage, it would be that it's available and works today.
- fsloth 9y ago"The difficulty is that people used to agree (and at varying times, sue each other) over which metaphors to use" I think you hit the nail on the head. A UI common library should not provide metaphors but direct access to the renderdable elements, their layout routines, etc. A proper UI library would resemble a modern 3D game engine more by its interface. The level where UI metaphors step in would be built on top of this basic substrate. There are oh-so-many projects out there trying to use this pattern but for some reason they've not reached popularity.
- jcelerier 9y ago> Can't we just make a proper, easy to use portable desktop application framework please? Qt ticks all your marks (though the "easy" part is through QML which is a superset of JS), + mobile, (+ one day web maybe https://msorvig.github.io/qt-webassembly-examples/window_opengl/window_opengl.html https://msorvig.github.io/qt-webassembly-examples/window_ope... though that's fairly experimental).
- IshKebab 9y agoYeah unfortunately it fails at the "10 MB" bit. Hello world in QML is like 50 MB. Also you can't statically link the GPL version which is just a bit of a pain. I agree if it allowed static linking and wasn't huge it would be perfect. Even so there aren't any better alternatives, but it sucks you can't make something as small and portable as e.g. putty.exe, or depends.exe.
- jcelerier 9y agoQt is under LGPL which allows static linking: https://www.gnu.org/licenses/gpl-faq.en.html#LGPLStaticVsDynamic https://www.gnu.org/licenses/gpl-faq.en.html#LGPLStaticVsDyn... This way, you can get under 20 megabytes: https://youtu.be/mbs3-XE0HNE?t=1180 https://youtu.be/mbs3-XE0HNE?t=1180 Sadly I don't think it's possible to have at the same time "portable" (including to platforms without UIs at all, like DirectFB on linux) and small. Putty and depends.exe aren't portable at all.
- rlp 9y agoLGPL does not allow static linking. From Qt's legal page: In case of dynamic linking, it is possible, but not mandatory, to keep application source code proprietary as long as it is “work that uses the library” – typically achieved via dynamic linking of the library. In case of static linking of the library, the application itself may no longer be “work that uses the library” and thus become subject to LGPL. It is recommended to either link dynamically, or provide the application source code to the user under LGPL.
- 9y ago
- noway421 9y agoDoes the binary size matter? Memory footprint is more important. There's always PyQt which works cross platform
- Figs 9y agoYes! Plenty of us are still stuck on mediocre internet connections that have data caps. My cap at home is 5GB/month! 100MB/app is in the range of "I am not going to download it" unless I have a damned good reason to. Doubly so for updates...
- matthewmacleod 9y agoI have used PyQt. I wouldn't suggest that it's a suitable cross-platform toolkit for anything more than the most basic applications.
- jcelerier 9y agointeresting, what makes you say so ? it's been used to build apps that I wouldn't call basic : Calibre (https://ic.tweakimg.net/ext/i/1324631500.jpeg https://ic.tweakimg.net/ext/i/1324631500.jpeg) Spyder (https://github.com/spyder-ide/spyder https://github.com/spyder-ide/spyder) Orange (https://orange.biolab.si/screenshots/ https://orange.biolab.si/screenshots/) QGIS (https://live.osgeo.org/_images/qgis_style.png https://live.osgeo.org/_images/qgis_style.png) OpenShot (http://www.openshot.org/static/img/gallery/clip-overview.jpg http://www.openshot.org/static/img/gallery/clip-overview.jpg)...
- timlyo 9y agoIf we're talking Python, then I've had great experiences with Kivy. https://kivy.org/#home https://kivy.org/#home
- nicoburns 9y agoThere's some promising early stage projects in Rust world. They're all building on WebRender (firefox's new renderer), but without the DOM/JavaScript bit.
- yoodenvranx 9y ago> Can't we just make a proper, easy to use portable desktop application framework please? We should just go back to Delphi, it was/is one of the best ways of doing GUIs.
- alkonaut 9y agoIsn't delphi procedural just like e.g. Swing/AWT or Windows Forms? (Been a long time since I worked with Delphi). I think XAML/XUL and similar declarative GUIs are better.
- JustSomeNobody 9y agoI’m so over XMLish and it’s declaritiveness. So please, no, don’t wish for this.
- memsom 9y agoNo. (Caveat, last version I used was version 5 from 1999.) Delphi forms are in one of two formats. 1) Binary serialization of the form data (this is the older versions, pre 4/5) 2) A textual representation. The code for a Delphi form was pre-XML, but it looked like a set of standard markup. There were resources (Form, Button, Edit, Label - these types of control) and they were laid out in a hierarchical developer readable form in blocks. The form code was streamed to/from the file (the files were embedded as resources in the Eve, and the form was read and re-constituted at runtime as well as design time.) Borland made a massive deal about the "two way editing" one could do to the forms. The developer was able to cut and paste controls, and the controls were cut/copied as straight text, which could be pasted to notepad (for example) IIRC.
- j_s 9y agoThe usual problem is that the various cross-platform UI toolkits not only fall into the uncanny valley but also only support one programming language best (in this case, Pascal). Only the incentives of the biggest cross-platform browser vendors align in such a way that they pursue native UI effectively. Recent discussion: Why I use Object Pascal | https://news.ycombinator.com/item?id=15490345 https://news.ycombinator.com/item?id=15490345 (2017Oct:268points,233comments)
- pjmlp 9y agoAccording to the latest Windows Developer Day, Xamarin.Forms is that framework in what concerns Microsoft. As for the rest, sorry for being so blunt, but it is just not wanting to learn. We we were writing applications across multiple OS and hardware architectures for ages now. It is easy, no, as it requires actually putting some effort into a proper architecture and OS/hardware abstractions, but it is surely doable. It feels like devs now want to write apps without spending any real effort on them.
- bsaul 9y ago"It feels like devs now want to write apps without spending any real effort on them." I think what people are fed up with, is to spend effort learning the "method du jour" of putting a button on a screen and updating the view on a click. This is pretty much a solved problem, and has been since MVC was invented in the 70s (not saying it's perfect, but it does the job). So there should be an easy an portable way of doing it for decades now. QT seems to be the kind of framework, but it's C++ so i won't qualify it as "easy".
- cm2187 9y agoIt's even worse than that. It makes apps expensive and slower to develop across platforms, makes different version more complicated to maintain and keep in sync, creates more attack surface, etc. And even from a non technical point of view, there is a consistency of experience across platforms point of view. There are very good reasons to have fully cross platform apps that you develop only once. And in general, I don't think developers are being lazy by going for higher level languages like java, c# or python. Ease of use has a lot of value, particularly if the underlying problem you are trying to solve isn't simple. The last thing is forward compatibility. If I write an objective-c app, it will only be compatible with apple's platform. Say a new kind of platform appears that takes a significant market share (AR?), there is a lot of value in your app being compatible with this platform without needing even to recompile it, just because the cross platform framework you use will be ported to that platform.
- pjmlp 9y ago
- linguae 9y agoIt would be nice if GNUstep (http://www.gnustep.org/ http://www.gnustep.org/) received much more attention. GNUstep is a free software implementation of the OpenStep API (which Apple's Cocoa API is based on), and GNUstep is available for *nix and Windows. The OpenStep API has already been shown to be cross platform; back in the days when NeXT, Inc. existed, it sold an implementation of the OpenStep API and development tools for Windows NT called OPENSTEP Enterprise (see http://i.imgur.com/I7VivtO.jpg http://i.imgur.com/I7VivtO.jpg for a screenshot). After Apple bought NeXT, Apple renamed OPENSTEP Enterprise "Yellow Box for Windows" during their Rhapsody efforts. However, in 1998 Apple's business strategy shifted from maintaining NeXT's cross-platform support for OpenStep to devoting NeXT technology solely to the Mac. This is what killed OpenStep as a cross-platform development technology. GNUstep could have picked up from where Apple left off in 1998 to be a major contender in cross-platform software development. Indeed; it could have attracted former OpenStep developers who liked the cross-platform nature of the API and were stranded when Apple stopped development of Yellow Box for Windows. But for various reasons GNUstep's development and adoption has been slow, and alternative APIs such as QT and GTK ended up winning out in terms of popularity. But I don't think it's too late to promote GNUstep, especially now when a vocal minority of Mac power users are increasingly becoming discontented with the state of the Mac and are looking for high-quality alternatives.
- matthewmacleod 9y agoAs an on-and-off Mac developer, I absolutely love Cocoa as a development platform. I did look into using GNUstep as a tool to base a cross-platform version of a Mac app on, but agreed that it just never quite made it. But I'd love that kind of API to be available cross-platform.
- deleted 9y ago[deleted]
- ttd 9y agoI've had good luck so far with Xamarin.Mac + traditional WPF for macOS and Windows respectively, with a PCL containing 90% of the shared code. Xamarin.Mac doesn't seem neglected to me, and the forums are decently active for support.
- jagger27 9y agoMaybe I'm confused, by Xamarin.Mac do you mean Visual Studio for Mac?
- ttd 9y agoXamarin.Mac is the project emcompassing bindings from Cocoa (i.e. native macOS) to Mono/.NET, the interface with Xcode for building Cocoa UIs, and Visual Studio for Mac (previously called Xamarin Studio). Essentially, Xamarin.Mac allows you to build C# applications that run on macOS with native macOS user interface elements. See e.g. https://blog.xamarin.com/your-app-on-66-million-macs-c-sharp-on-mac/ https://blog.xamarin.com/your-app-on-66-million-macs-c-sharp...
- ivm 9y agoXamarin and C# are great, I will use them for the next desktop + mobile project. I was looking at this option for a long time and the acquisition by Microsoft added enough confidence in the future of the stack.
- rippsu 9y agotry Qt
- amelius 9y agoIt's GPL'ed. That means it is a no-go for a lot of people. E.g., my boss would be against it.
- jcelerier 9y agoNo, it can be used under the LGPL, which is fairly different (eg no problem for proprietary apps). Electron uses Blink which should also be covered under LGPL (eg for instance: https://chromium.googlesource.com/chromium/blink.git/+/master/Source/core/html/HTMLDocument.cpp https://chromium.googlesource.com/chromium/blink.git/+/maste...) and it's not a problem for anyone.
- mrits 9y agoIf you think JS/HTML is bad you should try any of the cross platform desktop application frameworks.
- camgunz 9y agoQt is pretty great.
- cmiles74 9y agoSwing covers almost every use case (JavaFX as well and has a more modern feel). While people like to complain about Java, it is easy to follow and gets the job done. Other languages are available on the JVM that could also leverage Swing/JavaFX, like Clojure.
- vosper 9y agoI'm not sure this is helpful (yet?), but the Red programming language seems to be working on cross-platform UI support. Original announcement is here, and macOS support was recently added. Language development seems pretty slow, though. http://www.red-lang.org/2016/03/060-red-gui-system.html?m=1 http://www.red-lang.org/2016/03/060-red-gui-system.html?m=1
- LemurMadness 9y agoThe main problem with Avalonia is that it's still in alpha. It looks like a good solution, though, so definitely something to keep an eye on if you're looking for a solution that doesn't require running a web server and render for the UI.
- WorldMaker 9y agoIt's starting to look like PWAs will be soon powerful enough for mobile and Windows cross-platform development. I'm somewhat hopeful that maybe we'll finally start to see more PWA APIs and Electron/Electron-esque desktop integration APIs converge.
- serguzest 9y agothose guys are making progress https://github.com/AvaloniaUI/Avalonia https://github.com/AvaloniaUI/Avalonia Though I wish they didn't choose xaml/wpf way which is pretty much over engineered imho. React like api would be awesome.
- Const-me 9y agoI wish they hadn’t picked GTK+. This brings huge technology stack with it, required a desktop subsystem for no reason, and is focused on the CPU rendering. They should have used something like this instead for backend: https://github.com/memononen/nanovg https://github.com/memononen/nanovg