#golang — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #golang, aggregated by home.social.
-
Well, done the holiday thing of relaxing for a day and ending up feeling ill.
Given I’ve been in bed most of the day decided to spend a little time on a pet #GoLang project. Then when I got exhausted I figured it was time I actually picked up Maus and read it.
-
The last few days of ZenZX and zen80 development (my ZX Spectrum emulator and my Z80 emulator respectively) have been mostly about fine tuning memory contention correctness with precise T-state count, I/O contention, floating bus emulation, ULA last out byte, and a few other quirks and idiosyncracies very particular to ZX Spectrum emulation.
I'm not aiming to make ZenZX a simulator (like flooh's Z80) or an extremely precise emulator (like @FromTheFourthPlanet 's SpecIDE).
The first goal of ZenZX is to be a legible and usable ZX Spectrum emulator written in Go. That has already been largely achieved.
The second goal is subjective: to be able to run a good part of the software I personally considered to be some of the best I used to know for the ZX Spectrum back in the day. This has been largely achieved as well. My shortlist was that an emulator that is able to run Batman, Head Over Heels, Bruce Lee, and Jet Set Willy is a good enough ZX Spectrum emulator. Of course there is plenty of room for disagreement about the specifics here, but the general idea was that if some of the best titles are able to run on ZenZX, why wouldn't most others worth playing?
Which takes me to the third criteria: running a game is not exactly the same as loading it, and having dedicated quite a lot of effort to emulate the NEC FDC controller of the Spectrum +3, for a whille I neglected tape loading. The reason for that was that I had already developed reasonably functional loaders of .Z80 and .SNA snapshots, as well as ZenZX's own richer snapshot format .ZXS.
Though not the main focus of ZenZX, tape loading is historically important and there are many tape files of copy-protected games that ZenZX is still unable to load, even if it's able to run the games they contained via snapshot files. The other reason this has taken a long time is that loading of copy-protected tapes for some kinds of turbo loaders implies clock-perfect emulation, and perfect simulation of a host of ULA and bus peculiarities. Perfection of simulation of all the quirks has never been a ZenZX goal, but still, considering the historical weight of tape loading I persevered.
But there is a limit to how much perfection I can achieve within the technical limits and scope of ZenZX. Within the range of stated goals for ZenZX, in the next few weeks I'll be nearing the end of the correctness checks I aimed to deliver, most games run, many more tapes now load which didn't load before the latest improvements, but the truth remains that many copy-protected tape files were never part of the goal, still don't load and may never load.
What still lies ahead is massive UI improvements, making it more usable, making it more enjoyable, supporting a few more Speccy cousin models and custom ROMs, and possibly providing support for esxDOS. In that direction, both the Zenas assembler, and the zen80 emulator are now compatible with the ZX Spectrum Next's Z80N, including a test harness that checks behaviour against CSpect.
My expectation is that ZenZx is going to reach version 1.0 sometime in the next few weeks or months, delivering a reasonable emulation of ZX Spectrum 48k and ZX Spectrum 128k models, along with a list of tested titles that actually run on it.
Updates and fixes and new releases of the 1.x branch will continue for the reminder of 2026. The rest of the stuff that doesn't make it to the 1.x cycle is going to be scheduled to be released as part of a roadmap towards 2.0, sometime in 2027.
References:
-- flooh's cycle-stepped Z80 simulator
https://floooh.github.io/2021/12/17/cycle-stepped-z80.html-- Martian Girl's SpecIDE ZX Spectrum emulator
https://github.com/MartianGirl/SpecIde#zenzx #zen80 #Spectrum #ZXSpectrum #Speccy #emulator #foss #golang
-
#asyncmachine-go v0.19.3 has been released https://asyncmachine.dev/release-notes. The highlight of this release is a go-iroh overlay for aRPC.
https://iroh.computer #statemachine #p2p #golang #webassembly #iroh
-
MongoDB is hiring Senior Software Engineer, Server Security
🔧 #cplusplus #golang #java #rust #aws #azure #gcp #mongodb #securityengineer #seniorengineer
🌎 New York City, New York
⏰ Full-time
🏢 MongoDBJob details https://jobsfordevelopers.com/jobs/senior-software-engineer-server-security-at-mongodb-com-apr-17-2026-5cd15a?utm_source=mastodon.world&utm_medium=social&utm_campaign=posting
#jobalert #jobsearch #hiring -
The #golang team is doing what it does best. Giving you enough rope to feel excited about something, but not enough, to hang yourself on it 😅
-
Working in a programming language that never bothered to implement a Set data structure in its standard library does take its toll sometimes.
-
CW: Tech (Go)
I quite like `go tool ...`, but in isn't actually very practical. In theory you can include all your test/release tooling in there, and then you only need to run them with go tool, and not use any other containers.
So things like golangci-lint, and goreleaser.
The problem is the deps are then all mixed together with your own code's deps. When you ahve a couple of bigger, complicated tools, the deps don't always get on well together. -
Progress is being made. Complete success is still probably days or weeks away.
#zenzx #emulator #golang #foss #ZXSpectrum #Speccy #Spectrum #retrogaming #retrocomputing
-
Due to the way the zen80 emulator works (the Z80 emulator I wrote) and because when I started it I aimed for readability of the code and educational value more than raw performance, I've been hitting against a few limitations that seemed somewhat intractable when trying to make ZenZX load fast a good portion of the ZX Spectrum game titles that use a "turbo" copy protection.
For many titles that don't use that specific type of copy protection, ZenZX could load .tap and .tzx files just fine in "fast" mode, instantly loading and playing a game that used to take 3 or 4 minutes to load from tape. But games like Chase H.Q. and others, especially those which have substantial 128k versions, were a different story.
The design of zen80 (and ZenZX by extension) doesn't easily allow for dynamic acceleration of the virtual Spectrum's memory access beyond a certain limit. This would have been trivial to solve in C or C++ using a
unionstructure to access memory through different field arrangements, but Go (the language I chose to write zen80 and ZenZX) doesn't admitunionstructures. (and I could have used Go'sunsafepackage to implement something equivalent, but that would have defeated the educational purpose of writing an emulator in safe, readable, and educationally useful Go).So I was faced with the difficult possibilty of having to substantially redesign the emulator I've been working on for a couple of years.
Thankfully, that wasn't necessary. I designed an alternative "fast-track" memory that zen80 can use to read from and write to memory and i/o ports, which represents an addition and extension to the existing design, whilst keeping all the existing interfaces the same.
What good is it to have these extensions if, essentially, the CPU that already exists, and the one that's already wired into the code can't be dynamically accelerated to the maximum? you might ask.
Well, what it does is that it allows me to execute a second Z80 in parallel, just for the turbo loaders, with very high precision, at very high speed. The maximum speed a modern computer can achieve is potentially thousands of times the speed of an emulated Z80, especially for a Z80 that's running in parallel without need to update the screen.
So essentially, ZenZX now has a third tape loading mode
--tapemode=turbo, in addition to the already existing--tapemode=fastand--tapemode=accurate, with "accurate" being an euphemism for f* slow, identical to the original ZX Spectrum ROM tape loading routine.After some minor surgery to the code, a parallel Z80 instance now loads the game in a separate, faster memory, and when it's done loading and decoding whatever it has to do in turbo mode, every new tape block is copied verbatim to the memory of the user-facing emulator that ZenZX is running on the front shop.
I don't have much evidence to show yet, as I'm ironing out a number of other new wrinkles, trying to deliver a more polished user interface than you have seen in the last week or so. The thing with screenshots when everything goes right is that they look exactly the same as when everything went wrong but you fixed the problem 🤣
Here they are, for now you have to take my promise that these games actually loaded very fast! 🤣
#ZXSpectrum #Spectrum #Speccy #retrogaming #retrocomputing #zenzx #emulator #golang #foss #z80
-
Help AI Coding Agents Write Up-To-Date Code With Modern Golang Skills
#GoLang #Ai #Community #Goland #Agentskills #Aiskills #Go #Opensource -
My new article, the Kronk SDK, is live.
3 important components:
→ prep: messages validated, templated and tokenized into a job
→ KV cache: restore the prefix, decode only what's new
→ engine: makes your tokens tick concurrently -
Retrying is easy; deciding is not. Between two HTTP attempts sit the real decisions: whether that failure was worth another try, whether the body has been released, whether it can be replayed at all, and who gets a say on the wait. In nurago, the httpretrier package makes each explicit, including why a 404 can be worth retrying on reads and how Retry-After is honoured with a ceiling.
-
Пачка PDF положила прод. Расследование багов в Go библиотеках
Мой сервис обрабатывает большой поток PDF от самых разных генераторов. В начале июня один‑единственный файл уложил его на 30 минут: HPA раздул поды до потолка, и все они наглухо повисли, 100% CPU, обработка стоит, очередь копится, алерты сыпятся пачками. Расследование в трёх актах: ложный подозреваемый, закомментированный panic и санитайзер, не знавший алфавит до конца.
https://habr.com/ru/articles/1073660/
#golang #pdf #ascii85 #парсинг_pdf #goroutine #отладка #open_source #порча_данных
-
Two call sites, identical three-line pattern for recovering an authenticated actor from context — one worked, one silently didn't, because the async signal dispatch wraps the context in stdlib types that drop the richer interface. Found by writing the test the plan called for.
-
#golang 1.17 saiu e trouxe umas modificações na linguagem bem vindas.
-
I've been sitting on iterations of a change proposal for a while now, and I finally had the time to put enough polish on it to make it publishable:
https://go-review.googlesource.com/c/website/+/819720
The idea is really simple: https://go.dev/tour, but you can create and serve tour content for your own project.
I think this scratches a necessary itch in developer journeys: something going beyond API reference and examples but rather cataloguing and articulating complete developer/user journeys.
