F# Bloggers

Blog articles of F# Bloggers

0
comment
on 9/20/2014 5:00 PM
I recently saw a tweet from Ryan Riley linking to an article exploring F# performance and floating point processing: This blog post highlighted some perf issues (minor) in #fsharp that surprised me. http://t.co/D2Q6ZtorhW Anyone able to explain?— Ryan Riley (@panesofglass) September 18, 2014 I poked around the code and tested it a bit myself, and figured I would take up the author’s  call for feedback. Comments on the original blog are locked down, so I’ve written up my results here, instead. Initial[...]
>> Read the full article
.
0
comment
on 9/13/2014 11:18 PM
Let’s face it, @fsibot in its initial release came with a couple flaws undocumented features. One aspect that was particularly annoying was the mild Tourette’s syndrom that affected the bot; on a fairly regular basis, it would pick up the same message, and send the same answer over and over again to the brave soul that tried to engage in a constructive discussion. I wasn’t too happy about that (nobody likes spam), and, being all about the enterprise and stuff, I thought it was time to inject a couple mor[...]
>> Read the full article
.
0
comment
on 8/28/2014 8:50 PM
Today, at devLink 2014, my last session of the day is “Practical Machine Learning – Predicting Things” by Seth Juarez. In his presentation, Seth talks about machine learning and his machine learning library, numl. The session is very entertaining and I learn a lot from it. Fun fact: Seth originally called his library, Machine Learning … Continue reading →
>> Read the full article
.
0
comment
on 8/24/2014 9:35 PM
My recollection of how this all started is somewhat fuzzy at that point. I remember talking to @tomaspetricek about the recent “A pleasant round of golf” with @relentlessdev event in London. The idea of Code Golf is to write code that fits in as few characters as possible – a terrible idea in most cases, but an interesting one if you want to force your brain into unknown territory. Also, a very fun idea, with lots of possibilities. If I recall correctly, the discussion soon drifted to the conclusion that i[...]
>> Read the full article
.
0
comment
on 8/22/2014 2:25 PM
Compute the mathces Here is a simple, purely brute-force algorithm for computing the join mentioned in Part 1. Here is the entirely “CPU” implementation of the algorithm: Loop over both datasets, compare them one-by-one, if there is a match – flag it. The only thing to note is that while it’s tempting to write the […]
>> Read the full article
.
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper