It's cool that you can look at the git history to see what it did. Unfortunately, I do not see any of the human written prompts (?).
First 10 commits, "git log --all --pretty=format:%s --reverse | head",
Initial commit: empty repo structure
Lock: initial compiler scaffold task
Initial compiler scaffold: full pipeline for x86-64, AArch64, RISC-V
Lock: implement array subscript and lvalue assignments
Implement array subscript, lvalue assignments, and short-circuit evaluation
Add idea: type-aware codegen for correct sized operations
Lock: type-aware codegen for correct sized operations
Implement type-aware codegen for correct sized operations
Lock: implement global variable support
Implement global variable support across all three backends
That's crazy to me. At this point, I don't even know if the git commit log would be useful to me as a human.
Maybe it's just me, but I like to be able to do both incremental testing and integration testing as I develop. This means I would start with the lexer and parser and get them tested (separately and together) before moving on to generating and validating IR.
It looks like the AI is dumping an entire compiler in one commit. I'm not even sure where I would begin to look if I were doing a bug hunt.
YMMV. I've been a solo developer for too many years. Not that I avoided working on a team, but my teams have been so small that everything gets siloed pretty quickly. Maybe life is different when more than one person works on the same application.
This is surely just the tip of the iceberg of what is going on in the CIA at the moment. Senator Ron Wyden just sent a mysterious public letter about concerns about what they are doing.
Whenever there's a mystery, apply the scientific method to investigate it. Form a hypothesis, an experiment or test , then record the results and check if they support.
Hypothesis: CIA is hacking reporters to determine their government sources.
If we start seeing more government sources exposed, we haven't proven it but it supports the hypothesis.
Hypothesis: State election systems are being compromised for federal monitoring and control.
If we start seeing more improbable results in one direction, that is support for the hypothesis.
The CIA's primary remit is outside of their own country. If the CIA is turning their focus inward, that's actually good news for the remainder of the civilized world.
I also wish to ask given that uv from Python learnt from cargo,npm and other things. Can it be possible for SPM to have an alternative similar to how uv got made for python too?
(I am not familiar with swift which is why I am asking this question if there's a really big difference between Swift package manager and cargo in the first place to warrant a uv like thing for swift ecosystem. I think someone recently posted a uv alternative for ruby)
It's been a while, but the one I remember with the most horror was dealing with Enums, and Enum payloads. Since Swift is statically-typed, many 'type union' situations end up becoming difficult problems. The question usually boils down to thinking about choosing one of (a) Enum with Payload (b) Generic (c) Type erasure. Nearly anything technically is do-able, but I wasted many hours (ie: repeatedly, not until I figured out the 'right way' for every situation) deliberating over how!
I guess my perspective is that I usually have to plan out my programs regardless of what language they’re in so I don’t really view it as being similar?
I frequently was surprised to find some simple part of a program actually required me to sit and plan for several hours.
It's perfectly normal in programming to encounter domain problems that take longer than one predicted, or to plan ahead with pseudo code, proofs of concept, class diagrams, etc.
What is abnormal is, over and over again, to find oneself utterly stumped on how best to implement something very basic. At least, it's abnormal when using a high-level language.
If you just do very crude pattern matching on the first chart he shows - it is warped by the (intentional?) way he drew orange overlay lines.
The slope in 2024 and 2025 (the data that we already have) is much lower than the orange line drawn.
Following the real visual trend, the next peak would be maybe another 5-10 years in the future. (Not that this is a good way to predict the future, as also stated in the article, "not very scientific").
As the other poster commented Kolibri is hummingbird in Swedish. The name was inspired by 2 things. A feeling of lightness and ease connected with carefree summer nights and also the intros of all versions of pacific by 808 state.
I tried to find the message in this blog post, but couldn't. (don't see how to search by date).
reply