1.  

    A patch would be great, I don’t have a Mac.

    1.  

      I always associated the stdio functions more with the portable subset part of C, rather than Unix specifically. For Unix-specific I/O, I’d think of open, read, write, and one of our many friends, creat.

      1.  

        I looked into using highlight.js, but I want to minimize page size and load times, so using as little javascript as possible.

        Staying on an old version of hugo wouldn’t be so bad except that they don’t version their help, so you have no easy of getting the documentation that matters for your version.

        1.  

          That quote is from the talk From Parallel to Concurrent. He says it at 20:40.

            1.  

              On Firefox / macOS the (native) checkbox and option thingys are misaligned vertically.

              1.  

                Creating a memorial site for my deceased cats. This was prompted by the death of my almost two year old cat Max by a careless driver. Also staying in isolation as much as possible & washing my hands.

                1.  

                  Also Rob Pike:

                  The Go programming language was conceived in late 2007 as an answer to some of the problems we were seeing developing software infrastructure at Google. The computing landscape today is almost unrelated to the environment in which the languages being used, mostly C++, Java, and Python, had been created. The problems introduced by multicore processors, networked systems, massive computation clusters, and the web programming model were being worked around rather than addressed head-on. Moreover, the scale has changed: today’s server programs comprise tens of millions of lines of code, are worked on by hundreds or even thousands of programmers, and are updated literally every day. To make matters worse, build times, even on large compilation clusters, have stretched to many minutes, even hours.

                  Go was designed and developed to make working in this environment more productive. Besides its better-known aspects such as built-in concurrency and garbage collection, Go’s design considerations include rigorous dependency management, the adaptability of software architecture as systems grow, and robustness across the boundaries between components.

                  talk

                  1.  

                    Don’t want to leave the impression that ‘unfortunate conglomerates” is my general modus operandi, it’s definitely the oops.

                    In the usual, neat, case I find myself splitting between exploring them in magit and just scrolling the output of git diff in a terminal window.

                    1.  

                      Where does this quote come from?

                      1.  

                        Doesn’t it? I thought that was pretty much the definition.

                        Quirks aren’t a killer and I don’t think the author is arguing against using Go. But if its behaviour is surprising or unexpected to newcomers then that’s something to be aware of and hopefully improve upon.

                        1.  

                          If “people leave managers, not companies”, do they also “join managers, not companies”?

                          FWIW I’d answer “often, yes” to that one – of tech jobs I’ve taken in the past 15-ish years, only one didn’t have my impression of the manager I’d be working for as a heavy influence on my decision to accept an offer, and the last two were explicitly taken based on my liking of/trust in the manager who hired me.

                          1.  

                            There is another way of solving this issue using an HTML tag which points to the right git repository, but this requires the Git plaform to support it. It doesn’t feel like a good design decision to require Git platforms to add this special case for Go modules. Not only does it require upstream changes in the Git plaforms, but it also requires the deployed software to be upgraded to a recent version, which is not always a fast process in enterprise deployments.

                            Not a Go programmer but from what I get this doesn’t require any changes from Git platforms: on the contrary one can have a static site with <meta> imports (say, on example.com) that point to your Git platform of choice (say gitlab.example.com).

                            That the <meta> is used and embedded in Git platforms is just a convenience, not a hard requirement.

                            1. 6

                              On this topic, I recently submitted a pull request to replace lobsters little avatars with libravatar, and while I was at it, also implemented it for Emacs (ergo it will be used by Magit and Gnus), where it will be used as default after version 28.

                              Those who knew about the service, but didn’t pay too much attention (like me) might have been surprised to hear that they nearly shut down two years ago, but were then revived and revamped by groups using them.

                              1.  

                                I actually didn’t know about Tufte CSS at the time, but it is absolutely inspired by Tufte’s books, and the Tufte LaTeX theme that’s around.

                                1.  

                                  I find the article a bit misleading. From where I am sitting, author is confusing AI and automation. Labor automation is real, is happening, and does lead to workers losing jobs. This is happening in most of the industrialized sectors. Yes, AI will not replace any significant amount of jobs anytime soon, but robots (automation, mechanical, non-intelligent) will.

                                  – Written on a portable device assembled by non-human workers

                                  1.  

                                    I have used nanoc since several years for my blog. As part of my desire to move as much as possible to Emacs, I am currently working on porting it to a purely Org-based setup. When done, I will finally also have an English version of my blog (not that this is a nanoc restriction, but I never came around to implement it before I wanted to port everything to Org).

                                    1.  

                                      The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt.

                                      – Rob Pike

                                      1.  

                                        12/ The best predictor of future performance is recent performance in similar situations.

                                        37/ Ask the receptionist how the candidate treated them.

                                        41/ We leave too much of recruiting to Recruiting teams. Functional teams should take more responsibility for their own recruiting.

                                        51/ The critical recruiting problem most companies face is attracting candidates, not filtering them. Yet most focus on filtering.

                                        54/ Resumes show if the candidate can write a coherent document (which is important, and many candidates can’t do). But not much more.

                                        57/ Be careful when interpreting reference checks; most people are poor judges of talent.

                                        69/ If “people leave managers, not companies”, do they also “join managers, not companies”?

                                        What are your favorites ?

                                        1.  

                                          I think there are two things here. First, how idiomatic is the language. For example Python and Go are both idiomatic (Pythonic way / Go way). Second, how much are these idioms being enforced. Python doesn’t enforce idioms at all (it is possible to write C-like Python easily). It seems that in this case, Go enforces “Constants should be named” idiom. However I believe that Go will (or maybe already is) be hacked in a big project (code-base) that escapes from these enforced idioms, since beauty of the code (and everything else) is in its diversity.