React Desktop – React UI Components for OS X El Capitan and Windows 10
1–10 of 74 posts
Re: React Desktop – React UI Components for OS X El Capitan and Windows 10
#2Anyway, I would love to see these come in native form like reactive-native.
Re: React Desktop – React UI Components for OS X El Capitan and Windows 10
#3The components look nice but they're not really native like I had initially thought. Are these necessarily better or different than existing styles that reproduce these components? Anyway, I would love to see these come in native form like reactive-native.
Re: React Desktop – React UI Components for OS X El Capitan and Windows 10
#4Why does this exist? Is creating desktop programs out of HTML code really a good idea?
Re: React Desktop – React UI Components for OS X El Capitan and Windows 10
#5Please forgive the simple question, but... Why does this exist? Is creating desktop programs out of HTML code really a good idea?
Re: React Desktop – React UI Components for OS X El Capitan and Windows 10
#6Please forgive the simple question, but... Why does this exist? Is creating desktop programs out of HTML code really a good idea?
Re: React Desktop – React UI Components for OS X El Capitan and Windows 10
#7Re: React Desktop – React UI Components for OS X El Capitan and Windows 10
#8The components look nice but they're not really native like I had initially thought. Are these necessarily better or different than existing styles that reproduce these components? Anyway, I would love to see these come in native form like reactive-native.
Do you mean react-native, or is there a reactive-native I'm unaware of?
Re: React Desktop – React UI Components for OS X El Capitan and Windows 10
#9Please forgive the simple question, but... Why does this exist? Is creating desktop programs out of HTML code really a good idea?
Re: React Desktop – React UI Components for OS X El Capitan and Windows 10
#10Please forgive the simple question, but... Why does this exist? Is creating desktop programs out of HTML code really a good idea?
Because NodeJS is popular and desktop apps were getting small and efficient so we crammed a 30MB Chrome runtime in there.
This is my completely biased and highly selective history of events ;)