11–20 of 126 posts
Things I have to say: * Background noise in your video is annoying. * Why are you showing your face? I'd rather see your code bigger. * Using require instead of module imports shows me that this product is going to have trouble keeping pace with FB, Babel, ECMA speeds. * I'm not in love with adding another IDE * hello http://getqwikly.com/ all over again Sorry, but I'm not betting on this horse.
Will I need to submit my React Native libraries to a new registry? Or are you working with something like http://js.coach (formerly react.parts)?
I'm very excited to try this out. We've built one (very simple) React Native application so far and felt like the build chain could use some improvements. Do you plan on supporting imports instead of require?
What exactly constitutes the Deco package registry? Will I need to submit my React Native libraries to a new registry? Or are you working with something like http://js.coach (formerly react.parts)?
Things I have to say: * Background noise in your video is annoying. * Why are you showing your face? I'd rather see your code bigger. * Using require instead of module imports shows me that this product is going to have trouble keeping pace with FB, Babel, ECMA speeds. * I'm not in love with adding another IDE * hello http://getqwikly.com/ all over again Sorry, but I'm not betting on this horse.
Things I have to say: * Background noise in your video is annoying. * Why are you showing your face? I'd rather see your code bigger. * Using require instead of module imports shows me that this product is going to have trouble keeping pace with FB, Babel, ECMA speeds. * I'm not in love with adding another IDE * hello http://getqwikly.com/ all over again Sorry, but I'm not betting on this horse.
What does that mean?
Things I have to say: * Background noise in your video is annoying. * Why are you showing your face? I'd rather see your code bigger. * Using require instead of module imports shows me that this product is going to have trouble keeping pace with FB, Babel, ECMA speeds. * I'm not in love with adding another IDE * hello http://getqwikly.com/ all over again Sorry, but I'm not betting on this horse.
Not the best feedback but not sure it's downvote-worthy
Things I have to say: * Background noise in your video is annoying. * Why are you showing your face? I'd rather see your code bigger. * Using require instead of module imports shows me that this product is going to have trouble keeping pace with FB, Babel, ECMA speeds. * I'm not in love with adding another IDE * hello http://getqwikly.com/ all over again Sorry, but I'm not betting on this horse.
This product may die, however I believe competition and the fire to get what you want is more valuable than king making through bad reviews (whether intentional or unintentional). Tbh, Im not going to look at the product because Im more interested in terminal editors at the moment. But criticism should be used to enhamce a product, not degrade the blood sweat and tears that went into it
What exactly constitutes the Deco package registry? Will I need to submit my React Native libraries to a new registry? Or are you working with something like http://js.coach (formerly react.parts)?
For the beta, we currently have our own registry, but we are looking into ways to integrate with others.