Oh man, you keep finding these hex values in other places. I assumed the author of this particular theme just made them up, based on what they thought looked good.

And yeah, that is wild to me, that it passes a contrast check. I’m far from having the worst eyesight and still find it needlessly difficult to read.

Well, if he just got his tenure at 40, that means he presumably did something else in his life before tackling this path. Him saying the students can just call him Jeff is also maybe linked to him having still been a student until recently. I assume, it’s a case of this being funny, if you actually study history and know a professor like that. 🫠

Yeah, I do customize the themes like that, too, usually also #ffffff for the foreground or vice versa. It would just be nice to not need to maintain my own themes. 🥴

I try to kick my circadian rhythm with ample light, so for that I switch between light and dark theme more or less around sunrise/sunset. Staring into a bright screen with light theme isn’t as bright as being outside, but then I can at least also turn on all kinds of lights or sit outside somewhere, without it being as detrimental to readability as it would be with a dark theme.

I guess, what really bothers me here in particular is the extra low contrast. The background does actually use the correct color, that you point out. But the foreground/text color is #654735. That’s brown:

I don’t know where that color comes from. None of the original Gruvbox colors are that. It is dubbed as a “Gruvbox Material” theme. I do have opinions about the new Material You styles having shit contrast. But I don’t believe, it’s supposed to be quite as terrible either.

And well, yeah, I do usually end up modifying the Gruvbox themes to just set background to #ffffff, foreground to #000000, or vice versa for dark themes. It does work quite well IMHO, which is what makes it all the more frustrating that so many Gruvbox-like themes choose to go the other way.

As far as I’m aware, it started out with a Vim color scheme, which looks like this:

https://github.com/morhetz/gruvbox

And yeah, that’s just become a really popular theme, which got ported to virtually anything that can be themed.
Personally, I really like the color palette, but not that so many takes on it have text that’s horrendously difficult to read…

I think, it’s just used as in “late bloomer”, so someone who needed a bit longer, but now found their true potential. “Bloom” as in the thing flowers do.

https://infosec.exchange/@0xabad1dea/116335209525412306

The problem is that in this case, the LLM just naively auto-completes a password from what it knows a password to most likely look like.

It is possible to enable an LLM to call external tools and to provide it with instructions, so that it’s likely to auto-complete the tool call instead. Then you could have it call a tool to generate a correct horse battery staple, or a completely random password by e.g. calling the pwgen command on Linux.

But yeah, that just isn’t what this article is about. It’s specifically about cases where an LLM is used without tool calls and therefore naively auto-completes the most likely password-like string.

I imagine, it’s a matter of asking it to generate some configuration and one of the fields in that configuration is for a password, so the LLM just auto-completes what a password is most likely to look like.

It’s Apple’s programming language, kind of intended as a successor to Objective-C.

From what I hear, it’s actually decently designed and has quite a few similarities to Rust. Still not sure, how great it is outside of the Apple ecosystem…

My instance went down, so I’m way too late to make this joke, but anyways:

We’re not cantankerous, just a little …crabby. 🙃

We currently have some larger road construction sites in the city and therefore also traffic jams. Yesterday, my bus got stuck in one and I decided to get out at the next stop and walk to the following bus stop. When I arrived there, I looked back and saw that the bus had made it about halfway, which is just wild to me.

I don’t remember the details, but the Meltdown and Spectre vulnerabilities from a few years ago also felt like they were cutting corners. Those were enabled by some fundamental architectural decisions, which really just didn’t sound like a good idea to me, when I read up on them.

Considering their policy for the majority of their existence has been that open-source is cancer, it might as well be viewed like that. Just buy the central open-source exchange platform and slowly make it worse to hurt all of open-source.

Yeah, and the worst part is that submitting the PR is trivial. You just offload the reviewing work onto the maintainer and then feed the review comments back into the AI. Effectively, you’re making the maintainer talk to the AI, by going through you as a middleman, a.k.a. completely wasting their time.

Yeah, there are still indie titles with infamous creators. It’s just that the limelight is now taken by big corporations with big marketing budget.

I don’t feel like these positions are at odds with one another, unless you become active in reducing the number of humans, of course.

Like, you can uplift and protect people by stopping them from killing their environment, because you recognize that people are an invasive species that will do that.

If you’ve got access to a microwave, I’ve found rice dishes quite convenient, like for example a lentil curry. They generally re-heat without tasting worse and the rice traps the moisture, so even if your container isn’t 100% sealed, you’re unlikely to get mess everywhere.

(Though I’d still recommend getting a properly sealed container. Personally, I also transport my food in a separate cloth bag, so that if it should ever leak, I can just wash that bag.)

Yeah, feels like the correct move here would be to hold off with the next generation, if you can’t get enough of a performance jump without increasing prices. Otherwise you’re just offering a premium edition.