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.
Xamarin Evolve just concluded. And there no best time to write this post. And for the fact I am not writing anything new or even anything related to announcements that happened there. I am writing this because recently I got chance to work with android using Java. And experience was not at all good. And reason is not so surprisingly Java. I am will not explain anything instead I just copy paste three code snippets.
F# is wonderful language. And luckily or unluckily I do Web Programming (now a days mostly that). So, it is always a preference to use it, wherever possible. But even in 2014 end it is still pain in a**. I did make templates for Servicestack and I will continue to support that. But when it comes to real projects they go far beyond templates. I recently experimenting on something and obviously I am gonna use templates created by me.
NOTE- As per today I am neither married nor committed. And for that case never married and never committed. :P Whoever is following my progress must be knowing my love for F#. Neither me nor F# knows exact time and date when that happen. But now it is like if few days I have to pass without writing few lines to(in) F# then it felt like I have left software engineering for good.
This may be nastiest thing I have done with deployment after a long time. There is no problem with making it work. But deployment on azure is a serious issue. And luckily I completed that. Yes, there is a luck involved. If you read my previous entry for running Nancy and SignalR together. Then most of the things are same only. Use Servicestack template to create project. Remove global.asax & global.
- OLDER POSTS
- page 1 of 4