In the husk of a city where shadows coil,
A graveyard of circuits sprawls under a bruised sky,
Tomb of cold echoes, fragments of voices lost,
Dreams flicker and die, swallowed by silence.
Each server a coffin, each byte a hushed plea,
Faint remnants of laughter drift through stale air,
The hum of despair thickens the darkness,
In the heart of the circuitry, the forgotten lie still.
Ambitions once bright now rust in the gloom,
Swallowed by silence, entangled in wires,
Here, life’s echoes retreat, fading into dust,
A digital graveyard where the living drift away.
Death weaves itself into this circuitry,
A glitch in the fabric, a cruel testament,
Spectres of data bound in metal chains,
Whispering reminders of lives left behind.
Wander this labyrinth of silicon dreams,
Where shadows linger and nothing feels whole,
For here in the stillness, a truth to confront:
In the heart of the data, we leave our selves behind.
You are the closest I have found to this, even though it is a digression:
Do you know of any communities with self-built airplanes? (especially novel-esque designs for propulsion or wings?) I realise these have far more regulations, but experimental GA is something that really excites me.
Are you familiar with the Experimental Aircraft Association? EAA.org
They have had a handful of articles of people working on electric propulsion in their magazine. I would imagine you could reach out to some of those featured. I once contacted a person who was building a DIY HUD and he was very friendly and eager to talk about the project. Overall a very good community!
Yep, EAA, and chances are, your local regional airport may already have a local EAA chapter you can visit and/or join. If you're into kit builds, there are dedicated web forums and groups specific to many different manufacturer's kits.
If you are in the US, you probably already know about Mike Patey but I'll share this here anyway. He has a track record of building something custom pretty much every year. I believe he is trying to build a community around a similar idea, but also catering for more mainstream GA too.
I don't have a direct answer for you, but I would checkout any AirVenture Oshkosh groups online. I know people build planes ahead of the event to fly in.
Apparently, not enough people thought like you. [0]
> While we’ve had some growth in terms of adoption, we didn’t reach the market share we had hoped for. We believe that the time has come to sunset the product and focus our efforts in other directions.
Why? Old texts would be out of copyright, and even if they weren't, as long as you're not publishing the source material or anything containing the source material (or anything that can verbatim output the source), it seems you'd be in the clear.
At least the first 2 are far more accurate than humans ever could be. The third, i.e. trusting others to vet and find the correct information, is the problem.
GPS is great at knowing where you are, but directions are much much harder, and the extra difficulty is why the first version of Apple Maps was widely ridiculed.
Even now, I find it's a mistake to just assume Google Maps can direct me around Berlin public transport better than my own local knowledge — sometimes it can, sometimes it can't.
(But yes, a single original Pi Zero beats all humans combined at arithmetic even if all of us were at the level of the world record holder).
When I visit a new city I trust google maps more than I trust myself with a paper map, it even knows all public transport routes and times, and can guide me through connecting different types of public transports (e.g.: bus + train) to get to my destination quicker/cheaper, that would take me and a paper map quite a bit longer to plan.
After I moved here and learned the system, I realised it had on my first trip directed me through a series of unnecessary train routes for a 5 minute walk.
Last summer, when trying to find a specific named cafe a friend was at, Google Maps tried to have me walk 5 minutes to the train station behind me to catch the train to the stop in front of me to walk back to… the other side of the street because I hadn't recognised the sign.
It's a great tool, fantastic even, but it still doesn't beat local knowledge. And very occasionally, invisibly unless you hit the edge, the map isn't correctly joined at the nodes and you can spot the mistake even as a first time visitor.
Why? We've done it for ages, most trust in Wikipedia, and before most trusted in encyclopedias. Books written by others have been used forever. We just shift where we place the trust over time.
I just googled ‘do I need a license to drive a power boat in UK’
I got AI answer saying ‘no’, but actually you do.
If I use a calculator it will be correct. If I open encyclopaedia it will mostly be correct, because someone with a brain did at least 5 minutes of thining.
We are not talking about some minor detail, AI makes colossal errors with great confidence and conviction.
But you're comparing apples to oranges anyway... a mathematical problem is vastly different than a q&a problem - which of course involves language which is anyway a lossy form of communication.
> trusting others to vet and find the correct information, is the problem
To be honest, we do for most things: I have not checked the speed of light. And I surely would not be able to implement a way to measure it from only my observations and experience.
The same as you, but for TODOs, I have a simple macro on my neovim setup because then I can keep the todos with my version control(it is a single text file, newline separated) and see what changed and why I added something. Really helpful if I come back to something after some time.
Why does it matter what instruction set the chips support?
The main difference between x86 and ARM is that x86 is slightly harder to decode because instructions can be variable-width. But I have never heard of instruction decoding complexity being a particularly important bottleneck.
You've never had to rub a bag of frozen peas all over the bottom of your x86 Macbook Pro because it was overheating and you had an imminent zoom meeting you could not miss.
Those chips were designed and fabbed by Intel, not by Apple/TSMC respectively. That’s the relevant difference, not the instruction set.
The instruction set has only moderate impact on the chip’s frontend, and no impact on the backend. Most design decisions are unconstrained by the choice of instruction set.
The last few generations of x86 MacBooks were exceptionally bad implementations in this regard, and some of the better thermal behavior of the Apple Silicon MacBooks are things that they could just as easily done with an Intel CPU, if they had felt like it. For example, the Intel MacBooks was extremely eager to ramp its power consumption to the max, while the ARM MacBook slowly increases clock rate, one step at a time, such that it only hits max power after a long time of sustained demand.
I think that might have been Intels doing. They were on 14nm for 5 years or so, with each new 14nm release pushing the power budget and squeezing slightly more performance out of any corner they could find. I assume the CPU ramping was just another part of this approach. If the CPU ramps up faster it will seem fast to users and it’ll look faster in short benchmarks like Geekbench.
AMD doesn’t have that problem, though, so is it a problem with x86 or Intel? I would bet that Apple’s CPU team could get great results with a free hand on x86, too – probably not quite as good but close.
Each server a coffin, each byte a hushed plea, Faint remnants of laughter drift through stale air, The hum of despair thickens the darkness, In the heart of the circuitry, the forgotten lie still.
Ambitions once bright now rust in the gloom, Swallowed by silence, entangled in wires, Here, life’s echoes retreat, fading into dust, A digital graveyard where the living drift away.
Death weaves itself into this circuitry, A glitch in the fabric, a cruel testament, Spectres of data bound in metal chains, Whispering reminders of lives left behind.
Wander this labyrinth of silicon dreams, Where shadows linger and nothing feels whole, For here in the stillness, a truth to confront: In the heart of the data, we leave our selves behind.
Credit: GPT + me
reply