let’s start with the right question …
why so much people opt for node.js and react?
and I am talking about CEOs, CTOs, developers, programmers, even SEO consultants are suggesting node and react, so what could go wrong?
I’d say a lot … going with the trend is ok in fashion, it is for looking good, but in technology it is about working good, nobody sees what is under the hood, nobody ask about either, so the question changes …
what are the most reliable tools?
reliability starts with stability, performance, transparency and ends with maintenance … on a scale from 0 to 10, in the above order the score for node and react is 5 – 7 – 0 – 0
WHAT?
why people use it then? … and so, now we come to the moment of truth …
in order to talk about the same values, all I’m saying is comparing the values to a standard, well proven and stable PHP/JS-Ajax website – on first sight, node.js provides advantages, fast deployment, giant api repo (NMS), same language for front-end and backend, one guy can write the whole thing – that then is called full-stack developer – no need for specialists anymore, CTOs and even small company owners love that idea, hiring a cheap guy to do it all instead of 3 expensive engineers …
wow, that’s is the deal of the century … maybe at first sight, and then not so much anymore
what it really does is helping the copy-past culture to enter the application programming market, they need an authentication model, install the api and use it, same for any other part, what comes out is an application nobody knows how it really works because it is build on independent blocks which in most cases the copy-past engineer has no clew about what each of them really does …
of course, the application is up in no time and for very little money, it is the take for immediatists who do not care about later, the degradation comes with the same speed, the full-stack guy is gone, the app needs adaption and nobody can understand the code, nobody knows how it works, an intensive and expensive analysis is necessary just to add a new product category, the initial being-cheaper advantage just became a soap bubble – blubbb and gone, other technical caveats will add immediately and turn the whole application into a wreck which can not be recovered and a new investment is required
and it just get’s worse when you decided initially for REACT …
react is also java script and creates an interesting new reality treating the rendered document in a different way, it can be updated easily in parts, so that attends exactly the need of its maker’s operation mode, facebook adds new blocks by priority or commercial interest to the active running feed, so that algorithm decides to change the user’s feed instantly while he’s rolling down, with posts of similar content he just clicked, react can do that quite easily – that sounds interesting, and again, facilitates the task for inexperienced programmers, so again we are at the fast-deployment issue
also here we need to make the right questions, facebook has millions of simultaneous users, do you have that too? facebook has millions of adds which need to be synced with millions of user interests on the fly, do you have that too? facebook is a reckless money greedy operation and do not cares about quality of content, are you working that way too? and last but not least, we all now that facebook, whether in a pc browser or any of it’s apps is sluggish, constantly failing, so why is that? if the maker can not make it work you think you can?
and here we come where react and node.js met … their endpoint is JAVA SCRIPT …
js runs in the browser, nothing what runs on it can be considered save, and also, everything what runs on it depends on hardware, operation system, software version what is provided by the end user … means whatever crap it is you have to eat it … that means whatever powerful top end server you have invested in, it miserably fails because it doesn’t matter .. your app runs in the browser
and the real snap is, JS has that poor debug.log which also runs in the browser, but has no application log on the server, offers no way to debug seriously a problem, more intense, you depend on user input to identify a problem … so that explains why facebook and similar mídias are unstable, they have no clew what happens, the build a new feature and observe the result, reaction rate goes down – rollback, click-through rate goes down – rollback … absurd? totally, they do not even know if their new idea was good or just had a small implementation error, they are in a total frustration rush and there is no way out
so you will be facing unsolvable problems in a very short period of time
is that what you are looking for? then go for it an make your own experience, if you survive we’ll see us in a couple of month when you are looking for serious and approved PHP/JS development
until then, that the luck is with you …
Leave a Reply