41–48 of 48 posts
This looks really interesting! But I can't see any way to subscribe to book updates. A mailing list (my preferred means of subscribing to this kind of stuff these days) or an rss feed to get notified when new chapters are ready would be really handy.
Earlier quoted context omitted.
If this guy isn't getting headhunted, I have no idea what headhunting is. It's pretty rare for people to be able to write correct and easy-to-read guides to such low level concepts.
Finding a job is easy, finding the right job is hard for people like this.
Earlier quoted context omitted.
Finding a job is easy, finding the right job is hard for people like this.
Part and parcel of "There are not enough programmers [willing to work long hours for low pay]!"
Earlier quoted context omitted.
Part and parcel of "There are not enough programmers [willing to work long hours for low pay]!"
For that talent, it might even be that the work is too boring regardless of the hours or pay.
*I wish I could put that in sarcastic quotes.
Earlier quoted context omitted.
Your comment implies that programmers stop learning once they are slightly advanced.
No, it doesn't imply that, at all. My least favorite thing on the Internet nowadays are shallow fault-finding comments like yours from people who just want to interject themselves into discussions where they have nothing substantive to say. I used to be that guy and still have to actively resist the temptation. Don't be that guy.
Earlier quoted context omitted.
No, it doesn't imply that, at all. My least favorite thing on the Internet nowadays are shallow fault-finding comments like yours from people who just want to interject themselves into discussions where they have nothing substantive to say. I used to be that guy and still have to actively resist the temptation. Don't be that guy.
Oh, man — not being that guy, at least in the fault-finding sense; just apparently failing to make an obvious joke. Very strictly, grammatically speaking, it does say that, and it was a humorous implication to me, since I have known so many programmers who apparently did stop learning once they were very slightly advanced. But I'm completely aware that the implication was accidental.
Very interested in seeing how he'll deal with lexing Haskell. It's a major pain, tools like Parsec are very good out of the box with whitespace insensitivity, but not whitespace sensitive stuff.
Its not that hard to implement some form of whitespace sensitive parsing, you need to maintain explicit state, essentially a stack and a number of combinators. See for example https://github.com/purescript/purescript/blob/master/src/Lan... The state is defined in https://github.com/purescript/purescript/blob/master/src/Lan... (its just the column number). I believe the whitespace rules for Haskell are somewhat subtle…
Earlier quoted context omitted.
I suppose using haskell-src-exts is cheating...
"I will build haskell by taking the source code and running it" I jest, but this is an issue I've thought about idly for a while. Maybe it's possible to write a two-step parser: one that turns chars into tokens (and cheat a little bit by stripping spaces in some contexts to make it context free), and then you have a nice CFG that you can do easily.
I asked whether I could use bash, and consider gcc a feature of the language.
I was informed that would be cheating.