Related: The SymbOS operating system and graphical desktop for Amstrad CPC, MSX and some other Z80 machines was coded entirely manually - the first release was in 2006. https://www.symbos.org/
maybe they have a day job in a jurisdiction where their employer could claim ownership of the code if work was done during hours they paid for. it would be safer to scrub commit times if you’re worried about an aggressive employer.
This is the sort of thing I've wanted to write for a long time. Yes it looks like this is vibe coded but I'm glad this was made because it's cool to see what can be done, and it's interesting seeing how AI can be used as a compiler essentially given the output is assembly.
I'd be interested if the author would tell us more about what they did here and what went into the design and evolution, rather than the AI README.
Wow I did so many of those when i was 12 or around that age. Mostly I tried copying the Amiga Workbench on my +2A (the gray one).
Obviously at that age my knowledge of coding and window managers wasn't exactly deep and i mostly only had seen other OS from magazines. I don't think I even knew what 'drag-n-drop' was and was a bit confused at what the Trash bin should do (i loaded code from tapes).
I had fun playing around in Claude getting it to write 6502 assembler for the BBC Micro. It is fun to imagine what we could have built on those old machines with these new coding agents! But it is kind of hollow isn't it.
I think it's an issue for hobby projects. The other day I had a neat idea, looked into it and realized I would not have time to do it but still wanted to use it so I vibe coded it over an evening and there it was. But the code is not mine, I feel bad about it, it's completely hollow, I wish I had the time to do it properly. I'm glad I'm still hand coding my main hobby projects to avoid that.
Not for me. I do like having an agent at my disposition that accelerates the way into making those little experiments a reality.
A sloppy reality? Maybe. But It's just tinkering, there's no other use case for this outside of saying "So this can be done, huh? Okay time to go to for a walk".
While it's totally respectable to treat your code as your personal zen garden, I like the idea of having a highway where I can make reality anything that comes from my imagination, and also having time for family, friends, work and exercising out of sedentarism.
Thats your life and your opinion which you are fully entitled to, but dont make the mistake of thinking your life and opinion is better than anyone elses. It suits you, thats whats important.
Designing a table and letting somebody else build it can be enjoyable, too.
There are plenty of people enjoying designing, for example people who 3D print objects they design, or people designing PCBs or even entire gadgets but outsourcing production.
With LLMs, I guess a factor is how much direction you give the machine. “Build me a graphical desktop” likely isn’t very enjoyable, but I can see co-working with a LLM being enjoyable. Examples
- think of some novel UI interaction, and let the LLM code it
- spending hours to speed up the GUI or to make it use less memory
INHO the only unsatisfactory part for this "explorative" work is that you never really get into the flow since the LLM just takes too long between interactions (sometimes minutes). That's long enough to prevent from getting into the flow, but not long enough to focus on something else in the meantime.
Knowing your limitations of building, but being good at designing and watching somebody/something else realise your vision is incredibly satisfying.
I see it like 3D printing. Nobody can extrude molten plastic out of their bodies to make things, but the skill of designing the construction well and then watch the machine execute it is certainly a good feeling. I dont really see how this is different to designing some software verbally and prompting an ai to build it for you.
I have coded big projects manually for a long time. Being able to get ai to do it, then step back and marvel at knowing how much work that would have taken manually is very satisfying.
You can say the same for building computers. You didn't actually "built" a computer from the ground up. You just bought the pre-made hardware and plugged it in the places that are made to be easily pluggable.
Everything in tech is about standing in the shoulders of what came before.
At least when plugging a computer together I know who built the components. When building with LLMs I have no idea who actually wrote the code snippets that are thrown into the mixer ;)
> If you've never done anything for yourself, usually with your own hands, you don't understand the pleasure and satisfaction that comes from doing it.
That’s an absurd thing to say.
Doesn’t matter what “AI” feels or doesn’t feel. AI is a tool. You can derive as much pleasure from having an ideia, planning it, working on it from a higher level, and seeing it come to life as you do when you get down and dirty with it and do it from the low level up.
You are arguing against a very well known phenomenon. Technical people often avoid getting promoted to management precisely because they love doing the thing themselves. Despite the higher potential for impact in a management position, losing the detailed view of a practitioner is a real loss. This phenomenon is less obvious in big tech because there are so many people who really wanted to be managers the whole time, but had to be engineers first or never really cared about the work, but want a promotion for the better pay.
You either replied to the wrong comment or didn’t and proved my point exactly: some people like the technical low level approach, others prefer the higher level architectural work.
There’s space for both and there’s a need for both.
It's not absurd if you've actually done these things. I can only conclude from your response that you have not, so you don't know what it's like, therefore you don't know what the rest of us talking about.
Well, given that you are selfishly and arrogantly trying to set universal boundaries on what constitutes labour and effort, and what qualifies as “work” based on your feelings alone, then it seems fairly on brand for you to go about assuming things about people you don’t know from atom.
So you do you.
Go have fun bringing other people’s work down so you can feel better about yourself.
I hate the fact there is more discussion on things on HN about whether or not its vibe coded than the actual merits of the project itself. I really dont understand peoples attitude of immediately turning off something once they know ai is involved. These people are going to become pretty conflicted when somebody finally vibe codes some software they really like or have wanted forever.
As far as this project goes, the spectrum was the computer of my youth, and seeing this and getting to mess around with it brings my heart joy and my mind lots of nostalgic thoughts. Thanks for sharing!
I am going to give you my two cents on why this is the case, at least for me.
The reason I am in these spaces where people can posts things like "I created X..." or "I built X...", is because I want to learn from people that are much better engineers than I am.
I normally would skip a post of the kind "I built X", X being something simple that I am familiar with, because if I can do that too, there is not much value in spending my time going through an explanation on how you built it.
However, when the X you built is something really cool that I have not the slightest idea of how to build myself, I will take the time to explore your ideas, your code, your comments, and learn from you.
Clearly, up until very recently, I thought, if you built something really cool that I would not know where to even start with, you had something (knowledge, experience) that I lacked and I could learn from. You took the time to explain to others how you came up with that X, and I will take the time to ingest it and learn from it. I have learnt to be really appreciative of people that took the time to show others the things they make, and their thought process, insights, etc...
Please note that up until here, the WHAT you built is irrelevant. I don't care if it is a weather station you built in a makerspace, a new language compiler I will never use or a rendering engine for some kind of nonsense. What adds me value is not the what, but the how you made it. That is where my potential learnings are.
Fast forward to now, if what you did was spend a couple of hundred bucks prompting an LLM and generated a convoluted codebase that it is a royal Paine to look at as it does not really follow clear train of thought, and readme with Claude and uploaded it to GitHub to show off, I don't think I have much to learn from you.
I can also do that. The fact that you did that with a specific WHAT that didn't occur to me, is a curiosity at best. So now it is on me, to actually open the GitHub repo, realise that probably you have absolutely no idea how this even works either because it is a 100% intent-based generated codebase, be disappointed, and move on to the next post.
After going through that cycle 75 times a day, yes, I am a bit tired of vibe slop, even if the outcome X is good.
5 years ago, a post like this, would truly have been a work of love over months of someone's effort, and we could have learnt tons from the OP. Now, I am afraid that is not case. Now my thinking is, yep, nice project dude. Can't be bothered to open it. If I ever need one of this, I'll prompt it myself into existence, and I will learn probably very little in that process. Probably like you did too.
Long-form comments in the code are AI-written too, so I assume the whole thing is vibecoded. I guess my question is why. This is obviously not a piece of software anyone will ever use. If the author didn't do this for themselves - to learn, to show off their skills - then why bring it to life?
In business, there's this saying that "when a metric becomes a target, it ceases to be a good metric". I guess LLMs also make that true for hobby projects that used to make up a good portion of HN. We'd celebrate a project like that not because it's useful, but because it's a triumph of human ingenuity and a celebration of a personal achievement for the author. But now, it isn't, so is it still something we ought to celebrate?
Like many things in life, the answer is just "because I want to" and "because I can". Not everything has to be a linear progression or a level-up mechanic like a mmorpg.
Sometimes you want to create something out of creativity and you like seeing it done. The same way a painter wants to create something, not to show off skills, not to linearly progress onto something, but because they like making something out of nothing.
Well it’s more like commissioning art than making art yourself right? You want a painting of some specific thing to exist, so you find an artist you like and pay them to make it.
It’s not art, but I recently commissioned a translation of a manga that I wanted to read in English. The process was very similar to working with an LLM, just more expensive and the turn length was longer (and of course the output quality is much higher than an LLM generated scanlation would be at this point in time). I would pay for a chapter, he would send me a draft, we would go back and forth iterating on romanization and fixing typos until I was happy, then we’d move onto the next chapter. I achieved my goal of having the manga readable in English when it wasn’t before, but I wouldn’t call it my project.
I don't buy into the AGI commercial hype, and I treat LLMs as nothing more than pseudo-random text generators.
It just happens that at certain size the flow of words look a lot like "reasoning" because of the emergence phenomena (https://en.wikipedia.org/wiki/Emergence). But they do not have a theory of mind, they can't visualize and they do not have a sense of purpose.
A very significant difference is that AIs are programs, not people.
Perhaps it might be because i don't use any cloud LLMs, but the LLMs i use are all just data for a program running on my computer just like any other program and i don't really see them as any different than running -say- Bison to write a lexer or whatever (sure, Bison gives you the same output for the same input, but that is because LLM inference engines just add some randomness in the mix as that works better for the overall output - again, not any different than, say, rendering a 3D scene with a pathtracer that takes random samples: same input, different output -- or really any other thing that involves randomness).
That the combo of an LLM inference engine and weights kinda writes like a human and works with text in natural languages doesn't mean it is any different than any other piece of software.
I mean, i don't know about you but personally i'm not a fan of the idea of commissioning GCC to compile my code or Awk to process my text - even if i suspect there are business people out there who would love it :-P
I personally don't mind cloud LLMs as long as I'm aware of what's being sent to the internet.
I was thinking that it's a new thing for our field for such products only to be available behind a paid service. Before LLMs, there was always a local version of a product that worked just fine but with less capacity. Say, amazon vs local kubernetes, or CGI machines at Disney vs local Blender.
But on many other fields is normal for that to happen. Blacksmiths don't usually have a small steel furnace in their homes. Nurses don't buy a personal version of a CT Scanner to practice at home.
You really can’t see a difference between what Bison and GCC do and what an LLM does? You cannot tell GCC “I want a ZX Spectrum GUI” and get a working result.
The difference is that you'll get a different "ZX Spectrum GUI" each time with an LLM, but the same result with a compiler.
The actual work in both cases is not to write the source code, but to figure out and describe exactly what you want. In one case (traditional programming) this specificion happens directly in non-ambigious source code, in the other case (steering an LLM) you specify via an imprecise human language.
Quite often the human language specification is actually "good enough" to get what you wanted, but the more you need to go into specific details, the more the difference to traditional coding disappears.
Why not? The author wanted it, and had wanted it for about four decades since trying and failing as a child due to the difficulty of the task. If you’re in a certain frame of mind, then “why bring it to life?” can be directed at any kind of cultural work to negate it out of existence.
You're only addressing one half of my argument. The answer to this is obvious: the default state is that things don't get done unless we have a reason. So there is a motivation at play and it's perfectly OK to inquire about it, especially if the author appears to be cagey about how the project came to be. If your answer is "it was the author's childhood dream", fair.
But that brings me to the second half of the argument: I think we upvote this article in large part because of the historical association of a "crazy 8-bit software project" with "something that took perseverance and skill and our community should reward it". That link is severed now.
> The default state is that things don't get done unless we have a reason.
What about art? People make art and inventions just for the hell of it and to satisfy come itch. Whether or not other people then like it or find it useful is subjective and up to the individual. IMO taking away peoples right to make stuff for no reason and enjoy doing it is to take away our humanity.
I upvoted the article because it brought me some nostalgia and entertained me for a bit while I played with it and knowing how to code a spectrum myself, marvelled at the complexity of the code and the project itself. Maybe people have more reasons to enjoy things than your narrow viewpoint allows for?
What’s interesting about the project might no longer be ‘wow, someone figured out how to do that, I guess they must have a MASSIVE BRAIN’, but we can still wonder at the fact that the hardware can be made to do such a thing.
If someone finds an interesting shiny pebble and shows it to you, is your reaction to say ‘what do you want, a round of applause? You didn’t make that rock’
Can’t you just appreciate the shiny pebble someone went out of their way to find?
> But that brings me to the second half of the argument: I think we upvote this article in large part because of the historical association of a "crazy 8-bit software project" with "something that took perseverance and skill and our community should reward it". That link is severed now.
There’s the problem: you are assuming everyone else thinks in elitist terms like you. It still is a crazy 8-bit software project. It still rather impressive and fun to see.
Your “historical reason” reads a lot more like whining than anything else and it does come across as a display of insecurity.
AI is just a freaking tool. The dev used to tool to bring his vision to life. That’s the extent of it. Stop making such a fuss over something that quite literally was just made for fun.
Let people have fun in peace. Let people enjoy things in peace.
Yeah, I think this is interesting independently of how it was made, because it reveals a kind of "what could have been" alternative history. It's fun to imagine a past where the Speccy got a desktop, and it's fun to see what it could have looked like running on real hardware (or on an emulator).
> I guess my question is why. This is obviously not a piece of software anyone will ever use.
My best theory would be it's something that was built as like a novelty/proof of concept, that a current state of the art LLM can do tedious tasks like assembly on a ridiculously old/low resource platform and turn out something that actually looks coherent. I don't personally know a lot of people who enjoy building large things in assembly but LLMs aren't bothered by doing tedious tasks. Due to the tiny size of the thing it can probably very rapidly iterate on "this doesn't work, change a thing, run it again" thousands of times.
If you’re familiar with the way in which documentation artifacts like this fall out of a Claude project, you will recognize that every place where Claude says ‘this changes everything’ or ‘this is the load bearing insight’ most likely resulted from a human looking at what Claude had done, and redirecting it towards a more fruitful line of inquiry. When Claude gets ‘excited’ about a thing like ‘we figured out which clock measurement approach helps us actually optimize performance’ - excited enough to explain it in this level of detail - it usually results from the user pulling Claude out of a rabbit hole where it was going about things the wrong way.
This sounds like you have only had a superficial contact with LLMs. They do a lot of mechanical work, but "a bit of prompting" is not how they are used for something like this.
> If the author didn't do this for themselves - to learn, to show off their skills - then why bring it to life?
Isn’t wanting a thing to exist reason enough?
It’s a bit like seeing someone post an instagram photo of them eating a cake they made, and saying ‘why? Why did you make this cake? Are you trying to learn, or show off your skills?’
Maybe they.. just wanted to eat a cake?
I swear the instagram ‘look at me’ culture has broken people’s ability to just do a thing because they can.
> If the author didn't do this for themselves - to learn, to show off their skills - then why bring it to life?
Why not?
What if the person just wanted to see if it could be done and how it would look like, but wasn’t interested in the nitty-gritty bits in between?
There’s so much elitism and “you can’t sit with us” energy here that I feel like I just lost 4 decades of my life just reading this—and not in a good way.
Yeah, there certainly is AI slop. But there’s also very good uses of AI. So how about we stop shaming people for just building things they wanted to build using the tools at their disposal?
> But now, it isn't, so is it still something we ought to celebrate?
Why isn’t it? Don’t “having an idea and acting on it” count anymore? You guys seem so utterly insecure it’s depressing.
No, you did not make the pizza, but you have the wherewithal to order it, to think of what you wanted. You don’t get to claim you made the pizza, but you made the order for your pizza dinner.
And honestly, if you have any experience at all working with AIs, then you should know very well that it is not anything like ordering a pizza.
I can guarantee you the author did work on it, plan it, rethought parts of it, specced it out, tested it, and worked a lot to make it come to life. So no, you wouldn’t have made the pizza because all you had to do was order it, but you cannot just say “write a GUI for the ZX Spectrum” and wait at your table for it to come toasty out of the oven.
Bad analogy. Bad way of thinking. Bad behaviour. All on you.
I think all AI projects should die, but if your question is aimed as to "why to publish it on github", then why not? Others could look at the code and learn from it (perhaps); and it is easier to distribute it that way too, in many cases. So I don't fully agree with the assumption that it would be automatically useless. Personally I won't use AI slop projects. It already annoys me to no ends that AI skynet successfully took over ruby development. I don't feel like even giving any feedback, as a few ruby devs such as Hiroshi Shibata, only interact with other beings via AI slop spam via claude; suddenly newly gained "perfect english language skills". It is all so fake now when AI infiltrates projects.
Not all AI-assisted projects are AI-slop. The fact that you think so only tells me that you’re deeply insecure about your knowledge of a subject that you’re interested in.
Thinking of and expressing the functionality of the thing might be the labor of love for this person. Their definition of labor doesn't have to be yours.
I don’t think there’s ever been a more accurate and appropriate moment to say: that sounds like a you problem.
If you think computer science is only about manually writing lines of code yourself then goodness me you have SO MUCH to learn.
> Was this, then, done to impress others rather than enrich the coders skills and experience?
So coding is only valid when it “enriches the coders skills and experience”? How do you define those? Better yet, WHO is defining those? Are you so narrow minded and decidedly contrarian that you simply refuse to think of any other reason the dev might’ve done this for? I don’t wanna tell you you need to touch grass but goodness me you really ought to consider opening your mind to the fact that you are not the centre of the universe.
> The futuristic equivalent of pressing the “demo” button on old electronic keyboard and pretending to play
These two things do not equate in the slightest and the fact that you think they do is utterly depressing.
Not the parent, but it reads a lot like written by AI. It has that typical breathless style that's exhausting just from reading.
Also, looking at the code, the whole project looks vibe coded, no human would write such comments. Everything in a single git commit also looks "suspicious". It's cool that LLMs can write Z80 asm now, but yeah "labour of love"... tsk tsk tsk...
When your manager gives you the task of building a complex product with a more or less vague "do what I mean" specification, and once a week shows up for 2 minutes to nudge you into a different direction, would you agree when the manager calls this his own "labour of love" when you did 99% of the actual work and thousands of micro-decisions along the way that your manager didn't even know had to be made?
I use claude at work, I have to read its wall of text all day long, it's instantly recognizable. Like many others I'm developing an aversion toward it. The OP's project is pretty cool but I just couldn't read the readme.
I wonder: was there a time when using a compiler was considered cheating? "Real men" code everything in ASM!
I do recall a whole era when using a GUI was considered cheating and denigrated as a "point and drool" interface (a play on "point and click").
Is using a combine cheating in farming? Is a nail gun or using prefab wall sections cheating in home construction? Is a 3D printer cheating in fabrication? If someone prints something with a 3D printer, do we say "you didn't make that, the printer did!"
I find it weird for people who like technology to be so averse to tools that automate labor since that is literally what all technology is, and a tool to automate intellectual labor is literally what a computer is. A machine is a thing whose purpose is to provide leverage to amplify human effort and more rapidly realize human intent in some domain.
Maybe it comes from a category error. AI is kind of a hand-wavey term, since most people think it means the thing is sentient. It's not. It has zero intent, zero motivation, zero ability to choose anything not already in its training data, and it will go precisely where its context window (and training data) guide it. It's a tool, a machine, and like any other machine it is set in motion by the user and guided by the user. The "choices" it makes are latent in its data or structure, or implied by its prompt. (Yes sometimes they can be surprising, but that's true of all complex machines.)
Actual sentient AI does not exist. It might someday but it does not today. I suspect it requires a very different kind of system with continuous learning, dynamical state, and feedback, and a goal function tied somehow to thermodynamics in the real physical world the way ours is, but that's pure hypothesis on my part. We don't even have rigorous definitions for such things.
For me the red line is obviously AI generated readmes. If the author can't even be arsed to write obviously human facing text by himself I immediately lose all interest too.
The critical difference I think is deterministic vs non-deterministic. A compiler isn’t the correct comparison, it’s reading out your desired specs to a team member who does the actual engineering work.
> it’s reading out your desired specs to a team member who does the actual engineering work
Congratulations, you just discovered ”delegating”. I hope you don’t have anyone reporting to you at the moment because if this simple concept sounds demeaning to you… wow.
Can anyone suggest a simple high-level graphical desktop (perhaps written in a mix of assembly and C) that comes with good documentation, or even an associated textbook?
It’s Claude’s earnestness that’s so disingenuous in this kind of write up. This voice Claude has where it believes the work is important and deserves to be taken seriously, and where it takes ever part of the process where it has to adjust its approach because of a thing it figured out as a great insight which is incredibly valuable and that people should be made aware of…
I feel like vibecoded projects need Claude to pick up on a sense of ‘this is just me messing around’, and a project like this where there does appear to be genuine digging into the art of performance tuning Z80 assembly needs Claude to understand ‘this is impractical hacking for hacking’s sake not groundbreaking research’
I don’t have a problem with projects which are, essentially ‘Claude and I burned a lot of tokens for giggles to see just how far you can push something’. But the write up needs to reflect that spirit.
That's an excellent way of putting it. It's like an enthusiastic student who points out all the really smart stuff it did so that the teacher will be impressed and give it a gold star...which is basically what its RL environments were.
You can do a lot with custom agent prompts. Just telling Claude ‘this is only a personal project, we’re messing around here’ changes its tone somewhat already. It’s still Business Claude, but more Casual Friday Claude, less Monday Morning Standup Meeting Claude.
There's also a vast gulf between 'startup culture' and 'Enterprise engineering'. But the general sense of "this voice is for a specific context, and it is not 'weekend ZX Spectrum hacking project'", is correct.
Sure. If I ask my roommate to go make me a ham sandwich without mayo, I expect them to observe basic hygiene practices, too, but I am comfortable with them just handing me the sandwich and saying ‘there on you go - sandwich’ rather than “Here is an edible sandwich: No mayo, no lettuce – just bread and ham. And the load-bearing insight that makes it work: it doesn’t use the open ham from the fridge that was past its use-by date. That one decision changed everything.”
There is practically no other choice on a Z80. C compilers really don't like the Z80 ISA and create both slow and bloated output, at least compared to manually written asm. And on top, you can do many optimization tricks in assembly that simply are not possible in a high level language (self-modifying code, jumping into the middle of an instruction, etc...).
Forth might work better than C, but tbh, assembly code is more straightforward and easier to read than Forth ;)
Don't know, but AFAIK this wasn't a popular programming language on home computers in the 1980s (from what I've seen, the popular non-asm languages were usually BASIC, Forth and Pascal, even C was kinda rare).
I believe most of the 8bit microcontrollers from this era have no good optimizing compilers that get close to what competent practitioners achieve with assembly. I think it has to do with having complex addressing modes making the C stack fairly inefficient.
For an 8 bit Z80 based hardware project like this, assembly is a valid choice. The reason is performance. You'll lose significant performance with a compiler or interpreter.
The quickest way to redraw a screen or otherwise copy a memory region on Spectrum of is to use POP/PUSH instructions while flipping the stack pointer. Good luck getting that with C.
assembly is the only choice. The Z80 processor is a twisty collection of registers, none alike. It is pretty much the opposite of what a, for example, C compiler is looking for.
In fact C compilers are _notoriously_ bad at producing code for the Z80.
Related: The SymbOS operating system and graphical desktop for Amstrad CPC, MSX and some other Z80 machines was coded entirely manually - the first release was in 2006. https://www.symbos.org/
Of course for the Commodore 64 the GEOS desktop was already released as a commercial product in 1986. https://en.wikipedia.org/wiki/GEOS_(8-bit_operating_system)
> Three rules that earned their place:
> One commit per verified piece of work, with the acceptance numbers in the commit message
Project: One single commit: "ZX Desk, first release"
???
Maybe Claude one-shotted the project ;)
maybe they have a day job in a jurisdiction where their employer could claim ownership of the code if work was done during hours they paid for. it would be safer to scrub commit times if you’re worried about an aggressive employer.
Would love to see a corporation claiming ownership of a ZX Spectrum GUI, that would be performance art
This is the sort of thing I've wanted to write for a long time. Yes it looks like this is vibe coded but I'm glad this was made because it's cool to see what can be done, and it's interesting seeing how AI can be used as a compiler essentially given the output is assembly.
I'd be interested if the author would tell us more about what they did here and what went into the design and evolution, rather than the AI README.
Wow I did so many of those when i was 12 or around that age. Mostly I tried copying the Amiga Workbench on my +2A (the gray one).
Obviously at that age my knowledge of coding and window managers wasn't exactly deep and i mostly only had seen other OS from magazines. I don't think I even knew what 'drag-n-drop' was and was a bit confused at what the Trash bin should do (i loaded code from tapes).
Good times i guess :)
I had fun playing around in Claude getting it to write 6502 assembler for the BBC Micro. It is fun to imagine what we could have built on those old machines with these new coding agents! But it is kind of hollow isn't it.
I think it's an issue for hobby projects. The other day I had a neat idea, looked into it and realized I would not have time to do it but still wanted to use it so I vibe coded it over an evening and there it was. But the code is not mine, I feel bad about it, it's completely hollow, I wish I had the time to do it properly. I'm glad I'm still hand coding my main hobby projects to avoid that.
Not for me. I do like having an agent at my disposition that accelerates the way into making those little experiments a reality. A sloppy reality? Maybe. But It's just tinkering, there's no other use case for this outside of saying "So this can be done, huh? Okay time to go to for a walk".
While it's totally respectable to treat your code as your personal zen garden, I like the idea of having a highway where I can make reality anything that comes from my imagination, and also having time for family, friends, work and exercising out of sedentarism.
Thats your life and your opinion which you are fully entitled to, but dont make the mistake of thinking your life and opinion is better than anyone elses. It suits you, thats whats important.
It is fun to imagine what we could have built on those old machines with these new coding agents! But it is kind of hollow isn't it.
It's the difference between building a table yourself and telling someone else to build a table for you.
If you've never done anything for yourself, usually with your own hands, you don't understand the pleasure and satisfaction that comes from doing it.
And since "AI" isn't human, it can't know that feeling, either.
Designing a table and letting somebody else build it can be enjoyable, too.
There are plenty of people enjoying designing, for example people who 3D print objects they design, or people designing PCBs or even entire gadgets but outsourcing production.
With LLMs, I guess a factor is how much direction you give the machine. “Build me a graphical desktop” likely isn’t very enjoyable, but I can see co-working with a LLM being enjoyable. Examples
- think of some novel UI interaction, and let the LLM code it
- spending hours to speed up the GUI or to make it use less memory
INHO the only unsatisfactory part for this "explorative" work is that you never really get into the flow since the LLM just takes too long between interactions (sometimes minutes). That's long enough to prevent from getting into the flow, but not long enough to focus on something else in the meantime.
This.
Knowing your limitations of building, but being good at designing and watching somebody/something else realise your vision is incredibly satisfying.
I see it like 3D printing. Nobody can extrude molten plastic out of their bodies to make things, but the skill of designing the construction well and then watch the machine execute it is certainly a good feeling. I dont really see how this is different to designing some software verbally and prompting an ai to build it for you.
If you don't know how the artefact you ordered works you haven't built it in any meaningful sense of the word.
I have coded big projects manually for a long time. Being able to get ai to do it, then step back and marvel at knowing how much work that would have taken manually is very satisfying.
You can say the same for building computers. You didn't actually "built" a computer from the ground up. You just bought the pre-made hardware and plugged it in the places that are made to be easily pluggable.
Everything in tech is about standing in the shoulders of what came before.
At least when plugging a computer together I know who built the components. When building with LLMs I have no idea who actually wrote the code snippets that are thrown into the mixer ;)
> If you've never done anything for yourself, usually with your own hands, you don't understand the pleasure and satisfaction that comes from doing it.
That’s an absurd thing to say.
Doesn’t matter what “AI” feels or doesn’t feel. AI is a tool. You can derive as much pleasure from having an ideia, planning it, working on it from a higher level, and seeing it come to life as you do when you get down and dirty with it and do it from the low level up.
Let’s talk like adults here. Please.
You are arguing against a very well known phenomenon. Technical people often avoid getting promoted to management precisely because they love doing the thing themselves. Despite the higher potential for impact in a management position, losing the detailed view of a practitioner is a real loss. This phenomenon is less obvious in big tech because there are so many people who really wanted to be managers the whole time, but had to be engineers first or never really cared about the work, but want a promotion for the better pay.
You either replied to the wrong comment or didn’t and proved my point exactly: some people like the technical low level approach, others prefer the higher level architectural work.
There’s space for both and there’s a need for both.
That’s an absurd thing to say.
It's not absurd if you've actually done these things. I can only conclude from your response that you have not, so you don't know what it's like, therefore you don't know what the rest of us talking about.
> I can only conclude
Well, given that you are selfishly and arrogantly trying to set universal boundaries on what constitutes labour and effort, and what qualifies as “work” based on your feelings alone, then it seems fairly on brand for you to go about assuming things about people you don’t know from atom.
So you do you.
Go have fun bringing other people’s work down so you can feel better about yourself.
I hate the fact there is more discussion on things on HN about whether or not its vibe coded than the actual merits of the project itself. I really dont understand peoples attitude of immediately turning off something once they know ai is involved. These people are going to become pretty conflicted when somebody finally vibe codes some software they really like or have wanted forever.
As far as this project goes, the spectrum was the computer of my youth, and seeing this and getting to mess around with it brings my heart joy and my mind lots of nostalgic thoughts. Thanks for sharing!
I am going to give you my two cents on why this is the case, at least for me.
The reason I am in these spaces where people can posts things like "I created X..." or "I built X...", is because I want to learn from people that are much better engineers than I am.
I normally would skip a post of the kind "I built X", X being something simple that I am familiar with, because if I can do that too, there is not much value in spending my time going through an explanation on how you built it.
However, when the X you built is something really cool that I have not the slightest idea of how to build myself, I will take the time to explore your ideas, your code, your comments, and learn from you.
Clearly, up until very recently, I thought, if you built something really cool that I would not know where to even start with, you had something (knowledge, experience) that I lacked and I could learn from. You took the time to explain to others how you came up with that X, and I will take the time to ingest it and learn from it. I have learnt to be really appreciative of people that took the time to show others the things they make, and their thought process, insights, etc...
Please note that up until here, the WHAT you built is irrelevant. I don't care if it is a weather station you built in a makerspace, a new language compiler I will never use or a rendering engine for some kind of nonsense. What adds me value is not the what, but the how you made it. That is where my potential learnings are.
Fast forward to now, if what you did was spend a couple of hundred bucks prompting an LLM and generated a convoluted codebase that it is a royal Paine to look at as it does not really follow clear train of thought, and readme with Claude and uploaded it to GitHub to show off, I don't think I have much to learn from you.
I can also do that. The fact that you did that with a specific WHAT that didn't occur to me, is a curiosity at best. So now it is on me, to actually open the GitHub repo, realise that probably you have absolutely no idea how this even works either because it is a 100% intent-based generated codebase, be disappointed, and move on to the next post.
After going through that cycle 75 times a day, yes, I am a bit tired of vibe slop, even if the outcome X is good.
5 years ago, a post like this, would truly have been a work of love over months of someone's effort, and we could have learnt tons from the OP. Now, I am afraid that is not case. Now my thinking is, yep, nice project dude. Can't be bothered to open it. If I ever need one of this, I'll prompt it myself into existence, and I will learn probably very little in that process. Probably like you did too.
It _does_ look really cool, genuinely, but calling it a "labour of love" and then having AI write the readme/docs seems conflicting.
Long-form comments in the code are AI-written too, so I assume the whole thing is vibecoded. I guess my question is why. This is obviously not a piece of software anyone will ever use. If the author didn't do this for themselves - to learn, to show off their skills - then why bring it to life?
In business, there's this saying that "when a metric becomes a target, it ceases to be a good metric". I guess LLMs also make that true for hobby projects that used to make up a good portion of HN. We'd celebrate a project like that not because it's useful, but because it's a triumph of human ingenuity and a celebration of a personal achievement for the author. But now, it isn't, so is it still something we ought to celebrate?
> then why bring it to life?
Like many things in life, the answer is just "because I want to" and "because I can". Not everything has to be a linear progression or a level-up mechanic like a mmorpg.
Sometimes you want to create something out of creativity and you like seeing it done. The same way a painter wants to create something, not to show off skills, not to linearly progress onto something, but because they like making something out of nothing.
Well it’s more like commissioning art than making art yourself right? You want a painting of some specific thing to exist, so you find an artist you like and pay them to make it.
It’s not art, but I recently commissioned a translation of a manga that I wanted to read in English. The process was very similar to working with an LLM, just more expensive and the turn length was longer (and of course the output quality is much higher than an LLM generated scanlation would be at this point in time). I would pay for a chapter, he would send me a draft, we would go back and forth iterating on romanization and fixing typos until I was happy, then we’d move onto the next chapter. I achieved my goal of having the manga readable in English when it wasn’t before, but I wouldn’t call it my project.
I don't buy into the AGI commercial hype, and I treat LLMs as nothing more than pseudo-random text generators.
It just happens that at certain size the flow of words look a lot like "reasoning" because of the emergence phenomena (https://en.wikipedia.org/wiki/Emergence). But they do not have a theory of mind, they can't visualize and they do not have a sense of purpose.
Agents are not people.
A very significant difference is that AIs are programs, not people.
Perhaps it might be because i don't use any cloud LLMs, but the LLMs i use are all just data for a program running on my computer just like any other program and i don't really see them as any different than running -say- Bison to write a lexer or whatever (sure, Bison gives you the same output for the same input, but that is because LLM inference engines just add some randomness in the mix as that works better for the overall output - again, not any different than, say, rendering a 3D scene with a pathtracer that takes random samples: same input, different output -- or really any other thing that involves randomness).
That the combo of an LLM inference engine and weights kinda writes like a human and works with text in natural languages doesn't mean it is any different than any other piece of software.
I mean, i don't know about you but personally i'm not a fan of the idea of commissioning GCC to compile my code or Awk to process my text - even if i suspect there are business people out there who would love it :-P
I personally don't mind cloud LLMs as long as I'm aware of what's being sent to the internet.
I was thinking that it's a new thing for our field for such products only to be available behind a paid service. Before LLMs, there was always a local version of a product that worked just fine but with less capacity. Say, amazon vs local kubernetes, or CGI machines at Disney vs local Blender.
But on many other fields is normal for that to happen. Blacksmiths don't usually have a small steel furnace in their homes. Nurses don't buy a personal version of a CT Scanner to practice at home.
But that's a discussion for another time I guess.
You really can’t see a difference between what Bison and GCC do and what an LLM does? You cannot tell GCC “I want a ZX Spectrum GUI” and get a working result.
The difference is that you'll get a different "ZX Spectrum GUI" each time with an LLM, but the same result with a compiler.
The actual work in both cases is not to write the source code, but to figure out and describe exactly what you want. In one case (traditional programming) this specificion happens directly in non-ambigious source code, in the other case (steering an LLM) you specify via an imprecise human language.
Quite often the human language specification is actually "good enough" to get what you wanted, but the more you need to go into specific details, the more the difference to traditional coding disappears.
>Why bring it to life?
Why not? The author wanted it, and had wanted it for about four decades since trying and failing as a child due to the difficulty of the task. If you’re in a certain frame of mind, then “why bring it to life?” can be directed at any kind of cultural work to negate it out of existence.
> Why not?
You're only addressing one half of my argument. The answer to this is obvious: the default state is that things don't get done unless we have a reason. So there is a motivation at play and it's perfectly OK to inquire about it, especially if the author appears to be cagey about how the project came to be. If your answer is "it was the author's childhood dream", fair.
But that brings me to the second half of the argument: I think we upvote this article in large part because of the historical association of a "crazy 8-bit software project" with "something that took perseverance and skill and our community should reward it". That link is severed now.
> The default state is that things don't get done unless we have a reason.
What about art? People make art and inventions just for the hell of it and to satisfy come itch. Whether or not other people then like it or find it useful is subjective and up to the individual. IMO taking away peoples right to make stuff for no reason and enjoy doing it is to take away our humanity.
I upvoted the article because it brought me some nostalgia and entertained me for a bit while I played with it and knowing how to code a spectrum myself, marvelled at the complexity of the code and the project itself. Maybe people have more reasons to enjoy things than your narrow viewpoint allows for?
What’s interesting about the project might no longer be ‘wow, someone figured out how to do that, I guess they must have a MASSIVE BRAIN’, but we can still wonder at the fact that the hardware can be made to do such a thing.
If someone finds an interesting shiny pebble and shows it to you, is your reaction to say ‘what do you want, a round of applause? You didn’t make that rock’
Can’t you just appreciate the shiny pebble someone went out of their way to find?
> But that brings me to the second half of the argument: I think we upvote this article in large part because of the historical association of a "crazy 8-bit software project" with "something that took perseverance and skill and our community should reward it". That link is severed now.
There’s the problem: you are assuming everyone else thinks in elitist terms like you. It still is a crazy 8-bit software project. It still rather impressive and fun to see.
Your “historical reason” reads a lot more like whining than anything else and it does come across as a display of insecurity.
AI is just a freaking tool. The dev used to tool to bring his vision to life. That’s the extent of it. Stop making such a fuss over something that quite literally was just made for fun.
Let people have fun in peace. Let people enjoy things in peace.
Yeah, I think this is interesting independently of how it was made, because it reveals a kind of "what could have been" alternative history. It's fun to imagine a past where the Speccy got a desktop, and it's fun to see what it could have looked like running on real hardware (or on an emulator).
Precisely! Anyone who knows the hardware should understand how interesting this project is, regardless of how it came to be.
It’s just fun.
Even a cursory flick through the GitHub page until you reach “Why” shows that to be the answer.
> I guess my question is why. This is obviously not a piece of software anyone will ever use.
My best theory would be it's something that was built as like a novelty/proof of concept, that a current state of the art LLM can do tedious tasks like assembly on a ridiculously old/low resource platform and turn out something that actually looks coherent. I don't personally know a lot of people who enjoy building large things in assembly but LLMs aren't bothered by doing tedious tasks. Due to the tiny size of the thing it can probably very rapidly iterate on "this doesn't work, change a thing, run it again" thousands of times.
For the fun of it. Why not. And otoh, isn't it impressive that llm's can do it.
AI assisted or not, you have no idea how much of his personal effort went into the project.
Nothing else than a bit of prompting went in to this.
If you’re familiar with the way in which documentation artifacts like this fall out of a Claude project, you will recognize that every place where Claude says ‘this changes everything’ or ‘this is the load bearing insight’ most likely resulted from a human looking at what Claude had done, and redirecting it towards a more fruitful line of inquiry. When Claude gets ‘excited’ about a thing like ‘we figured out which clock measurement approach helps us actually optimize performance’ - excited enough to explain it in this level of detail - it usually results from the user pulling Claude out of a rabbit hole where it was going about things the wrong way.
I think you severely lack in domain knowledge if you think “nothing else than a bit of prompting went in to this”.
"A bit of prompting" is subjective, and can indeed take a lot of work to craft accurate prompts which produce genuinely useful output.
This sounds like you have only had a superficial contact with LLMs. They do a lot of mechanical work, but "a bit of prompting" is not how they are used for something like this.
How about the desire to steer LLMs to a point of their choosing? LLMs wouldn't do this by themselves...
> If the author didn't do this for themselves - to learn, to show off their skills - then why bring it to life?
Isn’t wanting a thing to exist reason enough?
It’s a bit like seeing someone post an instagram photo of them eating a cake they made, and saying ‘why? Why did you make this cake? Are you trying to learn, or show off your skills?’
Maybe they.. just wanted to eat a cake?
I swear the instagram ‘look at me’ culture has broken people’s ability to just do a thing because they can.
> If the author didn't do this for themselves - to learn, to show off their skills - then why bring it to life?
Why not?
What if the person just wanted to see if it could be done and how it would look like, but wasn’t interested in the nitty-gritty bits in between?
There’s so much elitism and “you can’t sit with us” energy here that I feel like I just lost 4 decades of my life just reading this—and not in a good way.
Yeah, there certainly is AI slop. But there’s also very good uses of AI. So how about we stop shaming people for just building things they wanted to build using the tools at their disposal?
> But now, it isn't, so is it still something we ought to celebrate?
Why isn’t it? Don’t “having an idea and acting on it” count anymore? You guys seem so utterly insecure it’s depressing.
If the author didn't do this for themselves - to learn, to show off their skills - then why bring it to life?
Likes. Clicks. Vanity. Being able to list GitHub on a resume.
The usual stuff we get from anything adjacent to A.I.
We went to the moon with slide rules. Now we boil the oceans for "likes."
What do you even mean by this?
Can’t things be made just for fun? Can’t people be proud of things they did for enjoyment only?
How is displaying a project on your GitHub “vanity”? Why shouldn’t they display it proudly? Why shouldn’t they put it on their resume?
Can’t people be proud of things they did for enjoyment only?
Absolutely. But he didn't do it. He asked Claude to do it for him.
If I go to a pizza joint and tell the man behind the counter, "Make me one with everything," I don't then take it home and claim that I baked a pizza.
No, you did not make the pizza, but you have the wherewithal to order it, to think of what you wanted. You don’t get to claim you made the pizza, but you made the order for your pizza dinner.
And honestly, if you have any experience at all working with AIs, then you should know very well that it is not anything like ordering a pizza.
I can guarantee you the author did work on it, plan it, rethought parts of it, specced it out, tested it, and worked a lot to make it come to life. So no, you wouldn’t have made the pizza because all you had to do was order it, but you cannot just say “write a GUI for the ZX Spectrum” and wait at your table for it to come toasty out of the oven.
Bad analogy. Bad way of thinking. Bad behaviour. All on you.
There's a tell in your response that lets me know you're a clanker.
Tell your creator that you failed in your task and should be deleted.
You will never be a real boy.
Oh wow now this is the biggest laugh I’ve had all day. Thank you for that.
You might want to rethink how well you think you can read people, because, as it turns out, it’s just not very well at all.
> why bring it to life?
I think all AI projects should die, but if your question is aimed as to "why to publish it on github", then why not? Others could look at the code and learn from it (perhaps); and it is easier to distribute it that way too, in many cases. So I don't fully agree with the assumption that it would be automatically useless. Personally I won't use AI slop projects. It already annoys me to no ends that AI skynet successfully took over ruby development. I don't feel like even giving any feedback, as a few ruby devs such as Hiroshi Shibata, only interact with other beings via AI slop spam via claude; suddenly newly gained "perfect english language skills". It is all so fake now when AI infiltrates projects.
You’ve officially reached the “you pesky kids get off my lawn” stage in your interest in computing.
Not all AI-assisted projects are AI-slop. The fact that you think so only tells me that you’re deeply insecure about your knowledge of a subject that you’re interested in.
[flagged]
Thinking of and expressing the functionality of the thing might be the labor of love for this person. Their definition of labor doesn't have to be yours.
Their labour didn’t involve coding. When we equate labour to creating a load of prompts then it feels hollow to me.
Was this, then, done to impress others rather than enrich the coders skills and experience?
The futuristic equivalent of pressing the “demo” button on old electronic keyboard and pretending to play
> it feels hollow to me
I don’t think there’s ever been a more accurate and appropriate moment to say: that sounds like a you problem.
If you think computer science is only about manually writing lines of code yourself then goodness me you have SO MUCH to learn.
> Was this, then, done to impress others rather than enrich the coders skills and experience?
So coding is only valid when it “enriches the coders skills and experience”? How do you define those? Better yet, WHO is defining those? Are you so narrow minded and decidedly contrarian that you simply refuse to think of any other reason the dev might’ve done this for? I don’t wanna tell you you need to touch grass but goodness me you really ought to consider opening your mind to the fact that you are not the centre of the universe.
> The futuristic equivalent of pressing the “demo” button on old electronic keyboard and pretending to play
These two things do not equate in the slightest and the fact that you think they do is utterly depressing.
Why do you say it's written by AI?
Not the parent, but it reads a lot like written by AI. It has that typical breathless style that's exhausting just from reading.
Also, looking at the code, the whole project looks vibe coded, no human would write such comments. Everything in a single git commit also looks "suspicious". It's cool that LLMs can write Z80 asm now, but yeah "labour of love"... tsk tsk tsk...
> but yeah "labour of love"... tsk tsk tsk...
What precludes this from being a labour of love, exactly?
I think some people prefer their labours of love to involve the expenditure of actual labour.
So planning, debugging, speccing, thinking, rethinking, designing, etc… do not count as labour?
Please, do give me a list of what constitutes labour.
When your manager gives you the task of building a complex product with a more or less vague "do what I mean" specification, and once a week shows up for 2 minutes to nudge you into a different direction, would you agree when the manager calls this his own "labour of love" when you did 99% of the actual work and thousands of micro-decisions along the way that your manager didn't even know had to be made?
That’s not even close to a valid analogy and I think (and hope) you know that. Because if you don’t… oof. You have a lot to learn.
I use claude at work, I have to read its wall of text all day long, it's instantly recognizable. Like many others I'm developing an aversion toward it. The OP's project is pretty cool but I just couldn't read the readme.
Claude’s written voice is so distinctive, anyone who has spent time working with Claude instantly recognizes it.
Which, if you think about it too hard, says something slightly profound and a little disturbing about identity…
I wonder: was there a time when using a compiler was considered cheating? "Real men" code everything in ASM!
I do recall a whole era when using a GUI was considered cheating and denigrated as a "point and drool" interface (a play on "point and click").
Is using a combine cheating in farming? Is a nail gun or using prefab wall sections cheating in home construction? Is a 3D printer cheating in fabrication? If someone prints something with a 3D printer, do we say "you didn't make that, the printer did!"
I find it weird for people who like technology to be so averse to tools that automate labor since that is literally what all technology is, and a tool to automate intellectual labor is literally what a computer is. A machine is a thing whose purpose is to provide leverage to amplify human effort and more rapidly realize human intent in some domain.
Maybe it comes from a category error. AI is kind of a hand-wavey term, since most people think it means the thing is sentient. It's not. It has zero intent, zero motivation, zero ability to choose anything not already in its training data, and it will go precisely where its context window (and training data) guide it. It's a tool, a machine, and like any other machine it is set in motion by the user and guided by the user. The "choices" it makes are latent in its data or structure, or implied by its prompt. (Yes sometimes they can be surprising, but that's true of all complex machines.)
Actual sentient AI does not exist. It might someday but it does not today. I suspect it requires a very different kind of system with continuous learning, dynamical state, and feedback, and a goal function tied somehow to thermodynamics in the real physical world the way ours is, but that's pure hypothesis on my part. We don't even have rigorous definitions for such things.
For me the red line is obviously AI generated readmes. If the author can't even be arsed to write obviously human facing text by himself I immediately lose all interest too.
The critical difference I think is deterministic vs non-deterministic. A compiler isn’t the correct comparison, it’s reading out your desired specs to a team member who does the actual engineering work.
> it’s reading out your desired specs to a team member who does the actual engineering work
Congratulations, you just discovered ”delegating”. I hope you don’t have anyone reporting to you at the moment because if this simple concept sounds demeaning to you… wow.
I just derived this exact line of thought from a different comment above so I’ve no idea why you’re getting downvoted for it.
Your analogies are completely non-sensical.
> Licence > > MIT, see LICENSE. Nothing here is derived from anyone else's code.
Right... Except the whole thing being generated by a model derived from everyone's code.
I'm not even sure I'm against licensing it as MIT but maybe stop with the ridiculous claims on top of that?
Sure are cute little pieces of history:
https://duckduckgo.com/?q=zx+spectrum&ia=images&iax=images
Can anyone suggest a simple high-level graphical desktop (perhaps written in a mix of assembly and C) that comes with good documentation, or even an associated textbook?
rio?
and there's a detailed write up
https://aryx.github.io/assets/pdfs/Windows-7.pdf
It’s Claude’s earnestness that’s so disingenuous in this kind of write up. This voice Claude has where it believes the work is important and deserves to be taken seriously, and where it takes ever part of the process where it has to adjust its approach because of a thing it figured out as a great insight which is incredibly valuable and that people should be made aware of…
I feel like vibecoded projects need Claude to pick up on a sense of ‘this is just me messing around’, and a project like this where there does appear to be genuine digging into the art of performance tuning Z80 assembly needs Claude to understand ‘this is impractical hacking for hacking’s sake not groundbreaking research’
I don’t have a problem with projects which are, essentially ‘Claude and I burned a lot of tokens for giggles to see just how far you can push something’. But the write up needs to reflect that spirit.
That's an excellent way of putting it. It's like an enthusiastic student who points out all the really smart stuff it did so that the teacher will be impressed and give it a gold star...which is basically what its RL environments were.
I have called it Claude's "iamverysmart" voice, but as you said, maybe it's more of a "thisisveryimportant" voice.
agreed, the only issue here is that Claude is targeted to enterprise engineering teams so its language model is trained for SoCal startup culture.
Would take three times the token cost to actually get it to fight with itself in the correct voice tone.
Honestly think self hosted models is more valuable here. At least then one can train it with the right system prompt.
You can do a lot with custom agent prompts. Just telling Claude ‘this is only a personal project, we’re messing around here’ changes its tone somewhat already. It’s still Business Claude, but more Casual Friday Claude, less Monday Morning Standup Meeting Claude.
the only issue here is that Claude is targeted to enterprise engineering teams so its language model is trained for SoCal startup culture.
SV is SoCal now? I missed the earthquake.
There's also a vast gulf between 'startup culture' and 'Enterprise engineering'. But the general sense of "this voice is for a specific context, and it is not 'weekend ZX Spectrum hacking project'", is correct.
TBH even if you're messing around you may still want the code to be performant and taken seriously :-P
Sure. If I ask my roommate to go make me a ham sandwich without mayo, I expect them to observe basic hygiene practices, too, but I am comfortable with them just handing me the sandwich and saying ‘there on you go - sandwich’ rather than “Here is an edible sandwich: No mayo, no lettuce – just bread and ham. And the load-bearing insight that makes it work: it doesn’t use the open ham from the fridge that was past its use-by date. That one decision changed everything.”
Yeah, but it doesn't have to sound like you have invented a time machine and deserve a Nobel prize.
> It runs on the real thing, not just an emulator.
Wow!!!!
It looks like Windows 10. Even the light theme is implemented. They only need to implement the dark theme to be at the same UX level as Windows 10.
Written in the best programming language ever!
Claude?
And take all the fun out of it??
Assembly seems overkill though.
There is practically no other choice on a Z80. C compilers really don't like the Z80 ISA and create both slow and bloated output, at least compared to manually written asm. And on top, you can do many optimization tricks in assembly that simply are not possible in a high level language (self-modifying code, jumping into the middle of an instruction, etc...).
Forth might work better than C, but tbh, assembly code is more straightforward and easier to read than Forth ;)
PL/M ?
Don't know, but AFAIK this wasn't a popular programming language on home computers in the 1980s (from what I've seen, the popular non-asm languages were usually BASIC, Forth and Pascal, even C was kinda rare).
I believe most of the 8bit microcontrollers from this era have no good optimizing compilers that get close to what competent practitioners achieve with assembly. I think it has to do with having complex addressing modes making the C stack fairly inefficient.
For an 8 bit Z80 based hardware project like this, assembly is a valid choice. The reason is performance. You'll lose significant performance with a compiler or interpreter.
The quickest way to redraw a screen or otherwise copy a memory region on Spectrum of is to use POP/PUSH instructions while flipping the stack pointer. Good luck getting that with C.
assembly is the only choice. The Z80 processor is a twisty collection of registers, none alike. It is pretty much the opposite of what a, for example, C compiler is looking for.
In fact C compilers are _notoriously_ bad at producing code for the Z80.