this is one aspect where theoretical background does help
i have spent a lot of time on the other side of computer science theory, i.e., algorithms and complexity... only recently discovered the type theory, category theory etc... and it's all super fascinating
otherwise it's hard to make intuition precise
@vinayakpathak I'd also recommend some basic study of logic
nothing too advanced, but the basics do help when reading about type theory
on the other side of computer science theory,
there's more... it's a fractal rabbit hole
one random example: models of computation, applied to concurrent and distributed computation
i agree :)
I wish people appreciated it more
i feel that broadly though cs theory can be divided into the Turing style areas and the Church style areas
Turing style being algorithms, running time, complexity, etc... Church style being more logic, type theory, that sort of stuff
not sure what kinds of models of concurrent and distributed computations you are talking about... i remember seeing some in my grad school days, but they were mostly Turing style
@tpolecat thanks will check it out
I mean, I don't want to open a whole new rabbit hole to dive into, type theory is big enough. But things like pi calculus, join calculus, model and temporal logic, and so on
I don't want to open a whole new rabbit hole to dive into
yeah makes sense :)
Hi, someone could tell me, why this give a true result?
anyone familiar with sbt? I am trying to figure out if I can access a file hosted not on my local machine but like somewhere on S3 instead? Trying to host our scalafmt conf to be working with Jenkins and our build process
well seems that this solved my problem:
s matches """\d+"""
scalafmtConfig in ThisBuild := file("~/.scalafmt.conf") <- Something like that but instead of a local file it could pull it off http somewhere?
With scala is there a huge drive to move all methods to functions (in objects)?
functional programming is just we want to make sure functions are "pure" as in without side effects
side effects should be encapsulated in some sort of Monads
at least that's what I understand
methods create side effects
as long as the methods is not mutative, it should be not creating side effects
methods don't always create side effects, but often times you do see methods side effecting in say, very OOP code like in Java, e.g. myInstance.setSomething(something)
With scala is there a huge drive to move all methods to functions