Show more

I’ve found my degree of productivity as a developer in direct proportion to the degree I’ve embraced the classic Unix command line tools vs. just using an IDE.

I've heard rumors that is moving toward adopting PAM. Anyone have information on this?

Someone last me week asked—not rudely, but with a genuine desire to understand—why people still write code and not computers.

I think we do ourselves a disservice by calling ourselves "coders." There's a lot more to what we do than write code. Writing code is the result of a lot of planning—planning that might happen more or less unconsciously, but happens regardless. And these parts are less easily automated.

Calling something the “Pit of Success” seems a bit overwrought when we really just mean “sane defaults.”

And if you want simplicity in programming, then I assert the following:

Static > Dynamic
Compiled > Interpreted
Simula-, C++, Java-style OO is a failure
Reflection should be used sparingly

Any others?

Show thread

That was really just a set up for this Dennis Ritchie quote: “A language that doesn’t have everything is actually easier to program in than some that do.”

Show thread

The thing about languages like C++ and Rust is that their syntaxes are so complex and overlapping that I end up spending as much time deciding how to represent something in the language as I do designing or implementing. I’m never as productive in these languages as simpler ones.

Mozilla has lost its way, making the web browser game a virtual monopoly. Google wins.

If anyone needs me, I’ll be hanging out on Gopher and IRC. Might also check out Gemini.


«We cannot have a society in which, if two people wish to communicate, the only way that can happen is if it's financed by a third person who wishes to manipulate them.»

— Jaron Lanier

Now that I’m trying to work with the API, this seems like a dumb question. Checked exceptions are too burdensome.

Show thread

Java’s Lock interface provides the methods lock and lockInterruptably, the former not responding even to user interrupts.

In what world would I ever want to lock non-interruptably?

Incidentally, I had been reading nobs(1) as "knobs," but I understand now that it should be pronounced "no-b-s" (bs for backspace, but one could think of more creative expansions).

Show thread

if(~ $termprog 9term || ~ $termprog win){
fn git {
`{which git} $* | nobs

Adding a second DoT provider to my forward zone seems to have resolved things:


Show thread
Show more

A private Mastodon instance