This post is part of F# Advent calender. Thanks Sergey Tihon for arranging this and giving me chance.
JavaScript is a different kind of beast when it comes to a programming language. It is easy to learn but too hard to master. I still get nightmares of interview questions about JavaScript code. One needs to select the correct output for a given code snippet.
For all those reasons, I always go for languages transpile to JavaScript.
This blog is part of FSAdvent F# calendar 2019.
Jupyter has been around for ages. The data scientist’s one of the favorite tools. Kind of best thing to write words, equations and result in the best possible manner. F# is and was a poster child for DotNet to do Data Science. I never liked the poster child part but still, it is what it is. I ’ll come to that little later on.
I am writing after a long time for F#. And this would be a little bit controversial post. Take it with a pinch of salt.
Recently I got a call from some company who wants me to do some job in F#, for its client. The client took my interview and told that its client wants to do some work in F#. Things were going smoothly until the interviewer asked me that I should be writing F# code following standard and design patterns.
This article is part of FSAdvent 2016 calendar.
This my second post of 2016. Sadly not much of writing this year. So, I need to cover up by this little longish post. So, grab your favorite coffee / tea before getting started.
There is one wonderful coincidence here that both post of 2016 is based on Epic Mahabharata. If anyone interested in poem like things do check out my another post.
This post is part of F# Advent calender. Thanks Sergey Tihon for arranging this and giving me chance.
First I like to clarify that this was not my original choice for FSAdvent calender. I was going to write long post about web, AKKA, api and real time system. My current working area. But this time’s calender entries are reaching new level and dimension. And recent post from Evelina Gabasova is kind of reason behind change.
Reactive word is not new nowadays. If you want your library to get limelight, use reactive word in the name any way possible and it will definitely get initial attention. Reactive word is appropriate for things that follows reactive manifesto. That is true for now. And there are many variant of libraries on server and client to fulfil this.
Let’s start from the start of web.
We were having old web were we used to do post event of page.
Whoever worked with Microsoft Shop knows about nuget. It is package manager for anything and everything related to .Net. And it is getting better and better with versions coming in. But again it is nowhere near maturity needed to work with projects having many small projects. Things get cranky soon.
Now, there is better option as per my opinion called Paket. Very easy to get started. And so damn reliable. Couple of more command to learn but I guess it is ok.
