It seems that in Haskell you have to learn several languages rather than just one, you have to see the program, the program written at the type level, the program written using tacit style, the program using the different type classes... Haskell the terminology is completely alien from all other languages and often deliberately misleading like return for wrapping into a monad instead of wrap, join instead of flatten, bind for >>=. Lets not add that names like semigroup, magma, monad, monoid, cartesian closed categories, kleisi arrow, profunctor, mean very little until you learn them. I have an idea of naming Haskell things by their "type/code" like afa for return/liftM0, aifafi for map/liftA, aiufafifu for zipWith/liftA2, =<< would be amiami, $ would be aiai.
Yeah, sorry for the sound. In order to record the screen and merge audio from microphone and the game I fed both audio streams through a mixer. It seems like the game engine's CPU usage sometimes took priority over the mixer, so the mixer started messing up the audio.
Haskell has to compete with Scala(too complex), swift, Julia, Rust, Ocaml, reasonml, Python, Clojure, Racket, Eff language. If Haskell moves to the Jvm, Python byte code, web assembly, hmm
We need a good Haskell ide that shows data flowing through your functions, can easily apply rewriting rules to code so you can see the various different ways that code can look like, we also need automatic ways to rewrite your program so that monads and extra arguments are automatically threaded through your program. Haskell also needs a solver to help you code sort of like Agra and ide is. Also haskell should merge with hose languages. Another thing is Haskell should come with template haskell macros that can do trace rewriting so that people can visualize Haskell code easily.
This is the best explanation of the effects system ever. I was trying to explain it to my colleagues and this is the talk they need ! Thx you you ROCK!
ZIO is slow like a snail, trashes the GC by generating a ton of garbage objects for even the simplest computations, and has a ton of pointer redirections that bust the cache. Keep your (mutable) Actors, you are going to get 3x performance.
At first I thought this cli feature would be great for our very large cli system. We are seriously considering converting all our TCL code to Scala/Java. But now I don’t think so. We should use Maven and target all our Scala and Java code to native binary files and run each file with a simple ./xyz -arg1 -arg2 … Shouldn’t we be able to do this without any shell scripting?
This video could have been so much better if it had focused on topics that everyone could relate to. I had to think hard about the last time I had to program a memoize operator, and I probably never have. I don't even know what a memoize operator is. Now I'm forced to learn about memoize and operators just to follow along? There are so many other interesting topics and problems that could have been the backdrop of this talk, ones that people actually have to solve without all the quantum physics operatot jargon. I don't understand why the Scala community, by and large, is so cerebral. Sorry for the rant, but if everyone wonders about Scala's decline, that's a big chunk of the problem. Meager 1.1k views after 1 year speaks for itself.
I am really rigorously trying to stay away from the value-type dichotomy. So at around 14:00, I would say "Vec N is a dependent type because it depends on members of other types, in this case natural numbers which are members of type Nat". I think that presenting value-type dichotomy is the single biggest roadblock when it comes to practitioners understanding dependently type languages.
And it talks about it. The runtime system of effects system has more features that loom is offering. I also see loom as not bringing values to Effect System usage. The loom can be exploited in the runtime implementation of the effect system.
I thought the factorial problem would check for huge enough numbers so people cheating with an arbitrary large integer data type would fail due to inefficiency. Note that: H> (\k -> product [1..k] `mod` 10 :: Integer) <$> [0..] [1,1,2,6,4,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0..]
I only hate how bad is the caption in broken French. I need to translate it back to English to guess the intented meaning. I usually do not have this problem on other YT channels. An example: The French phrase "calculs de compilateur basés sur la pile que je connais" is probably meant to refer to the "the stack-based compiler computation that I know", while it actually means "compiler computation based on the stack that I know". Like if the guys knows a precise stack and he based his computation on it ? In French as in English. the definite article "the" changes everything, and it looks likes the model misinterpreted the expression "the stack-based x" as meaning the same thing as "x that is based on the stack" instead of "x that is based on a stack".
getting following error, what can i do ? Description: Parameter 0 of constructor in com.example.demo.JobController required a bean of type 'org.jobrunr.scheduling.JobScheduler' that could not be found.
Half of the screen is dedicated to a white background and the "Haskell Love conference" branding. Really? Who was the genius who decided that only one-third of the available space should be enough for the code section in a presentation about competitive programming?
Thank you for this great keynote, and you've described and summarized perfectly the pathway (by chance and experimentation) I've followed this past two years :)
At 8:55, you said that the compiler didn't freak out when using an IsLabel instance and an ambiguous reference to a field name, but GHC 9.4.2 complains about an ambiguous reference when I define such an instance.
from the recent experience with some of these libraries i am finding DL4J more useful as compared to other as well as more functional. DJL has great document but still makes it very difficult to follow if you are working on very different data source. or having complex structure etc.
