4 ms·
And AJAX :) I'm also really hoping that the current crop of JS programmers learn event-driven / reactive style programming, and for that, RX is probably the be
by djtriptych 10y ago
And AJAX :)
I'm also really hoping that the current crop of JS programmers learn event-driven / reactive style programming, and for that, RX is probably the best JS library out.
- zghst 10y agoI spent a lot of the earlier parts of my life hating MS, however later after working at a .NET shop and with the late developments at the company, my love for MS is becoming near-infinite. Reactive is definitely the way to go
- mmgutz 10y agoIt's strange but I went the other way. I started hating MS because of working in .NET. Basically, if something wasn't blessed by MS, it wasn't used. There were open source MVC projects but since MS only blessed ASP.NET forms back then, you couldn't convince managers to use MVC. Same with IoC. Same with ORMs I do like the new Microsoft. VS.Code is hands down the best all-around editor right now. TypeScript is awesome sauce.
- bobwaycott 10y agoI started here, too. First production app was an early C# ASP.NET OSHA safety management and training platform for Mohawk carpets, built from the ground up back in 2007-08. Experienced all these headaches. Next major project was Python-based. Never went back to .NET.
- NicoJuicy 10y agoAsp.net forms was a monster. Asp.net Mvc was not
- bobwaycott 10y agoThe MVC variety was barely getting started when I was working at the time.
- shouldbworking 10y agoVSCode and Typescript are stellar. In the case of Typescript, possibly industry-changing long term. However, the .NET stack still suffers greatly from what you mentioned. The Microsoft world is like the Oracle world, you either use their stuff for everything or never touch it. I'm confident that .NET core will change this when it's mature enough, but that's still ~2 years away.
- KurtMueller 10y ago> In the case of Typescript, possibly industry-changing long term. I feel that way about a related Microsoft product, F#. It's too bad that it doesn't get the same amount of love as Typescript. I think it's more powerful yet just as easy to use in almost every way - I never knew how powerful or expressive algebraic data types could be until I used F#.
- NicoJuicy 10y agoToo bad nobody gives an example. Check out http://fsharp.github.io/FSharp.Data/ http://fsharp.github.io/FSharp.Data/ for an example why f# is 'powerful'
- mattferderer 10y agoRepeating myself a bit in this thread. If you love F#, try checking out Fable &/or Reason. Fable compiles F# to JavaScript and Reason is Facebook's attempt at OCaml to JavaScript. F# !== Ocaml but F# == Ocaml
- daxfohl 10y agoI've gone, and continue to go, both ways simultaneously. They put a lot of effort into creating awesome experiences to bring developers on board. They also run a business that caters to clients who need "enterprisey" stuff backwards compatible with COBOL.NET or whatever and try to push that along with the good stuff. So it goes. I can't complain too much.
- scalatohaskell 10y ago> There were open source MVC projects but since MS only blessed ASP.NET forms back then, you couldn't convince managers to use MVC. Same with IoC. Same with ORMs but that's not really Microsoft's fault
- deleted 10y ago[deleted]
- nathan_f77 10y agoMan, there's so many tools and styles to learn and evaluate. I'm still relatively new to React and React Native, and have enjoyed writing some apps with Redux. It took me a while to understand the need for redux-thunk, and now I'm about to get started with redux-saga [1]. I'm totally unfamiliar with RxJS, but some of the concepts sound familiar. Do I need to learn and use RxJS if I'm already using redux and redux-saga? I found this SO answer [2], and this post [3], which compares redux-observable and redux-saga. This guide [4] looks pretty good, too. [1] https://github.com/redux-saga/redux-saga https://github.com/redux-saga/redux-saga [2] http://stackoverflow.com/a/40027778/304706 http://stackoverflow.com/a/40027778/304706 [3] https://hackmd.io/s/H1xLHUQ8e https://hackmd.io/s/H1xLHUQ8e [4] https://gist.github.com/staltz/868e7e9bc2a7b8c1f754 https://gist.github.com/staltz/868e7e9bc2a7b8c1f754 EDIT: OK wow, as soon as you get to the "double click" stream diagram (in link [4]), it all starts to make sense. This is pretty amazing. EDIT 2: The example on http://reactivex.io/ http://reactivex.io/ is also good. I didn't realize it was available for so many languages: Java, .Net, JS, Swift. This sounds like something I need to learn. EDIT 3: This is the best programming guide I have ever read ([4]). It starts with a real problem, then goes on to show how you would solve it in RxJS in a rudimentary and familiar way. Then it expands on and successively simplifies that solution, to show how you would solve it in the idiomatic way. It's really the perfect way to learn these concepts. > A metastream for responses looks confusing, and doesn't seem to help us at all. We just want a simple stream of responses, where each emitted value is a JSON object, not a 'Promise' of a JSON object. Say hi to Mr. Flatmap: a version of map() that "flattens" a metastream, by emitting on the "trunk" stream everything that will be emitted on "branch" streams. Flatmap is not a "fix" and metastreams are not a bug, these are really the tools for dealing with asynchronous responses in Rx.
- bpizzi 10y agoYou might also like this: https://github.com/Day8/re-frame https://github.com/Day8/re-frame It's not js/es6 (re-frame is a react-based redux-like framework for clojurescript) but the author does a good job at explaining how reactive programming go well with functionnal programming and immutability.
- Stoids 10y ago