Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Proton Native – React Native for the desktop

proton-native.js.org

Post reply on HN
Print view View original

51–60 of 295 posts

Re: Proton Native – React Native for the desktop

#51

Post by drawkbox »

mstade wrote: post #21
whowouldathunk wrote: post #17

Earlier quoted context omitted.

> and now we're making traditional UI dev like web It's been like that on Windows since 2006 with XAML. In fact, if you squint at typical JSX, it looks like XAML. Disclosure: I work at Microsoft.

Or MXML, which most certainly was influenced if not entirely derived from XAML. Everything old is new again!

Yeah the Silverlight vs Flex days of 2006ish really inspired this quite a bit.

Today Xamarin does all this pretty well cross platform, desktop and mobile for UWP/Mac and iOS/Android.

Re: Proton Native – React Native for the desktop

#52

Post by foobarandgrill »

dilap wrote: post #49

Sort of tangential, but does anyone know of a good React Native app? Everything I've tried would clearly have been a better product if they'd just done native development. Like, you're sacrificing product quality for development ease.

Instagram uses react native, I believe

Re: Proton Native – React Native for the desktop

#53

Post by a13n »

dilap wrote: post #49

Sort of tangential, but does anyone know of a good React Native app? Everything I've tried would clearly have been a better product if they'd just done native development. Like, you're sacrificing product quality for development ease.

You might recognize a few on this list: http://facebook.github.io/react-native/showcase.html

Re: Proton Native – React Native for the desktop

#54

Post by woolvalley »

matchbok wrote: post #39
vintagedave wrote: post #35

> You can create a GUI using something like Qt, but the code to make it is messy and unorganized. Having made a very large GUI myself, it gets very cumbersome to manage all of that. Haven't we moved past writing UIs in code about twenty years ago? I see your code samples, and all they look like is an improved version of the code UI creation we had in OWL, MFC, and other UI frameworks on other platforms. Starting abou…

NIBs in macOS/iOS are horrible for development and code review. Using a UI to build UI is slow and clunky. There is no "moving past" it. That's a bad way to develop stuff. We don't do it with HTML, do we? No.

I think that is a uniquely iOS thing since they insist on using computer generated IDs to link objects together, while %100 human editable UI formats like HTML or Android's UI XML formats don't do that.

It's the same issue that project.pbxproj has in Xcode.

Re: Proton Native – React Native for the desktop

#56

Post by discreteevent »

kusti8 wrote: post #22
mstade wrote: post #4

> It is not only shorter, it is also easier to read and to edit, and can easily utilize the power of the state. Easier to read and edit is obviously subjective, but shorter is not and that front page is just straight up lying. The Qt example is most definitely shorter. What am I missing?

Hey. I'm the author. It's hard to find a simple example that everyone understands but can show capabilities. If you're used to Qt then you're going to like Qt better, but I mainly developed this for people who want to use React. You are obviously free to use whatever you want. But if you have any suggestions let me know!

I think the 'easier to read' is unfair considering that you didn't use QML fur the Qt example. For me QML is easier to read than JSX (and quantitatively it is less verbose)

Re: Proton Native – React Native for the desktop

#57

Post by enkiie »

dilap wrote: post #49

Sort of tangential, but does anyone know of a good React Native app? Everything I've tried would clearly have been a better product if they'd just done native development. Like, you're sacrificing product quality for development ease.

Have you heard of Facebook?

Re: Proton Native – React Native for the desktop

#58

Post by mstade »

tomtheelder wrote: post #32
mstade wrote: post #20

Earlier quoted context omitted.

No, you can’t “skip” them. If you skip them, the code is broken. The lines may well be noise, and arguably that’s even worse, but you certainly can’t skip them – counting or otherwise.

You can skip them if you want by various means, and you can also not put them on their own line. You don't even have to use JSX, which is what is taking up most of the space. A shortened, yet still totally readable (if you are used to not using JSX) version that is shorter in LOC than the Qt example might look like: import React, { Component, createElement as e } from 'react'; import { render, Window, App, Button } f…

This seems like as much of a non sequitur as "skipping" syntactic elements. The comparison is clearly syntactic, and thus factually incorrect – the second example is in fact longer than the first.

Sure, if you swap in another example that is in fact shorter, then it'd not longer be an incorrect statement. Maybe I am indeed being silly, but it seems getting the hook-line-sinker arguments as right as possible is a worthwhile goal, particularly when at least one of them can be objectively verified.

If by "shorter" you mean "less complex" than stop saying "shorter" and start saying "less complex" instead – just as you say they aren't the same thing. It'd mostly be redundant I guess, given "easier to read" and "easier to edit" implies "less complex", but at least it'd be harder to immediately refute.

Re: Proton Native – React Native for the desktop

#59

Post by kusti8 »

mstade wrote: post #43
kusti8 wrote: post #22

Earlier quoted context omitted.

Hey. I'm the author. It's hard to find a simple example that everyone understands but can show capabilities. If you're used to Qt then you're going to like Qt better, but I mainly developed this for people who want to use React. You are obviously free to use whatever you want. But if you have any suggestions let me know!

I have zero experience with Qt, but I'm pretty sure I can follow along with the examples anyway. (I do have experience with React, JS, and Python.) It seems to me you're making a syntax comparison and using shorter as an argument for Proton Native, yet the example is obviously not shorter so it's factually incorrect. My suggestion is you don't use shorter as an argument. Aside from being incorrect, it's probably not…

Yeah I'll reword that. My bad.

Re: Proton Native – React Native for the desktop

#60

Post by carloscr »

I like react on the web, but sometimes I find it cumbersome all that sending props down and passing functions to update global state. When I'm almost done with an app and then I decide that it will be nicer to open a modal window to ask the user 2 or 3 parameters is when I miss the most the desktop paradigm of just call a method that opens a small window and returns an object with the collected data
Post reply on HN