I started programming before modern LLMs so I can still hack it without, it will just take a lot longer.
420 karma · joined December 6, 2016
trying to be more offline nowadays
I started programming before modern LLMs so I can still hack it without, it will just take a lot longer.
I think I've seen an adtech company use AI influencers to market whatever product a customer wanted to sell. I got the impression that it initally worked really well, but then people caught on to the fact it was just AI and performance tanked.
I don't actually know whether that was the case but that's the vibe I got from following their landing page over time.
Democratization they call it.
Go is generally fine for crosscompiling.
edit: what gave me pain with Rust for a cli was clap (with derive, the default). Go just worked.
Sometimes I am uncertain whether it's an absolute win. Analogy: I used to use Huel to save time on lunches to have more time to study. Turns out, lunches were not just refueling sessions but ways to relax. So I lost on that relaxation time and it ended up being +-0 long-term.
AI for sure is net positive in terms of getting more done, but it's way too easy to gloss over some details and you'll end up backtracking more.
"Reality has a surprising amount of detail" or something along those lines.
Buuut with Go one in general tends to reach less for dependencies so less likely to run into this and cgo is not go ;) https://go-proverbs.github.io
but for cross-compiling actually ended up filtering out the liconv flag with a bash wrapper and compiled a custom zig cc version with the support for exported_symbols_list patched in, things appear to work.
Should look into cross-rs I suppose. Hope it's not one of those "download macos sdk from this unofficial source" setups that people seem to do. Apparently not allowed by Apple.
Too ba null/nil is to stay since no Go 2.
Or maybe they would? Iirc 1.21 had technically a breaking change related to for loops. If it was just possible to have migration tooling. I guess too large of a change.
I don't like that for fairly basic things one has to quickly reach for crates. I suppose it allows the best implementation to emerge and not be concerned with a breaking change to the language itself.
I also don't like how difficult it is to cross-compile from Linux to macOS. zig cc exists, but quickly runs into a situation where a linker flag is unsupported. The rust-lang/libc also (apparently?) insists on adding a flag related to iconv for macOS even though it's apparently not even used?
But writing Rust is fun. You kind of don't need to worry so much about trivialities because the compiler is so strict and can focus on the interesting stuff.
I tried running various Linux distros on my desktop some years ago and definitely agree on the crap-out experience and having to reinstall. Eventually settled on macOS and it's been okay.
The game changer for me has been Nix. It works on macOS. I have had coworkers use it on Ubuntu. I am soon planning to switch to NixOS.
People complain about the syntax but honestly AI gets you around that. You will still do janitorial work, but you mostly only need to do it once.
latest release is 0.15.2 https://ziglang.org
I've recently started to contribute to open source, mostly just to add some tiny feature or such
I did not realise before this that getting your changes upstreamed can take a long time. Now I have even more respect for the likes of Asahi Linux. The code reviews usually improve the change a lot but it's not like coding at a company where best case you are able to get multiple changes deployed a day on repos your team does not even own.
But I feel it's worth the effort. For as long as my changes are not upstreamed I can keep using the forked version or just tolerate not being able to do something.
But the major issue I keep running into is how the build setup is painful. This is where Nix really comes to the rescue though. I can import the nixpkgs setup for the given project, point it to my forl/branch, and rebuild the software into my cachix for use in dev shells and containers.
I wish more people used nix. I would love to see it getting adopted as a backend for other package managers. Just maintaing a binary cache for your distro and it would be more or less the same.
But I suppose there are arguments against a monoculture as well.
Lefthook with glob+stage_fixed for formatters makes one of the issues raised a complete non-issue.
I'll write a in-depth post about it maybe within the next week or so, been diving into these in my hobby projects for a year or so.
> ssh exe.dev
> The disk persists. You have sudo.
on mobile
It didn't try to maximise by how much it won, but just that it won. Apparently it changed the meta for human pkayers.
If you have the time for it, the movie/doc is worth watching https://youtube.com/watch?v=WXuK6gekU1Y
cdk8s.io
> Intel staging area for llvm.org contribution. Home for Intel LLVM-based projects.
Seems like they use it to contribute to upstream which is business as usual?