4 ms·
The next protocol is DNS! :) It is a bit tricky but I have the working parser for the header. Looking into how I could parse qname with that octet thing going o
by StreamBright 6y ago
The next protocol is DNS! :) It is a bit tricky but I have the working parser for the header. Looking into how I could parse qname with that octet thing going on.
https://github.com/n0hup/elafi/blob/master/apps/dnscache/lib/dnscache/server.ex#L27 https://github.com/n0hup/elafi/blob/master/apps/dnscache/lib...
It will be running on raspberry nodes (kind of replacing Pihole).
- imglorp 6y agoNice. How do you feel about Elixir, seeing as how you're working in both? I'm happy with straight erl but always curious about the other grass.
- StreamBright 6y agoSince I learned Erlang first and I really like it I have no issues with its syntax. I do not even understand people complaining about it. Elixir is just Ruby(ish) syntax on the top, it does not add anything (or takes away anything) at least to me. I write a lot of F# so I think I probably like it because Elixir took some of the features from F# (or ML languages). It is nice to have a pipe operator. One piece of functionality that is nice to have is fmt. You can format your code before committing to the repo, this takes away some of the bikeshed arguments. Other than that I am not using much from Elixir. Jose is a really smart Erlang guy though. He used to hang out on IRC and StackOverflow answering Erlang questions. Straight Erlang is fine.