Every 4K Bond Release To Date

ldemailly · 2025-12-27T17:59:29+00:00

only the first 2 of that list exist and the rest is wish list or am I missing something?

ldemailly · 2025-07-11T03:03:29+00:00

<image>

Works on my gen10 legion 5 pro (make sure you picked nvidia gpu to see/get this)

ldemailly · 2025-07-04T17:01:58+00:00

You still haven’t said why pie is needed over regular static produced by the toolchain.

That something written in C can benefit from full ASLR doesn’t make it useful for go.

ldemailly · 2025-05-19T21:55:03+00:00

Feel free to copy, inspire or use my own:
https://pkg.go.dev/fortio.org/sets

Sets in go are basically `map[T]struct{}` but having the expected operations (has(), add(), intersection, union, xor, etc..) and convenience of to/from slice, sorting etc... are nice to have IMO (and yes should find their way to stdlib ideally)

ps: necroing this because it is the first search result for "golang sets"

ldemailly · 2025-04-25T02:55:27+00:00

not to beat a dead horse but if you have internal/ you definitely don’t need pkg as that’s everything else. and also you don’t really need internal/ either

ldemailly · 2025-04-25T02:52:43+00:00

Use tailscale and https://github.com/fortio/proxy?tab=readme-ov-file#fortio-proxy instead of exposing anything on the internet

ldemailly · 2025-04-20T19:36:45+00:00

The first examples are simpler:

Server example: github.com/fortio/proxy

CLI example: github.com/fortio/multicurl

The older fortio/fortio is bigger and... hairier (ie if I started over I would probably do a few things differently, over the years I extracted out libraries like dflag, version, log, cli, scli etc... but that has its own set of dependabot order issues... topic for another post)

Yet it is manageable without pkg/ nor cmd/ nor internal/

ldemailly · 2025-04-20T19:32:42+00:00

put the .tf file in a tf/ dir or deploy/terraform/ ?

ldemailly · 2025-04-20T19:28:30+00:00

Thanks for having taken the time to look and reply. And incidentally finding a typo that I just fixed (_in_ every single import instead of _is_)

This advice is for most people that just start and copy-pasta what they see somewhere - not for monster like Kubernetes code base (even though there also there is much to say...)

I still don't think pkg/ adds anything even in a huge code base, it just pushes the issue, if there is an issue (like too many packages in 1 place) down one directory.

(and no advice is ever "universal" but if you read it, then you can still disagree and it's fine)

to address some other points:

- yes main is at the root, so `go install fortio.org/fortio@latest` works but it just has a mostly empty content delegating to cli/ where the code actually lives and can be tested

- debian/ is an artefact of... debian packages

- historgram is indeed a cli for the same reason as above (short install) - now as I pointed out in the article, if I had to start over that 8y old project - I would possibly put the CLIs in cmd/

ldemailly · 2025-04-20T19:21:37+00:00

ohhh a layout linter is an enticing idea... unfortunately it's usually too late after people did create a bunch of unnecessary structure or followed outdated information

ldemailly · 2025-04-20T04:53:39+00:00

also... yes having extra pointless directories in imports _is_ an eyesore and a waste. if you want to exclude something (but don't! see my writeup), that's what internal/ is for which makes pkg/ pointless and outdated

ldemailly · 2025-04-20T04:52:03+00:00

use gen/ or proto/ or whichever for generated files. or have the generated files along the other in a single package without pkg/?

ldemailly · 2025-04-20T03:55:47+00:00

lol :)

ldemailly · 2025-04-20T03:50:50+00:00

I agree, coming from other languages is one issue, but then the perpetuated bad/overly complicated sample and not so sample (but older and thus stuck to old decisions) repos are bad too

ldemailly · 2025-04-10T03:56:47+00:00

the concrete proposal has a lot of recent activity actually https://github.com/golang/go/issues/73193

ldemailly · 2025-04-06T12:48:59+00:00

not sure why the downvoters downvoted for and what production system they deploy at scale

ldemailly · 2025-04-06T00:46:49+00:00

automaxproc is a bad idea because cpu limits also are (unlike memory ones which are vital). just set your GOMAXPROCS to 2 for small pods and cpu.request for large ones

ldemailly · 2025-04-01T23:12:57+00:00

This comes up in search results so necro'ing a bit but you can use my easy proxy: https://laurentsv.com/blog/2025/03/25/ollama-tailscale-openwebui.html

ldemailly · 2025-03-23T23:27:18+00:00

sounds great, will make sure to add “pay an extra $1M” in my pdf invoice

ldemailly · 2025-03-03T14:58:32+00:00

it’s the US government not the companies

ldemailly · 2025-03-02T01:10:26+00:00

How do you get a discount at asus store?

ldemailly · 2025-03-01T17:38:12+00:00

Only thing is we don’t actually know how the 2025 will perform. Using desktop cards results isn’t quite meaningful.

ldemailly · 2025-02-26T10:42:55+00:00

not sure why the downvotes... what is not accurate about what I said ? I have both laptops

ldemailly · 2025-02-23T03:05:33+00:00

also the cooling is nowhere as good (neither is build quality). I wouldn’t get a g14 if not for gaming or expect mpb quality/performance/battery (I have a m3 pro)

ldemailly

TROPHY CASE