It took me 30 minutes (between writing a previous post and this) to figure out how to use Desktop Embedder and run the app on the desktop. Now, desktop support is still under heavy development and require separate building steps for different OS-es, plus small additions of harnessing code to the main function. However, I even added native OS menu support in a couple of minutes.
Status-Flutter on Desktop:
There is also a Google’s project HummingBird – Flutter for Web – they try to find the best way to map rendered image onto web – either by using CSS Paint API, or WebGL or something else. At some point, Flutter apps will run in the browser, with or without WASM.
Awesome to see another implementation! Flutter and Dart make alot of sense if targeting Fuchsia. Looking forward to seeing how easy it is to integrate status-go.
The Nim+Qt approach is also interesting as we can have a tighter integration with Nimbus, smaller binaries and I suspect it would be quite performant.
It does make sense if targeting iOS/Android and Desktop first.
Qt bindings for nim (a language nobody’s using in production yet in 10 years of its existence) are literally a single issue for tracking lack of progress.
Flutter, on the other hand, in just two years, created more success stories than React-Native, grown largest community I’ve ever seen in tech in a decade and provides orders of magnitude productivity improvement for mobile dev.
Of course, it makes sense to compare Nim+Qt and Flutter, haha.
Are you supporting or disproving my opinion with those links?
There are few solo devs and indie developers, adding their scripts and couple of browser games to the list of “Companies using Nim” - 9 in total (4 with proofs, mostly IRC chat logs and HN comments "…we’re rewriting one Python script to Nim in our company).
Pretty sad picture for the 10 year old language.
Look, I have huge respect to people who push new boundaries and horizons in tech, fighting dogma and inertia, but doing that doesn’t automatically make technology good or promising or reliable. Nim’s success just didn’t happen, and I don’t know why would anyone assume it should. I hope it’ll find its niche, though.
Ok, QML doesn’t require much bindings, agree. This 3-year old tiny wrapper seems to run helloworld in QML.
Please, watch your language. You’re just attempting to degenerate the technical topic into childish bickering.
Everything I described about Flutter has nothing to do with the fact it’s made by Google. There is a reason, though, why the projects of that scale and quality are something Google sometimes makes extremely well, but correlation is not causation.
And how exactly did you correct the “falsehoods”, by showing links demonstrating that Nim in 10 years has only a few indie devs using it?
There is one argument presented that I can shed some more light on, having a single developer implement some screens isn’t really that indicative of a projects development speed or success, in Coinhero, Syng and Status we had knocked up the UI and even ported EthereumJ to Android (this is before gox or gomobile was even a thing) in a matter of days.
Infact at devcon2 I said Status was largely feature complete, and it even had unique features that are not present today.
Back then the UI worked well, and alot of things did not, we also had no QA, no UX, no management and much less coordination costs.
The software development process is balancing alot of tradeoffs, some can be seen, many cannot, it’s also just one part of a larger system. Flutter looks nice, but was only released last year. That doesn’t mean we shouldn’t assess it for future use,
Nim is pretty successful in it’s own right, it has a pretty dedicated community and there’s alot going for the language. The difference is really having a solid backing, maybe we will be it when we’re in a stronger position.
I really like the discussion, I hope we can continue it without the attitudes, in all existing & future threads.
