11–20 of 28 posts
Blink has so much investment, and is moving so fast, that I don't think React Native's renderer can keep up meaningfully. As far as I know it doesn't support s huge number of useful CSS, like Grids, variables, transitions, multiple border styles, text-transform...
Blink has so much investment, and is moving so fast, that I don't think React Native's renderer can keep up meaningfully. As far as I know it doesn't support s huge number of useful CSS, like Grids, variables, transitions, multiple border styles, text-transform...
I googled for Blink and couldn't find what I think you might be referring to. Would you mind dropping a link to Blink?
Blink has so much investment, and is moving so fast, that I don't think React Native's renderer can keep up meaningfully. As far as I know it doesn't support s huge number of useful CSS, like Grids, variables, transitions, multiple border styles, text-transform...
I googled for Blink and couldn't find what I think you might be referring to. Would you mind dropping a link to Blink?
I don't know if React Native is technically the answer but an approach _like_ RN, like you asked OP, makes the most sense to me from a user standpoint.
From a developer standpoint, even with cross platform toolkits like RN, it _really really sucks_ managing multiple platforms. I can understand why most go for Electron or similar. We really need some better, cross platform stories for developers.
Earlier quoted context omitted.
I googled for Blink and couldn't find what I think you might be referring to. Would you mind dropping a link to Blink?
It's Google's fork of WebKit: https://en.wikipedia.org/wiki/Blink_(web_engine)
is this possible with proton-native?
It can be in theory, but in practice managing native widgets across all major platforms is such a mammoth project that it's almost impossible. People have been trying for decades, rarely with success.
Users, except the tech savvy one, will not notice if you do a nice job. (hard to miss with UI framework like fabric, semanticUI, etc..)
If you want a small application that start fast and/or use system look and feel. A react-native approach (like https://proton-native.js.org/) will be better.
If you plan to customize/brand your apps and the app will run for a long time, it doesn't really matter. The downside is that it will take more memory.
Also, v8, constantly improve, reduce memory usage and optimize javascript performance. Soon it will be easier to run faster code with webassembly. It's even possible now to compile your typescript code with AssemblyScript, or do it the hard way with C, C++ or Rust. It's only a matter of time before the performance between the two will be reduce.
As for the problem mention about the whole browser ship with every apps. Maybe we will see a solution similar to adobe air in the future or a way to strip down blink based on the app requirements. Technically a browser is just a standardized drawing library, like flutter uses skia, Qt it's own or GTK uses cairo.