nickwitha_k (he/him)

It is a way to go but there are still cons there. Guaranteeing memory safety isn’t free. You have to pay for it somewhere, either at compilation time, like Rust, or during runtime like in Go. Both are solid approaches but GC will cause problems in cases where the extra runtime overhead is not acceptable.

sudo systemctl stop sawtrapd

Thank you!

Question: Can you suggest resources or tips for picking colors that are friendly for color-blind people? Is it easier to differentiate based upon saturation?

I’ve become convinced that the c-suite doesn’t even care of they think AI can do a job. If they can convince investors and/or the board that they should dump money into it and their golden parachute, that’s good enough.

Now, if only there was a term for intentionally misleading people investing in your leadership into thinking something is much more capable than it really is and running with the cash…

Version control integration

Almost always garbage, in my experience. Except for merge conflict resolution. That’s unbelievably nice. But git command lines have always been more reliable and less likely to end up with broken local branches.

Seriously though. The merge conflict resolution in three panes is super nice.

TIL. Thanks for that!

Yeah. I like using main() that way too. It’s usually just a high-level function that handles globals relevant to running in standalone and calling other functions to do work.

This is exactly why the conditional is used. It allows the script to function both as a standalone application and a library.

ETA: Probably would make sense to just treat it as default behavior in the interpreter and only require the conditional to overwrite in cases where main is not the main function and/or pre-processing is needed.

Use the modulo operator? Nah. Need to import the isEven library and a ton of other unnecessary sub-50 LOC libraries “maintained” by a single dev to make their CV look more impressive. /s

An AI company not respecting copyright and licensing? I’m shocked.

Svalboard. Not am EMACS user (it’s a fine editor/Lisp interpreter) but, even nice mechkb isn’t necessarily going to prevent RSI or exacerbation of existing conditions. Best to change to a text-entry device that is designed with humans in mind.

Man is that overvalued as fuck.

In this case, it’s a feature of the language that enables developers to implement greater amounts of parallelism. So, the developers of the Python-based application will need to refactor to take advantage of it.

https://docs.python.org/3/whatsnew/3.13.html#whatsnew313-free-threaded-cpython

It’s also, I find, much more widely supported on a wider variety of hardware and with easier config automation.

That would be reasonable. The people running these things aren’t reasonable. They ignore every established mechanism to communicate a lack of consent to their activity because they don’t respect others’ agency and want everything.

vi in base Ubuntu isn’t really vi. It’s vim-minimal.

Both, last I checked.

Yeah… That’s what I think the idiot is likely doing. Anyone doing so has no fucking business touching code.

Just read that the fuckstick is copying government data onto an external.