master or prologic/yarnd:latest Docker image this _should_ be fixed π
master or prologic/yarnd:latest Docker image this _should_ be fixed π
Apple's main selling point is a walled garden of privacy and no ad serving or ads shoved down your throat by anyone.
don't do this.
Apple's main selling point is a walled garden of privacy and no ad serving or ads shoved down your throat by anyone.
don't do this.
In case you missed it @mckinley βοΈ Just looked at the "Manage Account" Dashboard of my account with Open AI and since launching this ~12hrs ago last night (for me) $0.13 of my $18 free credit has been used π ~
In case you missed it @mckinley βοΈ Just looked at the "Manage Account" Dashboard of my account with Open AI and since launching this ~12hrs ago last night (for me) $0.13 of my $18 free credit has been used π ~
h
2022/08/13 23:58:37 build: index.md
exec: "jointoday.sh": cannot run executable found relative to current directory
exec: "pods.sh": cannot run executable found relative to current directory
Has Alpine changed some security policies on their image?! π€ π€¦ββοΈ
h
2022/08/13 23:58:37 build: index.md
exec: "jointoday.sh": cannot run executable found relative to current directory
exec: "pods.sh": cannot run executable found relative to current directory
Has Alpine changed some security policies on their image?! π€ π€¦ββοΈ
docker build (that's how it's built and hosted) is somehow missing these bits π€
docker build (that's how it's built and hosted) is somehow missing these bits π€
GPT3 Demo
Source: https://git.mills.io/prologic/gpt
You can tell I just "whacked" it together pretty quickly -- mostly imperative, procedural style.
GPT3 Demo
Source: https://git.mills.io/prologic/gpt
You can tell I just "whacked" it together pretty quickly -- mostly imperative, procedural style.
cc @mckinley as promised! π
cc @mckinley as promised! π
Anyway, who's coming today? I don't mind if it's just you and me @mckinley
Anyway, who's coming today? I don't mind if it's just you and me @mckinley
however the only point that he does make that I do agree with based on my own experiences as well as one of encapsulation which just doesn't work. In my opinion I think interfaces are a better way to encapsulate behavior ala Go.
however the only point that he does make that I do agree with based on my own experiences as well as one of encapsulation which just doesn't work. In my opinion I think interfaces are a better way to encapsulate behavior ala Go.
This was a really interesting video. I _think_ he really has a lot of valid points here, especially on encapsulation. I also especially agree on the point of just writing your program procedurally rather than getting bogged down in abstractions that just lead to premature mess -- or something I'm paraphrasing π
What do you think? π€
This was a really interesting video. I _think_ he really has a lot of valid points here, especially on encapsulation. I also especially agree on the point of just writing your program procedurally rather than getting bogged down in abstractions that just lead to premature mess -- or something I'm paraphrasing π
What do you think? π€
errors.New() is just how stupidly simple it really is:o
// New returns an error that formats as the given text.
// Each call to New returns a distinct error value even if the text is identical.
func New(text string) error {
\treturn &errorString{text}
}
// errorString is a trivial implementation of error.
type errorString struct {
\ts string
}
func (e *errorString) Error() string {
\treturn e.s
}
That's it! π
errors.New() is just how stupidly simple it really is:o
// New returns an error that formats as the given text.
// Each call to New returns a distinct error value even if the text is identical.
func New(text string) error {
return &errorString{text}
}
// errorString is a trivial implementation of error.
type errorString struct {
s string
}
func (e *errorString) Error() string {
return e.s
}
That's it! π
errors.New() is just how stupidly simple it really is:o
// New returns an error that formats as the given text.
// Each call to New returns a distinct error value even if the text is identical.
func New(text string) error {
return &errorString{text}
}
// errorString is a trivial implementation of error.
type errorString struct {
s string
}
func (e *errorString) Error() string {
return e.s
}
That's it! π