Louis :emacs: on Nostr: npub17rwq9…92p8j Thanks for sharing this article. It is a very good read. I think ...
npub17rwq9g7ptr4wj3r5cl3v4ys8629gw4pele8fn53a7hd679j3w0mqm92p8j (npub17rw…2p8j) Thanks for sharing this article. It is a very good read. I think there is not much to add, the author is right. We "like" Go because it gives us the power to do things the fast and easy way, postponing complexity to some other time.
I've spent almost the whole last week to migrate a project from Go to Common Lisp. Needless to say that it was not only a huge fun, but also quite surprising how good the result is. Not only in terms of performance but also in expressiveness of the resulting code, and I don't consider myself anything more than an intermediate.
To never have to compile, try, and debug the whole program from state 0, but building block by block and staying in a live image during the whole time was an eye-opener.
Also, Common Lisp gives you a lot of choices. Which might be one of the pain points for devs (like me) coming from very opinionated languages. As a die-hard advocate of static typing, experiencing how I can build anything more complex than a simple script without having to deal with types (almost) at all puts a new perspective on the importance of static typing. Especially when you have to deal with external dynamic data sources (JSON, SQL) (i.e. json.Unmarshal doesn't tell me when the source is missing or adding fields, it just complains when types do not fit).
Unlike the author I'm not a language expert, but from what I can say now after my last week's effort is that I'm a bit more sceptical when it comes to the infallibility of Go as the best choice for server-side project.
Having said all that, I still "like" Go but wish that I've had seen the light a bit earlier.
#CommonLisp
I've spent almost the whole last week to migrate a project from Go to Common Lisp. Needless to say that it was not only a huge fun, but also quite surprising how good the result is. Not only in terms of performance but also in expressiveness of the resulting code, and I don't consider myself anything more than an intermediate.
To never have to compile, try, and debug the whole program from state 0, but building block by block and staying in a live image during the whole time was an eye-opener.
Also, Common Lisp gives you a lot of choices. Which might be one of the pain points for devs (like me) coming from very opinionated languages. As a die-hard advocate of static typing, experiencing how I can build anything more complex than a simple script without having to deal with types (almost) at all puts a new perspective on the importance of static typing. Especially when you have to deal with external dynamic data sources (JSON, SQL) (i.e. json.Unmarshal doesn't tell me when the source is missing or adding fields, it just complains when types do not fit).
Unlike the author I'm not a language expert, but from what I can say now after my last week's effort is that I'm a bit more sceptical when it comes to the infallibility of Go as the best choice for server-side project.
Having said all that, I still "like" Go but wish that I've had seen the light a bit earlier.
#CommonLisp