u/SneakyRead
-
25points
- 19points
-
19points
The comment macro loves repl driven development (youtube.com)
-
21points
What's that function? clojure.core/juxt (youtube.com)
-
2points
A Simple Event Sourcing and DDD Example (github.com)
-
5points
An Easy Event Sourcing Example (github.com)
-
6points
Getting Started With ChatOps - Pluralsight Course (pluralsight.com)
-
8points
How changing my commit messages made me more productive (sneakycode.net)
-
0points
This War Of Mine #1 - Watch me play by Roblol (youtube.com)
-
12points
Getting wooed by F# (sneakycode.net)
-
0points
Modeling with Aggregates (sneakycode.net)
-
0points
Getting Started With Chat Ops (sneakycode.net)
-
6points
Getting Started With Chat Ops (sneakycode.net)
-
5points
Getting Started With Chat Ops (sneakycode.net)
SneakyRead
SneakyRead
I have found that I needed Stack overflow much less after moving to Clojure.
SneakyRead
Agreed. It is better suited to more complex domains. but that is just because it has some operational complexity. If you are building a blog then you prolly don't need it
SneakyRead
For those interested my getting started with chatops course went live on pluralsight last month. It focuses on building a culture of chatops within your team.
SneakyRead
To give some credit back to c# I did the following
- Put all the enums on one line, even though this is not convention
- Auto initialized the lists (available in C# 6)
This brought the line count for c# down to 55 vs 19 for f#. I then figured you can write everything on one line and that a word/character count might be a better metric. C# had 160 words and 1063 characters. F# 82 Words and 457 Characters. There is still a significant difference.
I also feel the need to say that I still love c# and I think it is a great language. This post was less about c# being long winded and more about f# being really compact.
SneakyRead
Fair enough
SneakyRead
Yes I have most definitely noticed the lack of tooling, this is however not the languages fault but I agree that it can make or break a language(especially when coming from c# and all the glorious tools). Like the post said I just scratched the surface. There are still many things that I need to explore before I will drop c# for f#. I am still not sure if this will ever happen. But I am sure that going through this process will make me a better programmer, regardless of what I end up using.
SneakyRead
Please elaborate
SneakyRead
Thanks much appreciated :D
SneakyRead
looks great
SneakyRead
Thanks
Thanks for watching and appreciate the feedback