171–180 of 208 posts
How does this compare to nativescript-vue? https://nativescript-vue.org/
It doesn't touch on the Vue integration, since that's relatively new.
> Vue Native transpiles to React Native. Why would you not use react native directly then? I don't get it
This is ironic, given that a lot of people advocating for vue on the web talk about how it's better because it doesn't involve all that complicated transpilation.
Earlier quoted context omitted.
> I re-wrote my entire teaching syllabus for my programming course to use Vue instead of React, simply because it's much better to maintain Vue apps rather than React apps after 6 months, which is the most important value add for me in any framework. Why do you find it harder to maintain React apps after 6 months?
One of the main reasons - JSX. Contrary to popular belief, JSX is all cool until you're in a situation where you need to maintain the app you wrote. I know React can be written without JSX as well, but frustratingly most documents/resources online are all examples with JSX. And then, this: https://twitter.com/thomasfuchs/status/810885087214637057
Earlier quoted context omitted.
Gibbon: - https://medium.com/netflix-techblog/crafting-a-high-performa... - https://medium.com/netflix-techblog/building-the-new-netflix... - https://www.youtube.com/watch?v=eNC0mRYGWgc Cobalt: https://www.cobalt.dev/
I find it funny that youtube made a cool new tech specifically to render UI on tv's and yet it works like shit on any tv I encountered.
It's based on react-vue[1] and It is internally using react-native. 1. https://github.com/SmallComfort/react-vue Why but Why.
I honestly do not understand how did a large part of the software engineering community get to this point of idiocy. Is this due to the principle of getting to the market first and quick prototypes? I don’t see a quick way back.
Earlier quoted context omitted.
They do it simply because it's the most cost effective solution overall.
Typical capitalism outcome. Cheapest to produce AND worst quality. In this case by bad performance and unneeded cellphone battery drain. These products will be dominated by superior options eventually.
It's based on react-vue[1] and It is internally using react-native. 1. https://github.com/SmallComfort/react-vue Why but Why.
Because, it solves a problem. I'm sorry, but, outside of the "let's use react for everything" bubble, people believe in different ideologies and use different frameworks to accomplish similar tasks. One of them is using Vue for web applications, and now thanks to this new project, the same Vue developers can also make use of Vue to build their mobile apps. What it uses under the hood isn't really a concern for me as…
Earlier quoted context omitted.
Xaml and Wpf? Qt? I am honestly asking you, have you worked with React before? XAML has a learning curve of 2 years and more to get to expert level. I developed with it for more or less 5 years and i still have nightmares. Qt and the others are all imperative layout inflaters. React was a revolution, maybe the first cross platform paradigm that actually made sense. A learning curve that doesn't span more than a day.…
I love writing React code and it is easy to get up to speed there. I abhor the mix of HTML/CSS for UI design. I'd rather code UIs in Actionscript. The web browser as an abstraction for general use UIs is just not ideal. XAML might be a company induced mess underneath but my point is that you don't have to be XAML expert to make nice interfaces. I made CRUD apps on WPF and rarely did I have to touch XAML directly. I h…
- how is it supposed to adapt to different resolutions?
- is an inner absolute component allowed to escape its container?
- how does it layer with other components?
The CSS required to position an element at an absolute location must take all of these into consideration, and I'm not sure how much better a native toolkit can make it.
Earlier quoted context omitted.
Frankly I find your view pretty offputting. I’m not really that into the idea of JS-as-a-platform, but it obviously emerged because it fulfilled certain requirements that weren’t covered elsewhere. The “way back” from this is for people like yourself to stop dismissing others’ work as “idiocy” and start building better solutions to these problems as you see them.
> I’m not really that into the idea of JS-as-a-platform, but it obviously emerged because it fulfilled certain requirements that weren’t covered elsewhere. Maybe they weren't covered for a reason? The ability to have your web team churn out lowest common denominator bloated JS based mobile/desktop apps was not a real requirement, more like a wish of some. Now businesses do that just because they can.
Come on, the requirement has always been there. It is "Shit out that underbudgeted project in half the promised time". Those small frameworks where you can hire a cheap front-end guy and have him manage the entire project alone or in a small team are perfect to fill that niche.