CodeBlooded

joined 2 years ago
[–] CodeBlooded@programming.dev 2 points 3 days ago (1 children)

Toyota? Buddy, that’s not a “pickup truck.” That’s a street legal war machine! A technical!!! 😎

[–] CodeBlooded@programming.dev 6 points 6 days ago (5 children)

What games are you playing and what hardware are you running?

Linux has come a long way regarding the ability to easily play games made to run on Windows. It’s never been so easy and well performing. However, in my experience, it’s not quite “just works” yet. Yes, some Windows games will “just work,” but for now that’s still the exception to the rule in my experience.

I use Arch btw, with a i9-9900 and an Nvidia RTX 2070. I still have to tweak settings, research what others are tweaking, I have a few hours of research and tinkering invested into stopping up close jitters in VR(still unresolved), my graphic settings have to be lower than normal for decent performance and I do not enjoy the same frames I’ve enjoyed on Windows with this same machine.

I could probably get some better performance squeezed out of these games, but it’s going to cost me time and tinkering.

tl;dr I don’t think we’re in “just works” territory yet, but we’re getting closer and the progress over the recent years has been amazing. I can’t wait to be rid of Windows forever.

[–] CodeBlooded@programming.dev 11 points 2 weeks ago (2 children)

For me, Docker has been amazing. It’s probably my single most favorite tool in my tool belt. It has made my life so much easier over the years. It’s far from hell for me! 🐳

[–] CodeBlooded@programming.dev 2 points 2 weeks ago

This meme is 10/10

[–] CodeBlooded@programming.dev 4 points 3 weeks ago

Just came back to Debian on my gaming rig after a 4 year hiatus, I’ve missed it.

[–] CodeBlooded@programming.dev 2 points 3 weeks ago (1 children)

XP was “the Linux” of Windows releases… 🤘

[–] CodeBlooded@programming.dev 18 points 1 month ago

Here’s another comment endorsing Signal.

https://signal.org/

[–] CodeBlooded@programming.dev 25 points 1 month ago (9 children)

I have never once understood these sock references and jokes. Never seen a programmer wearing thigh high socks. Never associated socks with specific programming languages.

What’s the punch that I’m missing here?

[–] CodeBlooded@programming.dev 4 points 1 month ago (1 children)

This same type of cable setup can be found in the Philippines as well.

[–] CodeBlooded@programming.dev 3 points 1 month ago

Roughly 1-3 time a month.

 
 

I’ve been using this to execute Go “scripts” in CI pipelines where Bash just doesn’t cut it. It’s an interpreter for Go. It can be used to treat Go code like a “script,” rather than a compiled application. It is also able to be imported into a Go program and used to load up Go code dynamically at run time (think “loading plugins” with Go!).

From the readme:

release Build Status GoDoc

Yaegi is Another Elegant Go Interpreter. It powers executable Go scripts and plugins, in embedded interpreters or interactive shells, on top of the Go runtime.

Features

  • Complete support of Go specification
  • Written in pure Go, using only the standard library
  • Simple interpreter API: New(), Eval(), Use()
  • Works everywhere Go works
  • All Go & runtime resources accessible from script (with control)
  • Security: unsafe and syscall packages neither used nor exported by default
  • Support the latest 2 major releases of Go (Go 1.19 and Go 1.20)

Install

Go package

import "github.com/traefik/yaegi/interp"

Command-line executable

go install github.com/traefik/yaegi/cmd/yaegi@latest

Note that you can use rlwrap (install with your favorite package manager), and alias the yaegi command in alias yaegi='rlwrap yaegi' in your ~/.bashrc, to have history and command line edition.

CI Integration

curl -sfL https://raw.githubusercontent.com/traefik/yaegi/master/install.sh | bash -s -- -b $GOPATH/bin v0.9.0

Usage

As an embedded interpreter

Create an interpreter with New(), run Go code with Eval():

package main

import (
	"github.com/traefik/yaegi/interp"
	"github.com/traefik/yaegi/stdlib"
)

func main() {
	i := interp.New(interp.Options{})

	i.Use(stdlib.Symbols)

	_, err := i.Eval(`import "fmt"`)
	if err != nil {
		panic(err)
	}

	_, err = i.Eval(`fmt.Println("Hello Yaegi")`)
	if err != nil {
		panic(err)
	}
}

Go Playground

As a dynamic extension framework

The following program is compiled ahead of time, except bar() which is interpreted, with the following steps:

  1. use of i.Eval(src) to evaluate the script in the context of interpreter
  2. use of v, err := i.Eval("foo.Bar") to get the symbol from the interpreter context, as a reflect.Value
  3. application of Interface() method and type assertion to convert v into bar, as if it was compiled
package main

import "github.com/traefik/yaegi/interp"

const src = `package foo
func Bar(s string) string { return s + "-Foo" }`

func main() {
	i := interp.New(interp.Options{})

	_, err := i.Eval(src)
	if err != nil {
		panic(err)
	}

	v, err := i.Eval("foo.Bar")
	if err != nil {
		panic(err)
	}

	bar := v.Interface().(func(string) string)

	r := bar("Kung")
	println(r)
}

Go Playground

As a command-line interpreter

The Yaegi command can run an interactive Read-Eval-Print-Loop:

$ yaegi
> 1 + 2
3
> import "fmt"
> fmt.Println("Hello World")
Hello World
>

Note that in interactive mode, all stdlib package are pre-imported, you can use them directly:

$ yaegi
> reflect.TypeOf(time.Date)
: func(int, time.Month, int, int, int, int, int, *time.Location) time.Time
>

Or interpret Go packages, directories or files, including itself:

$ yaegi -syscall -unsafe -unrestricted github.com/traefik/yaegi/cmd/yaegi
>

Or for Go scripting in the shebang line:

$ cat /tmp/test
#!/usr/bin/env yaegi
package main

import "fmt"

func main() {
	fmt.Println("test")
}
$ ls -la /tmp/test
-rwxr-xr-x 1 dow184 dow184 93 Jan  6 13:38 /tmp/test
$ /tmp/test
test

Documentation

Documentation about Yaegi commands and libraries can be found at usual godoc.org.

Limitations

Beside the known bugs which are supposed to be fixed in the short term, there are some limitations not planned to be addressed soon:

  • Assembly files (.s) are not supported.
  • Calling C code is not supported (no virtual "C" package).
  • Directives about the compiler, the linker, or embedding files are not supported.
  • Interfaces to be used from the pre-compiled code can not be added dynamically, as it is required to pre-compile interface wrappers.
  • Representation of types by reflect and printing values using %T may give different results between compiled mode and interpreted mode.
  • Interpreting computation intensive code is likely to remain significantly slower than in compiled mode.

Go modules are not supported yet. Until that, it is necessary to install the source into $GOPATH/src/github.com/traefik/yaegi to pass all the tests.

Contributing

Contributing guide.

License

Apache 2.0.

 

OrbStack is a fast, light, and simple way to run Docker containers and Linux machines on macOS. You can think of it as a supercharged WSL and Docker Desktop alternative, all in one easy-to-use app.

I just caught wind of this and have yet to try it. Does anyone here have any experience with OrbStack that they can speak to? 👀

view more: next ›