ClojureDart VS gallery

> "ClojureDart is production-ready: you can ship applications right now.

Source: https://github.com/Tensegritics/ClojureDart

See a live demo here: https://www.youtube.com/watch?v=dqBeGpuedf0

ClojureDart is very similar to ClojureScript, which the GP is already comfortable with.

Ah, and there is also a new version of Clojure in active development - ClojureDart. It is a port of Clojure language to Dart with the primary goal of using Flutter framework and getting a native mobile and desktop UI.

There is a port of the Clojure language to Dart with Flutter support: https://github.com/Tensegritics/ClojureDart

Now https://github.com/Tensegritics/ClojureDart exist to build GUI with flutter.

There are ways, but it is generally a lot of work, for example there is ClojureDart https://github.com/Tensegritics/ClojureDart . Though unusually that sort of thing is normal for Clojure, because it is a hosted language (Clojure -> JVM, ClojureScript -> JS, etc).

Something to checkout for mobile and desktop is: https://github.com/Tensegritics/ClojureDart

Basically, you take a programming language and make it work on a platform that meant to be programmed using a different PL. Clojure is hosted by design - it's not Java, but can be used to program for JVM. It ain't Javascript, but can be used to target nodejs and browser; not an [official] CLR language, but you can write .Net programs. You can use Clojure to make Flutter apps with ClojureDart. You can integrate Python into Clojure with libpython-clj. Or write Clojure to target Erlang/OTP; or Rust; or R; There's even a clojure-like language for Lua - Fennel.

There's something about Clojure people like so much, they want it to work atop any platform.

https://github.com/Tensegritics/ClojureDart

https://github.com/clj-python/libpython-clj

https://github.com/clojerl/clojerl

https://github.com/clojure-rs/ClojureRS

https://github.com/scicloj/clojisr

https://fennel-lang.org

I was pessimistic about flutter 4 years ago but rechecked it recently (learning right now) and IMO it's really good user/developer proposition these days. They resolved most of issues on mobile devices and desktops - only web version still off but once wasmGC is ready (hopefully this year) probably things will improve.

Best way for developer elevator pitch just download few flutter apps and see how you like the experience:

1. wonderous - https://flutter.gskinner.com/wonderous/

2. flutterflow (low code + gui editor for flutter) - https://https://flutterflow.io/

3. appflowy (notion alternative) - https://appflowy.io/

4. flutter gallery (official flutter kitchen sink) -

Android (Google Play Store, .apk) - https://play.google.com/store/apps/details?id=io.flutter.dem...

web (gallery.flutter.dev) - https://gallery.flutter.dev/

macOS (.zip) - https://github.com/flutter/gallery/releases/latest

5. official material 3.0 demo - https://flutter.github.io/samples/web/material_3_demo/#/

I recommend to checkout and play with material 3.0 demo (just keep in mind this is web version will have even better when using native compiled version on mobile or desktop):

https://flutter.github.io/samples/web/material_3_demo/#/

4) Try web flutter gallery to see numerous app samples (more complex) and widgets

https://gallery.flutter.dev/#/

again even better to download mobile or desktop version that there is in app store:

play store: https://play.google.com/store/apps/details?id=io.flutter.dem...

macos dmg (.zip): https://github.com/flutter/gallery/releases/latest

I tried both macos flutter gallery and on iOS and surpassingly is pretty good these days and smooth and feel native - even text selection works these days, moving cursor with long press on keyboard space etc. Occasionally was more difficult to dismiss keyboard on iOS and back/next mouse keys or touchpad gestures didn't work on macOS flutter gallery. But overall I'm quite satisfied and surprised comparing how it looked 4 years ago.

I remember the first time when I looked at the Flutter Gallery and was surprised at how things felt just broken in a web browser, for example: https://gallery.flutter.dev (I think it was the Reply example in particular)

Ctrl + click or middle mouse button didn't work on links, right click didn't work, selecting and copying text didn't work, inspect element didn't work (due to how the technology is built), even attempting to zoom the page did nothing.

This article does ring true both because of that experience, as well as some of the SPA implementations I've seen even with more conventional technologies.

Google Docs. Figma. Any Flutter app like https://gallery.flutter.dev/. Short answer, they're really not handling accessibility.

Even when you did that, scrolling was completely wrong. The web simply doesn’t expose primitives from which you can build native-feel scrolling, and the best you can manage on precise touchpads (that is, all laptops now) will normally feel terrible, and lack things like inertia which are rather important. https://gallery.flutter.dev/, for example, scrolls less than half as fast as it should, and lacks inertia. (… and renders text in the wrong font, and doesn’t do links at all where it obviously should, and uses scrollbars that behave all wrong quite apart from being overlay which my native aren’t, and get typing emoji wrong, and… and… seriously, it’s just a litany of awfulness.)

Oh wow. I had thought the claim that they were not producing any semantic web elements was almost certainly exaggerated. That said, for the number of things that are on https://gallery.flutter.dev/#/reply, there are a surprisingly low number of elements. Wow.

example: https://gallery.flutter.dev (and Flutter Gallery on the playstore)

You could just need to clear your cache, but I suspect might have something going on because of how you're loading your theme. Not sure about having two runapp functions. I would suggest inspecting gallery.flutter.dev and then implementing a splash screen the way they have, as you will get the benefit of having a slash while flutter is being loaded, vs a splash screen that won't start until after, which imho, defeats the purpose.