Traister101

@[email protected]

Yo whatup

This profile is from a federated server and may be incomplete. View on remote instance

Traister101 ,

We do know we created them. The AI people are currently freaking out about does a single thing, predict text. You can think of LLMs like a hyper advanced auto correct. The main thing that's exciting is these produce text that looks as if a human wrote it. That's all. They don't have any memory, or any persistence whatsoever. That's why we have to feed it a bunch of the previous text (context) in a "conversation" in order for it to work as convincingly as it does. It cannot and does not remember what you say

Traister101 ,

Interesting direction to go...

An Important Hypothetical - What Android Apps Do You Install?? ( sh.itjust.works )

You're twelve years old on Thanksgiving at six thirty in the morning. You'll be leaving for Grandma's in about a half hour, and she's lives a three hour drive away, going in one direction. You have nothing to prepare yourself on this journey, other than a tablet running Android Eleven. Beware, the speaker is broken and there is...

Traister101 ,

A BTD game, probably BTD6 but BTD5 would do

Traister101 ,

Semantic whitespace is awful because whitespace (something that you can't actually see) has meaning in how the program runs. Braces { } for scopes gives you the ability to easily tell at a glance where a scope ends. Whitespace doesn't allow for that. Especially, especially when you can accidentally exit a scope (two new lines in a row with Python) and it's not actually an error (Pythons global scope). Yeah formatters and linters make this less of an issue but it sucks... Languages with legible symbols for scoping are significantly easier to reason about, see end symbols in Lua.

Traister101 ,

It erases the type of what your pointing at. All you have is a memory location, in contrast to int* which is a memory location of an int

Traister101 ,

Sounds like the same shit those rare metal guys are always yapping about but with extra scams...

Traister101 ,

Smart pointers model ownership. Instead of (maybe) a comment telling you if you have to free/delete a returned pointer this information is encoded into the type itself. But that's not all, this special type even handles the whole deleting part once it goes away.

Since they model ownership you should only use them when ownership should be expressed. Namely something that returns a pointer to a newly allocated thing should be a std::unique_ptr because the Callie has ownership of that memory. If they want to share it (multiple ownership of the object) there's a cheap conversion to std::shared_ptr.

How about a function that takes in an object cause it wants to look at it? Well that doesn't have anything to do with ownership so make it a raw pointer, or better yet a reference to avoid nullability.

What about when you've got a member function that wants to return a pointer to some memory the object owns? You guessed it baby raw pointer (or again reference if it'll never be null).

Traister101 ,

There's most certainly residuals, I've accidentally deleted then installed Windows on top of a bunch of my game saves. I found some random file recovery application and let it run for awhile. Guess what? Nearly everything was readable despite the fact it got wiped and then had a whole windows install.

NAND also experiences minor permanent damage on writes. Actually clearing the NAND involves a write as the charge has to be forced out (a write of 0s)

Traister101 ,

JetBrains might not be my friend but they don't hold anywhere near the dev tool monopoly Adobe does for artists. Know what happens if JetBrains starts to blow massive ass? I finally sit down and figure out how to get my terminal editor working with my LSP. Yeah I lose some productivity but not as much as I'd lose by using Visual Studio or fuckn Eclipse.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • kbinchat
  • All magazines
    •