Photo by Joey Csunyo on Unsplash
I want to talk about those brave JS developers who changed web-development forever.
JSON
JSON - bor...
For further actions, you may consider blocking this person and/or reporting abuse
Thanks for sharing, this post is remarkable 👊 👊
Most of the environment we know as web developers are quite recently and yet most people ignore where does it comes from and why it changes so fast.
With WASM, service workers and web components 2018, is a great time for web development.
So glad you didn't mention npm! That one has been a right mess from the start and has only recently started to learn from other package systems that solved these problems years ago. It's a shame, because with a decent package system the whole js ecosystem could be a lit further along than we currently are.
Stream based processing popularized by RXJS might become part of the standard.
Do you have a link to the proposal or a draft? I'm intrigued
here you go, github.com/tc39/proposal-observable
Sorry for the wording. It was wishful thinking. This is not going to happen anytime soon. :(
Very good post. Kudos, but you missed a few innovations that made a real radical change as well like RxJS and innovations in JavaScript runtimes.
To be fair I don't see radical changes from RxJS. Maybe I use it wrong or I miss something, but in reality I haven't need anything more than
debouncefrom reactive/stream libraries on the client-side. On the other side streams on the server-side is a real deal - you can use streams for things like Gulp, stream response from the server, for queues etc.There is also interesting story about ability to cancel request with RxJS+Redux, which I haven't tried.
What do I miss here?
Yes on the server side it brings an amazing set of functionality. Treating stuff as stream has performance advantages on certain applications. Regarding the story of cancelling promises it's not just promises any even can be cancelled. That was one of the powerful functionalities. I felt it to be extremely useful as I had some unorthodox usecases at work to implement streams in existing javascript app.
So many people are praising this. I want to start by saying thanks for the history, but the writing was Helter skelter, it didn't feel researched or thought through. When I finished reading, I felt the article was different from where it began.
Kudos for the thoughts, and thank you for explaining.
I will mostly agree with this (with small "but").
I'm doing basic fact-checking and if I'm not sure about something I will add something like "I think" or "I guess" etc. I'm trying to be intellectually honest (first of all with myself).
If you refer to the fullness of research, for sure I believe I missed other interesting things. I focused on things that I know. I also agree that it lacks some links to the sources. And I can explain why. This post took me about half a day (not exact number). I have limited time and a limited amount of energy to accomplish the post. If I will iron-out post I can lose interest and never publish it, so I choose to finish it as soon as it "good enough".
If writing blogs would be my job, I would spend more time on it. I would do more thorough research. I would ask friends to edit it for me. But as of now, this is a hobby. I'm doing it in between work, attempts to learn something new and personal time.
My intent is to share some ideas I have, to show perspective.
It is not a rewarding experience so far - I do not get much response to my posts (I get likes and followers), but not sure if people understood what I tried to say, do they agree or not, do they have a similar experience or not.
This is why it is what it is.
In addition to basic fact-checking, I also do basic grammatical check and if I use somebody's else material (code snippets, photos) I place a link to the author.
RxJS observables