Ask HN: Why React developers don't want to use UI builder?

Re:Ask HN: Why React developers don't want to use UI builder? by midnightmonster on Wednesday May 04, 2016 @04:46PM (#11631618)

Marketplaces classically suffer from the chicken and egg problem. No point in distributing via marketplace if no one is buying there, no point in trying to buy there if no one is distributing (this is true even if "buying" is free).

For open-source stuff, npm is pretty much the One True Way to distribute JS libraries these days. If I'm looking for a component, I'll expect to find it by google and install it from npm.

(As far as Structor itself, I'm not at all clear on what it's supposed to do for me. The article is very long and covers too much ground. I don't see myself as likely to use a UI builder in any case, though. My current React work is all with bespoke UI controls, look of which is given to me by a designer.)

[ Parent | on HN ]

Re:Ask HN: Why React developers don't want to use UI builder? by ipselon on Wednesday May 04, 2016 @05:11PM (#11631857)

You are totally right that every one used to workflow: google, npm, reading docs, trying to setup new component into project.

The goal of Structor is to give a simpler way - open project, and if you want component try to install it through the market for 10 seconds. The problem - to have big amount of such components. For this I made convenient mechanism for publishing components generator.

BTW, generator can generate only the glue code (which you writing every time after you installed npm) and has the ability to install dependencies from npm automatically.

[ Parent | on HN ]