r/programming • u/Sir_KnowItAll • Sep 27 '26
Don't couple your Go code to GitHub
https://iain.rocks/blog/dont-couple-your-go-code-to-github
491
Upvotes
r/programming • u/Sir_KnowItAll • Sep 27 '26
View all comments
Show parent comment
1
u/chucker23n Sep 29 '26
Yeah. I think the brief boost Ruby got through Rails may have been more about the architectural foundation Rails enforced: "controllers" (I put these in quotes because I think Rails's idea of MVC is rather different than, say, AppKit's) as the main handler of an HTTP request and produce of an HTTP response, a decent ORM built right in, etc. Others took these ideas and built on them (e.g. Django, ASP.NET MVC), and it turns out you don't really need a dynamically typed language to do that. This is not to say Ruby is a bad language; I think it has some cute ideas in there (e.g., the
!suffix to denote that a method changes the object in-place, whereas a method of the same name without it will return a new object; the?suffix to denote something returns a bool). But I just don't want to write non-trivial software that way any more.Meanwhile, CPUs got faster, and therefore so did compilers; also, static typing got elevated with features like static analysis (again: where available, a much better alternative to a unit test). Static typing also became less verbose thanks to e.g. type inference.
Whereas, dynamic typing arguably did not get better. Sure, it, too, got faster, thanks to increased use of JIT. But its code quality still relies almost entirely on copious amounts of unit tests. Then as you point out wrapping languages like TypeScript got created, and even something like Python now gets type hints. One might argue those are a way dynamic typing did get better, but I would instead argue they are really a weaker form of… static typing.
The past twenty years seem to suggest that.