Okay, but just to be clear, the problem is not that it can’t do a timer. The problem is that it claims to be able to and even produces a result which looks plausible. It means, you cannot trust it to do anything that you can’t easily verify. If they could fix that overconfidence in a year, it would be much better.
I’ve been wondering, if you could combine LLMs with a logic programming language like Prolog. The latter is actually able to reason through things, you “just” have to express them in Prolog facts and rules.
Well, from doing a quick online search, I’m most certainly not the first person to think of this, which does not surprise me at all…
Hmm, is the last staff thing just the death message from Sif Muna? I seriously don’t play often enough with Sif Muna, because Heplhjdtfhxhdh always seems so good… 🥴
Yeah, in particular, anything close to 100 million users presumes that non-gamedevs will use this. For anything beyond simple variations of existing games, like e.g. “Skyrim with spears”, you need to have an actual understanding of game design. It is not enough to have cool ideas.
So, I really don’t see many non-gamedevs using this. Especially when they can pay less to play a properly designed game.
Okay, but why would you:
a) use machine learning for rolling out an update,
b) tell your users that you’re using machine learning, and
c) not call it “AI-based”, so that your investors throw more money at you?
Also interesting: What’s “cloud nine” in English is “cloud seven” in German (“Wolke Sieben”).
No idea, if those are linked…
Yeah, I can understand the frustration when an external decision forces you to disappoint some of your users, but ultimately you have to pick your battles. When neither the Python nor Rust ecosystem thinks those platforms are worth supporting, it’s probably not either worth it for you to worry…
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.
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…
And 3 months later, i have not booted it once
Oh man, I know the feeling. It took me 5 months to remember that I had a Windows partition.
It was so important to me, to have a way back (which is fair enough), and then I just completely forgot about it.
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.
There’s a very faint “pbfcomics.com” in the bottom right in the last panel.
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. 🙃
I like to use LilyPond for transcription. It’s basically LaTeX for sheet music.
For 8-bit music, I like to dick around with MilkyTracker. It’s a tracker-style composition tool, which basically came to be in early computing days. It takes a bit to get used to, but then it’s super simple for writing a quick chiptune.
And I guess, I’ll also throw in VMPK. It allows you to play piano on your computer keyboard, similar to how lots of DAWs do.
As with any such implementation, it’s unfortunately limited by keyboard rollover, but still useful for playing around with intervals and jamming a bit. It can also be used as MIDI input for audio software, which doesn’t have this feature built-in.