3 ms·
He's upset with the following: "An Angular "service" is a singleton object created by a "service factory". These service factories are functions which, in turn
by chris_wot 11y ago
He's upset with the following:
"An Angular "service" is a singleton object created by a "service factory". These service factories are functions which, in turn, are created by a "service provider". "The service providers are constructor functions". When instantiated they must contain a property called $get, which holds the service factory function."
He programs his front end in React. I'm not an expert in React in any way, but let's look at some sample code:
"use strict";
var HelloMessage = React.createClass({
displayName: "HelloMessage",
render: function render() {
return React.createElement(
"div",
null,
"Hello ",
this.props.name
);
}
});
ReactDOM.render(React.createElement(HelloMessage, { name: "John" }), mountNode);
In this code, I see what looks like a singleton object called ReactDOM, which would be an Angular service. There's a factory function "createClass" (a service factory), which is created by an object called React - which looks suspiciously like an Angular service provider.
Call me a cynic, but this rant looks like an uninformed screed, written by someone who thinks that creation patterns are only creation patterns if they are called factories, singleton factories and factory-functions (or constructor functions).
If he can't identify patterns in use in his favourite tool that are precisely the same as the ones he criticises, then I'm not sure he's as good a coder as he thinks he is. Even if he enjoys writing in Erlang.
- draw_down 11y agoI think the code you posted is much simpler, both conceptually and at the level of the code itself. We know what classes are, we know what render means. I think the requirement to express markup as a tree of function calls is inelegant (JSX is no different, just shorthand for this) and my least favorite part of React, but I'll take inelegant over WTF any day.
- k__ 11y agoYou can also express markup as a tree of objects. https://github.com/kay-is/react-from-zero/blob/master/0-object-elements.html#L20 https://github.com/kay-is/react-from-zero/blob/master/0-obje...
- chris_wot 11y agoI'm not an Angular expert, and this isn't quite the same, but seems to show the same basic principles at play: var helloWorldApp = angular.module('helloWorldApp', []); HelloWorldApp.controller('HelloWorldController', function ($scope) { $scope.displayName = "HelloMessage" }); I believe you just add a directive to add a new element. Slightly more code, but the same concepts in play. React uses an MVC framework, only it doesn't use those exact words. Seems pretty much the same to me! Note that React may well be easier to understand, but its not because it doesn't use a singleton object to access an object factory created by a provider of factories (a factory that creates factories).