I understand a web-application can be accessed via a browser (from mobile/desktop).. but where is it hosted? For example, could a web-application hosted on a PC access the USB hardware peripherals connected to it, or would a pure Flutter Desktop application be required? Haven't seen any Flutter Desktop examples that talk to hardware. Also, a hello-world Augmented-Reality app using Flutter (ar_flutter_plugin / arcore ) would be great! Not sure with how much precision an image be overlayed onto the camera screen, but I'd like to make android app that can find components from a circuit board! For example, if you have a sheet of paper with a grid of squares, say 50x50.. if A4 is said/entered, could AR use a fiducial on the paper to calculate precisely how far into the grid it needs to place an appropriately scaled marker (scaling it based on the the angle and how close the camera is to the sheet). BTW, I understand has the Flutter framework uses state-management as its philosophy (ex. Fred Grott), but what do you think of Flet (Python for flutter)? On the "Flutter Clutter" blog they mention some cool projects featured in the 2022 "Flutter Puzzle Hack" contest.. any idea if they're going to do another?
This is awesome. I'm glad I found this talk. I was looking to kick the WASM (and embedded) tires after the Swift 6.0 release, but I bumped into a whole different Swift Wasm based on 5.10. This is what I was looking for. That sent me down a rabbit hole of confusion. Great talk! Thanks! Also, thank you for making the example publicly available.
Money makes the world go around. *What about Flutter-web-stripe support.* Without solving this gap, there is no way to hop into the Flutter-web development train, sorry.
Holy moly! You compiled a shell environment AND nodejs to webassembly to run in the browser!? That's unbelievable! Does the Nodejs here support napi extensions? Do you have a link to the playground? Do you have a link to the sources? This is _exactly_ what I need - I'd love to build on top of it
I'd really love to know how to set up this project from scratch and successfuly get the wasm working with @_extern and, also getting the hot reloading working
For hot reloading there are a few live server and preview VS Code extensions for your choosing, and the readme file in the example repo also provides a command to run a bog-standard Python HTTP server. Use your favorite command-line file watcher that will invoke the build command when any of the source files change. The summary is that there's no special magic for hot reloading, everything is pluggable and you can use whatever hot reloading tools you prefer.
@@kevinl.9657 the excel demo is a bit more complicated than any other extism demo. I’ll share the code though! in the meantime, I’d try out extism using JavaScript SDK, which will make the Excel part more familiar since it uses JS too
Mayby more code or demo to show me the improve or fution, such as kotlin in web how to use with react, you know that even rust wasm provide the react and yum to build web app.
Why use React for mobile if native is standard?. Why use Kotlin if C++ is more fast?. Why use C++ if assembly is more fast. Why use assembly if binary is the natural machine language?.
Every single time I hear Flutter pitch speech stuffed with benchmarks putting Flutter in a spotlight, I swear, every single time I immediately follow one of the example app links and end up with a janky app with terrible UX. Oh, let me try this text input field - keyboard appears and app yeets you to another dimension and text input is nowhere to be seen. I'm talking about Material 3 app mentioned on the slides. I love Dart lang, I'd really love using it for web development, but this whole "Flutter for web" narrative is just one big lie.
Too much magic going on here. I wonder how does recovery actually works, specially for time sensitive workloads or random internal inputs: - Your WASM program dies, so it needs to be resurrected on another node. - How many events need to be replayed on the cloned WASM program to get to the state the program was when it crashed? - How long does it all take? - What happens if the program was running for days, months or years before crashing? won't you have a long down time until it resumes somewhere else? - What if the running state of the crashed program involved calculations using time or random data (auto generated keys) as sources and those did not interact with the host, but were only internal to the WASM program memory? is the WASM running memory being replicated or snapshoted? that seems expensive BTW. Very interesting how that could be done thought. I do not think the app running on Golem can be completely oblivious to the constraints the platform imposes: apps that might reply differently to the same inputs depending on randomly generated data or the wall clock will not be reproducible, so they should be negated those somehow, or they should asume reality does not really exist for them... If the platform is going to intercept random source generator interactions or private key generation to replay and fake it later, that is a security issue, for instance. You cannot fully isolate apps from reality. And in reality, shit happens. Another thing, you are NOT deleting databases, you are just hidding them from app developers. Databases will be used to store the events that will have to be replayed as needed. Same goes for Kubernetes or network serialization, that will still exist in a way or another on the Golem platform level. or below It might be a good simplification and might reduce duplication and increase overall productivity, but someone will still have to write and maintain databases, schedulers and network serializations.
That's....really boring! It's just another iteration of "the thing we could already do, but in the browser." Jeff even says, "there are no VMs", and then has to clarify, "just WASM"(a VM). Then they share the screens and do the CRDT thing and he goes, "it's like we both SSH'd into a shared server, except there's no server!" But there IS a server - it's the one that's exposed by the service worker! Huh, yeah, it's almost as if we should go back and fix the UX around the actual OS instead of doing whatever this is.
@@kyleaustin2728 have an seo landing page and redirect to the web app dashboard. People really over optimize for this problem imo. But youre welcome to have a different perspective :)
@@kyleaustin2728 just add a landing page with SEO and then put redirect to the webapp. Google Drive doesn't have SEO indexing for their apps. Why would any other webapp need SEO indexing?
Closures closures closures. Please resolve issue 798 in AssemblyScript! Everything else seems very exciting, but it's completely useless without closures because rewrites from JS/TS are too unwieldy without this ubiquitous core feature.
Really cool BUT if you are starting from scratch and want to take inspiration from stuff like smalltalk, why not listen to Alen Kay and not try to repeat the same 50 years old Unix design?
Thanks! Yes, there is plenty we could leave behind. However, I've noticed that without grounding in something familiar, you can make something too "out there" to be practical/compatible/understandable. Also, instead of Unix/Linux, I'm pulling more from Plan 9, which had great refinements of Unix ideas that have not totally made their way outside of that research context. I think the real trick, though, is taking this familiar paradigm and pushing into being something that is actually totally new without you realizing. We'll see how it plays out. Hope you'll be following along!
This is really cool stuff. I am having a tiny bit of trouble seeing the use case but I think thats just because its early. The tech here though is epic.
Agreed! It's on the roadmap. The tricky bit is that the current version of WASI is synchronous, so the only way to integrate it with WANIX or anything that isn't running in the same worker is to use SharedArrayBuffer, which adds complexity and extra security constraints. That said I have a prototype of the mechanisms needed, so it's possible even before WASI 0.3 (I think) introduces async. Would love people with motivated use cases to help us prioritize it though.
