I suspect I get mild SAD in the winters. Not enough to feel truly depressed, just more of a constant low-level “damn, I wanna nap right now.”

It’s probably different from your case, but what helped me was a sunlight lamp (light therapy) and a grab bag of supplements - standard multivitamins as well as magnesium pills and vitamin D fortified milk.

Oof. Looks like this affected some other languages as well - somebody at Microsoft needs to up their documentation game, methinks.

Snowball throwing was banned because a nephew of a friend of a friend of a teacher was supposedly blinded by one.

FWIW, this can actually happen, although I still think that’s an overbearing rule. One of my younger siblings had a teacher who was blind in one eye - ice shards from a snowball when she was in elementary.

Chevy Suburban. I volunteered to drive for a university course field trip and it’s what I got stuck with.

• Unresponsive fatass brick of a vehicle. I mean, come on, a minivan has more cargo space and the same passenger capacity without three light aircraft worth of inertia.
• Dashboard sucked. It took me a solid three minutes to find the button shifts. (I know these can be done well - Honda does them right - but the PRNDL was fucking laid out in a thin row at the side of the dashboard. Huh?)
• Overtaking damn near anything would redline the (very new, less than 10k miles) engine.

I understand the sentiment, but… HTML and some light CSS is just as fast and much more accessible. It just strikes me as something that defines itself in opposition to “thing everyone uses” for no good reason.

A large language model has no concept of good or bad, and it has no logic.

Tragically, this seems to be the minority viewpoint - at least among CS students. A lot of my peers seem to have convinced themselves that the hallucination machines are intelligent… even when it vomits unsound garbage into their lap.

This is made worse by the fact that most of our work is simple and/or derivative enough for $MODEL to usually give the right answer, which reinforces the majority “thinking machine” viewpoint - while in reality, generating an implementation of & using only ~ and | is hardly an Earth-shattering accomplishment.

And yes, it screws them academically. It doesn’t take a genius to connect the dots when the professor who encourages Copilot use has a sub-50% test average.

My guy, see a doctor. Temporary blindness/blacking out is not a normal reaction to nicotine, even in excess. “Nic sick” should just mean nausea/vomiting, dizziness and headaches.

I liked GalaxQL.

Can’t beat Iosevka in my opinion. I use the Term variant for my shell as well.

A few posters I bought from the campus poster sale at the start of the year. (Specifically, a woodblock print, a solar system map and a Cowboy Bebop poster.)

I have a huge window with a nice view (in a university owned apartment no less!) so I can afford to skimp on the other walls.

At least five years. Even if the company goes under tomorrow, it’ll be a while before the mainboard is truly obsolete. The main “consumable” would be the battery, which I can probably hack a replacement for if official parts are no longer available.

I’ve had mine (first generation 13" model) for over a year now. I’m very happy with it, and I intend to make it last me through university (3 years) and then some. I would consider it a good investment for me.

… Eh, no. I’ve seen GPT generate some incredibly unsound C despite being given half a page of text on the problem.

Well, that’s to be expected - the implementation of map expects a function that takes ownership of its inputs, so you get a type mismatch.

If you really want to golf things, you can tack your own map_ref (and friends) onto the Iterator trait. It’s not very useful - the output can’t reference the input - but it’s possible!

I imagine you could possibly extend this to a combinator that returns a tuple of (Input, ref_map'd output) to get around that limitation, although I can’t think of any cases where that would actually be useful.

It wouldn’t be as relevant, since passing a function or method instead of a closure is much easier in Rust - you can just name it, while Ruby requires you to use the method method.

So instead of .map(|res| res.unwrap()) you can do .map(Result::unwrap) and it’ll Just Work™.

The GNOME text editor or Nano.

I appreciate Vim, but when I just need to inspect something or change a single line, the former are easier.

As for Neovim and Emacs… I don’t have eight hours to set aside monthly to keep them configured and working.

You forget that many people live in areas where passenger rail infrastructure is not economically (or practically) viable. I, for one, pity the grain truck that has to drive over an unpaved road.

Yeah, the Copilot ad in the source viewer smacks of desperation.

Unfortunately, it’s not that simple. The Remote* extensions rely on the (proprietary) VSCode server, and nobody has managed to hack it to work with e.g. Codium.

Mostly just Visual Studio Code, alongside the usual constellation of Git + assorted language toolchains.

It’s plug and play at every level - no need to waste hours fucking around with an Emacs or (Neo)Vim configuration just to get a decent development environment set up.

(And yes, I would use Codium, but the remote containers extension is simply too good.)