rephrasing
This commit is contained in:
parent
e9630b0b5c
commit
9a8b877074
|
@ -110,25 +110,29 @@ of documentation in the comments).
|
|||
|
||||
{{< img class="stickers" src="/images/config_length.png" >}}
|
||||
|
||||
So far I don't fully understand it yet at the time of writing, but I do
|
||||
understand it a hell of a lot better than when I prodoced most of those 300
|
||||
lines.
|
||||
I don't fully understand it yet at the time of writing, but I do understand it
|
||||
a hell of a lot better than when I produced most of those 300 lines.
|
||||
|
||||
The greatest thing about XMonad is simultaneously the thing that kept me away
|
||||
from it: it's written and configured in bloody Haskell. Thus there is barely a
|
||||
separation configuration and source code. The only difference there _really_ is,
|
||||
is the filename. Once you understand a bit of Haskell (no small task if you're
|
||||
used to imperative languages) adding and integrating your own features is really
|
||||
easy.
|
||||
easy. And then they are _properly_ integrated. Sort of like how DWM works, only
|
||||
with proper documentation and support. Part of me wants to see if I can figure
|
||||
out a way to package my XMonad build as a single binary to be able to chuck it
|
||||
onto systems without putting much thought into it.
|
||||
|
||||
Weird thing with Haskell I'm noticing so far is that I'm slowly but surely
|
||||
managing to dig up old concepts that I tried to implement in imperative
|
||||
languages, but couldn't due to their nature. Things like pattern matching and
|
||||
maps are quite intuitive to me. It's just that the syntax takes a _lot_ of
|
||||
getting used to.
|
||||
maps are quite intuitive to me. It's just that Haskell's syntax takes a _lot_ of
|
||||
getting used to. In the mean time, I guess that my experience with POSIX Shell
|
||||
bridged the gap between my knowledge of Go and C#; and Haskell.
|
||||
|
||||
I highly recommend giving it a shot if you're willing to bash your head against
|
||||
the Haskell wall for a while before understanding how your window manager works.
|
||||
I highly recommend giving XMonad a shot if you're willing to bash your head
|
||||
against the Haskell wall for a while before understanding how your window
|
||||
manager works.
|
||||
|
||||
Looking back I find it quite funny to see how I went from not being able to get
|
||||
i3 to do what I wanted it too and giving up; to barely being able to write or
|
||||
|
|
Loading…
Reference in a new issue