121–130 of 169 posts
/me Quietly goes back to using Knockout and Typescript to happily pootle along building apps without worrying about routing, SPAs and other added complexity. Simplicity brings its own rewards.
> Save the global components off as global variables and just use them ... When my ActivityIndicator component mounts, it saves itself off to a global. Any code can import busy and run busy.start() and busy.stop(). What is the story that FP folks need to tell here, so that people don't do things like this?
Nothing. We know it's messy, but React doesn't really provide a better way of doing this. Context is barely mentioned in the docs, "not recommended" by the devs. Redux is incredibly verbose and overcomplicated. Passing "global" things down in props is just madness (if everything needs it). Personally I use context, or a singleton (which is just a hidden global really). It's naughty, but usually required for one or tw…
No one has ever approached that code and been confused or had issues tracking down bugs in my experience.
I agree it's ugly. I've found it triggers the same sense in a lot of developers that make them over-abstract code to achieve DRY at the expense of simplicity (this is just an observation, I don't have an opinion on if it's good or bad!).
Earlier quoted context omitted.
I haven't tried it, because the components don't look native. Buttons with text that have a shadow? What on earth is that? It looks less polished than Ionic and suffers the same problems of all Cordova-based hybrid apps: No native input controls. For me, this is a dealbreaker.
Cordova is all about plugins. You can use a native datepicker plugin for example. If you need native functionality, use a plugin. (there's probably one already there, but maybe you need to write a tiny bit of native code). I guess that's the whole point of hybrid that people don't understand - it's a hybrid, and you get to choose the best of both, making the trade offs you need to make for the best result. Not ideal…
It feels like working with raw ES6 with a small but powerful library on top. Anyone good Javascript developer can pick it up in a matter of a few hours which makes onboarding very easy.
It is still young and small when comparing it to its big brothers but you should try it anyway. It's really a joy to work with.
I keep reading about how there is no community but that isn't true at all. The Gitter chat is very active and you can get an answer there in a matter of minutes.
----
My answer to the article's conclusion:
"My team is small and doesn't have a professional web designer; I need other people's components."
- In my experience using other people's components is often the weakness in big projects. You end up spending more time customizing them to your need than it would have taken building them yourself using the project's specification. That being said, yes, you do need either a full-stack or a front-end dev. for that.
"I also hit too many stumbling blocks building out my spike, requiring hours of painful research."
- The building system is very simple and looks like the ones I do myself but bigger. You can choose between Webpack and JSPM. You can even use their very simple CLI if you are not used to front-end build systems.
"I never did succeed at getting a dialog to open, show a progress bar, and close programmatically."
- ... Really? That's the basic tutorial on their website. Was an attempt even tried?
Earlier quoted context omitted.
Speaking of evangelists...
I'm happily cleaning up react messes :) As my dads plumber friend used to say... "There's money in shit!". Fair cop. Not sure why I'm participating in a JavaScript framework internet discussion. I wish people would concentrate on standards, and apps.
I swear "React is just a library, not a framework" is the new "JavaScript is just a scripting language, not a programming language". The comments in this thread are a great example of this.
Earlier quoted context omitted.
I haven't tried it, because the components don't look native. Buttons with text that have a shadow? What on earth is that? It looks less polished than Ionic and suffers the same problems of all Cordova-based hybrid apps: No native input controls. For me, this is a dealbreaker.
Cordova is all about plugins. You can use a native datepicker plugin for example. If you need native functionality, use a plugin. (there's probably one already there, but maybe you need to write a tiny bit of native code). I guess that's the whole point of hybrid that people don't understand - it's a hybrid, and you get to choose the best of both, making the trade offs you need to make for the best result. Not ideal…
Earlier quoted context omitted.
It really isn't a template language as the term is commonly used. If you feel so strongly about the weird syntax you can write equivalent code in javascript syntax instead. return React.createElement( button, { className: "square", onClick: () => this.setState({value: 'X'}) }, this.state.value ); If you think your code is written in a template language, then the code I just wrote must also be written in a template la…
That's not a good thing. I want to write this, and have it actually be HTML : I like HTML.