How does the client component use data from the server component (eg. Comp.server.vue / Comp.client.vue)? When I use the useState or useAsyncData API to define a key, I find that this key is global. When reusing the component, there is a data sharing problem.
While I was able to recreate UI quickly with Vuetify (playground code YVHhuA) the Radix version definitely helps us deliver more polished UX/a11y. Nice demo
I've just started using Quasar, and my first experience is really good. The documentation is probably the best I've ever seen for any framework, and the speed at which you can start deploying to mobile with Capacitor or other modules mentioned in the video is impressive. I'm looking for a tool/framework that will be good for developing for web, mobile, and touch screen devices used in marine environments. Unfortunately, I've run into a lot of issues due to browser versions and JavaScript compatibility on these devices, requiring a lot of polyfills for JavaScript. I've had to create a lot of bespoke components, and I'm wondering how difficult it will be to edit the ones made in Quasar to add new functionality..
You know what? I am a regular viewer of your RU-vid Channel. I have seen all your videos and your content qualities are very good. I learned lots of things from you. Your channel has great quality contents but still it is not delivering its right audiences due to SEO problems. You should focus on your SEO so that You can get a big fanbase. Thanks
going to be honest, the amount of times (7+) he says “but you don’t have to use it” when referring the Rust side of things, really says a thousand words. not great when they make it sound like Rust is the ugly thing you don’t want to touch.
Let me know if I get this correctly... You want me to decouple architecture injecting a smart hosting layer for serverless functions with integrated message queue? It looks nice of the presentation slides, but I feel like Shopify has it all covered and in custom scenarios we can either introduce additional actions in UI (e.g. suggest subscription to mailing list during initial onboarding) or rely on cheap cron jobs to act upon "events" put into any data store we like. I would be rather cautious with spinning up a load of functions. The simple scenario shown on the video gets easily much more complex once we acknowledge that user may find a notifications opt-out toggle in profile settings right after signing up, or remove account he had set up using wrong email address... but hey, maybe ultra-durable happy-path is all your customers need.
Nobody wants to admit that no team want's to hire gpt-proompters as real coders, but it makes MS stock go up, so who cares right? Terrible presentation based on "AI-down-your-throat" agenda. People need to read documentation, apply examples and fail in order to learn and grow. Amaaaaizing, I know.
