4 ms·

I skimmed it but didn’t see, do they say why they didn’t use Compose for Desktop? Seems strange not to use the UI library being developed at the same company.

by teg4n_ 3y ago

AbuAssar 3y ago
because Compose for Desktop wasn't available yet when they started fleet development
NoahKAndrews 3y ago
From the article: "When we started working on Fleet, however, Jetpack Compose didn’t exist, and thus Noria was born." On the one hand, it seems like a significant waste of resources to duplicate efforts between the two projects. On the other, I wonder if Noria has any desktop-centric advantages over the mobile-oriented legacy of Compose.
- tadfisher 3y ago
  It doesn't at a base; both render via Skia and have completely bespoke widget systems, not tied to AWT/Swing or the native platform. They could implement the Fleet widget system on top of Compose if they wanted to invest in the effort. Personally, having worked with multiplatform Compose, I very much appreciate it over the plain "widget objects with callbacks" approach.
webprofusion 3y ago
They're reasoning is Compose wasn't available, surely then the next logical step was to either work on Compose or eventually port to Compose? Not, "ah well let's just have two competing frameworks".
- solardev 3y ago
  As a customer, I'm really excited for Jetbrains to take on experimental research projects. I love their IDEs, but they definitely have that old crusty feel, like old enterprise Windows apps and not in a good way (slow and ugly). Yeah in the short term it's not great to have two similar homegrown frameworks. In the long term though maybe it gives their apps more options to choose from, or at least different pros and cons they can try to merge together later. Either way, it's a great step forward than having to rely on Java or Oracle directly. Of course the web dev in me wishes they built a similar stack from Typescript instead (to compete with Electron and React Native) but I don't blame them for not doing that.

I skimmed it but didn’t see, do they say why they didn’t use Compose for Desktop? Seems strange not to use the UI library being developed at the same company.

by teg4n_ 3y ago

I skimmed it but didn’t see, do they say why they didn’t use Compose for Desktop? Seems strange not to use the UI library being developed at the same company.

AbuAssar 3y ago

because Compose for Desktop wasn't available yet when they started fleet development

NoahKAndrews 3y ago

From the article: "When we started working on Fleet, however, Jetpack Compose didn’t exist, and thus Noria was born." On the one hand, it seems like a significant waste of resources to duplicate efforts between the two projects. On the other, I wonder if Noria has any desktop-centric advantages over the mobile-oriented legacy of Compose.

tadfisher 3y ago
It doesn't at a base; both render via Skia and have completely bespoke widget systems, not tied to AWT/Swing or the native platform. They could implement the Fleet widget system on top of Compose if they wanted to invest in the effort. Personally, having worked with multiplatform Compose, I very much appreciate it over the plain "widget objects with callbacks" approach.

webprofusion 3y ago

They're reasoning is Compose wasn't available, surely then the next logical step was to either work on Compose or eventually port to Compose? Not, "ah well let's just have two competing frameworks".

solardev 3y ago
As a customer, I'm really excited for Jetbrains to take on experimental research projects. I love their IDEs, but they definitely have that old crusty feel, like old enterprise Windows apps and not in a good way (slow and ugly). Yeah in the short term it's not great to have two similar homegrown frameworks. In the long term though maybe it gives their apps more options to choose from, or at least different pros and cons they can try to merge together later. Either way, it's a great step forward than having to rely on Java or Oracle directly. Of course the web dev in me wishes they built a similar stack from Typescript instead (to compete with Electron and React Native) but I don't blame them for not doing that.