91–100 of 117 posts
I wish there was some way to speed up the videos.
document.getElementsByTagName('video')[0].playbackRate = 1.2;
Earlier quoted context omitted.
Here's a look at the folder structure we're using for our app: https://i.imgur.com/wc7DyOA.png /actions: Flux action creators /components: These are all the JSX React components (the presentation layer) - so there are subfolders like "pages", "controls", etc. /reducers: These are Redux reducers - they're the logic that handles all of the application state /services: This is what your question was really about. We use…
I've been hesitant of Fetch() because of the lack of timeout; has anyone been able to successfully get around this issue?
Earlier quoted context omitted.
I've been hesitant of Fetch() because of the lack of timeout; has anyone been able to successfully get around this issue?
Yeah, this is an important question. I don't have answer for you and neither do the people in charge of the fetch API. It's an issue with promises not being cancelable. There's probably a reasonable argument that promises just aren't that great because you can only resolve or reject. Personally I don't see a huge problem with either resolving or rejecting with a message about the cause of the result. Others see it di…
Rxjs provides the observable data type. The extensions are functional reactive operators. There are operators used to retry, throttle, filter, debounce, etc.
Angular2's http module is already based on Rxjs observables for this exact reason.
Really can't decide to go ahead with an Angular approach (2.0) or use React. I know React is only for the view layer so what are people using with React to do stuff like api calls?
I don't know what to say. I'm deeply humbled by all the kind comments in here. Thank you all so much, truly.
I don't know what to say. I'm deeply humbled by all the kind comments in here. Thank you all so much, truly.
Honest noob question, what's with all the hype about React? Edit: Awesome replies, thank you!
From my point of view, React brings two important ideas to web app development: 1. The virtual DOM. When I'm writing jQuery-based code, I have to write both a component template and code that updates the DOM in response to input; when I'm writing code for a virtual DOM, the component template is sufficient to update the DOM and I don't have to write that extra code, so there are fewer chances for bugs to creep in. 2.…
Honest noob question, what's with all the hype about React? Edit: Awesome replies, thank you!
From my point of view, React brings two important ideas to web app development: 1. The virtual DOM. When I'm writing jQuery-based code, I have to write both a component template and code that updates the DOM in response to input; when I'm writing code for a virtual DOM, the component template is sufficient to update the DOM and I don't have to write that extra code, so there are fewer chances for bugs to creep in. 2.…
Also data-binding brings its own myriad of problems that older programmers will know about from the days of desktop programming.
And 2 just sounds like a violation of the rule we've all learnt not to mix presentation and code.
So they're not reasons why React is interesting.
Earlier quoted context omitted.
From my point of view, React brings two important ideas to web app development: 1. The virtual DOM. When I'm writing jQuery-based code, I have to write both a component template and code that updates the DOM in response to input; when I'm writing code for a virtual DOM, the component template is sufficient to update the DOM and I don't have to write that extra code, so there are fewer chances for bugs to creep in. 2.…
Just a note paraphrasing a Medium post that I encountered that extends point 2: it's a lot more robust to work with a framework that essentially puts HTML into Javascript rather than many alternatives, which essentially do the reverse. Javascript is a lot more complex than HTML, and yet most of the alternative JS frameworks attempt to compress some version of its logic into templating.
Earlier quoted context omitted.
Just a note paraphrasing a Medium post that I encountered that extends point 2: it's a lot more robust to work with a framework that essentially puts HTML into Javascript rather than many alternatives, which essentially do the reverse. Javascript is a lot more complex than HTML, and yet most of the alternative JS frameworks attempt to compress some version of its logic into templating.
So we should throw away decades of practical experience in all the other platforms that this is a bad idea because some blog post said so?