I don't know what happened to this website but stuff like this keeps hitting the front page more and more often despite having close to zero value. It feels like SEO spam to me.
"Please don't post insinuations about astroturfing, shilling, brigading, foreign agents, and the like. It degrades discussion and is usually mistaken. If you're worried about abuse, email hn@ycombinator.com and we'll look at the data." https://news.ycombinator.com/newsguidelines.html
Except there's nothing to discuss because the book is not released. Is HN about "awareness" now? Why not come back in 2026 when the book is actually released and people can actually talk about the contents of the book?
Yes, the bad link given here doesn't do the content justice, whatever your opinion would be. It would've been better to link to one of the author's articles on the Nerd Reich website (or something more substantive like his newsletter content). I'm assuming you're talking about the link itself as opposed to the content of the book or topic in general.
Like clockwork. Each time someone criticizes any aspect of any LLM there's always someone to tell that person they're using the LLM wrong. Perhaps it's time to stop blaming the user?
Why would their response be appropriate when even the creators of the LLM doesn't clearly state the purpose of their software, yet alone instruct users how to use it? The person I replied to said that this software should be used yo "help you build and run experiments, and help you discuss your findings, and in the end helps you write your discoveries" - I dare anyone to find any mention of this workflow being the "correct" way of using any LLM in the LLM's official documentation.
You wouldn't use a screwdriver to hammer a nail. Understanding how to use a tool is part of using the tool. It's early days and how to make the best use of these tools is still being discovered. Fortunately a lot of people are experimenting on what works best, so it only takes a little bit of reading to get more consistent results.
What if the company selling the screwdriver kept telling you your could use it as a hammer? What if you were being bombarded with marketing the hammers are being replaced by screwdrivers?
You can recognise that the technology has a poor user interface and is wrought with subtleties without denying its underlying capabilities. People misuse good technology all the time. It's kind of what users do. I would not expect a radically new form of computing which is under five years old to be intuitive to most people.
I've never experienced the original Amiga and I probably never will. I would however be open to emulating the machine. Are there any good resources for people like who would like to try out the whole ecosystem as a complete newbie in 2025? My knowledge about Amiga is close to zero.
1. Get a copy of the Amiga 3.1 Kickstart ROM (v40) and Workbench disks (for example by legally buying Amiga Forever ... or other ways). If you do buy Amiga Forever, they've put together an Amiga emulation environment for you with lots of software pre-installed.
2. Consider buying AmiKit or using its free version: https://www.amikit.amiga.sk/ -- it needs the aforementioned Kickstart ROM and Workbench Disks, but again they've put together an Amiga emulation environment for you with lots of software pre-installed.
3. If you don't want to use those pre-made packs, install WinUAE (for Windows) or amiberry (for macOS/Linux) yourself, configure them yourself with the ROM... and use one of the ClassicWB (https://classicwb.abime.net/) hard drive images.
4. And if you don't like ClassicWB, you can also extract the Amiga hard drive image included with PiMiga 4 to enjoy an alternative pack. PiMiga is a Raspberry Pi image that includes an Amiga emulator for the Pi and a huge Amiga hard drive image -- simply use software to read the PiMiga Linux ext2 filesystem and extract that hard drive image to use it on your own emulator, no RPi needed (https://old.reddit.com/r/amiga/comments/1dfcn8u/extract_amig...)
If the aim is to emulate games, Kickstart 3.1 or even 2.04 shouldn't be the first choice. Backwards compatibility must have been really poor back then; at least I've run into lots of software that will only run on 1.3.
One does not typically run games directly. That's fraught with the compatibility concerns you raise, and also the slowness of loading them from their disks, even when using an emulator, and needing a cumbersome UI to swap disks as needed.
Instead you run them with WHDLoad, originally designed to install all games onto the hard drives of real Amigas.
A lovely group of programmers have made WHDLoad installers for every game you know of, that patch the game in just the right places so it runs correctly, regardless of Amiga model or OS version.
WHDLoad also lets you press a "QuitKey" that returns you back to Workbench. And if you have an emulated Amiga with lots of RAM, you get to preload all the disks into RAM so there's basically zero loading time.
People have made large collections of "preinstalled" WHDLoad installers, bundling games in a ready-to-run way for any Amiga.
I am very happy with AmigaVision, packaged by Alex Limi (of early Mozilla Firefox UX/product fame) et al.
AmigaVision is a carefully curated collection of game and demo configurations for the Amiga computer platform, as well as a minimal Workbench setup with useful utilities and apps, wrapped in a user-friendly launcher.
AmigaVision is very nice. One thing that's especially great for emulation users with modern hi-res flat screens is they've already done the work to set up proper integer scaling, cropping and scanline/shadow mask pixel shaders.
Many of the Amiga's legendary games and graphics were specifically hand-crafted to look best on high-quality analog RGB CRTs. It's shocking how much better they look when properly displayed. The hard-edged, square block pixels on so many retro Youtube channels is not just technically incorrect - it's not what the original developers and artists created or ever intended their users to see.
MiSTer, especially the new cheaper builds (MisterPi) are by far the best way to play the old consoles if you want to play on a TV and well worth the $200.
Yeah. (Sorry, somehow didn't read your comment about the same AmigaVision before commenting.)
I find myself wishing for something like AmigaVision for e.g. the IBM PC.
The launcher should be in either classic text mode or VGA 640x480x16 colors with custom palettes like those cool disk mags. And of course tracker background music.
There is some similar effort called 0MHz based on the eXoDOS project, but I'm not sure I like it as much. Needs more work. And a lot more curation.
Totally agree with you, I'd like to see it for the C64, Spectrum, Atari ST, Amstrad etc too. It makes the system into something which is really close to "plug in and play".
I'm also hoping that we start seeing USB external Amiga / C64 keyboards for the real enthusiasts. That might be a little too niche though.
Buy a MiSTer FPGA and run Amiga Vision on it. You can plug in a proper keyboard and joystick and you can map jump to a button instead of up as it traditionally is on Amiga.
I have to admit that it's better than using my A500/A1200s.
Thanks, your comment made me buy the icode prebuilt preloaded MiSTer FPGA, 128mb ram, hope that is sufficient for Amiga Vision. I used to own an Amiga 500 with internal HDD, long ago. Guru meditations still exist?
Even the most basic models (the $99 + shipping + tax from China) can handle the Amiga. You get more bells whistles plus a better package with a MiSTer stack but I would recommend most people to either grab the Multisystem II or the Mister Pi (Turbo Pack) from RetroRemake. If you want to run Saturn fighters then getting a second stick of RAM is a must as it allows everything to run at full speed.
I have the Ultimate Mister kit with USB + AV boards but only a single stick of RAM (also 128MB) and a Honeywell PSU and it's awesome especially for the Amiga and C64 :)
Yeah the Mister Pi makes more sense, financially. On the C64 side, there is the upcoming C64 Ultimate https://www.commodore.net, that looks almost identical to the original one
getting the hardware is only half the battle. Hard agree with going for a MiSTer setup however it's quite an expense for someone dipping a toe in.
ultimately it's hard to prescribe the "definitive" amiga experience in 2025 to a total newbie. At a surface level, for many people, amiga ownership was simply a console like experience -> Buy an amiga 500, and shovel game disks into it, play game, turn it off. Replicating that is super easy with either just a raspberry pi and the PiMiga distro (see the Chris Edwards youtube channel for details) or even retropie comes with support for amiga OOTB however it comes with the caveat of having a little background knowledge of the hardware combinations available.
The ABSOLUTE easiest way of getting a taste of amiga is to get hold of a "The A500" mini console which comes with pre-packaged games (but also lets you run your own once you've got to the end of enjoying the 30 or so pack-ins).
There is the WinUAE emulator for windows that's excellent (so good, you can use it to prep real-world Hard drives for actual physical amigas) but it's complicated without prior knowledge of the OG hardware combinations.
The most common setup back in the day (for UKers playing games at least) was an OG Amiga 500 with OCS (Original Chip Set) with 0.5MB RAM(ChipRAM - essentially shared system and graphics memory) and maybe an optional extra 0.5 MB upgrade (FastRAM - CPU only memory, though often known now as SlowRAM because it was directly accessable by the CPU only but had to share the bus with the chip RAM) and 1.3 Kickstart ROM.
This was later upgraded by the A500+ which came with ECS (Enhanced Chip Set) which gave a few added graphical modes, 1MB of Chip RAM (typically upgradable to +1MB fast RAM) and kickstart 2.0. it broke compatibility with some games and was a min spec for others.
This was replaced directly by the A1200 which came with an upgraded CPU (68020ec at 14 MHz) AGA chipset (16.7 mil colour palette, 256 on screen), internal IDE interface and kickstart 3.0 with 2MB ChipRAM out of the box.
The A500+ was also indirectly replaced with the A600. Essentially a A500+ mini - they updated the manuafcturing to surface mount, reduced the PCB size significantly and removed the numberpad from the keyboard and added the IDE interface from the A1200. it was supposed to be a cost reduced version but initially cost more to make than the outgoing A500+. It was hated at the time because it cost more at retail and had less features (lack of keypad broke a lot of software, IDE interface wasn't seen as beneficial at the time and the side expansion port was replaced by a PCMCIA port which again only had much more expensive peripherals at the time)
The rest are the "Big Box" amigas - computers with a separate keyboard from the main box case:
A1000 (the OG or just "Amiga" when it launched)
A2000 - The workhorse version of thw A500 with expansion, processor,video upgrade slots.
A1500 - a UK specific cut down version of the A2000 just launched to inflict trademark damage to a sole trader startup making aftermarket cases for the A500.
A3000 - the first fully 32-bit platform - ECS and 32-bit 680x0 CPUs available (IIRC both 68020 and 68030 though might be wrong about the '020)
A4000 - a big box equivalent to the A1200 - AGA and expansion
A4000T - towerized version of A4000 - the holy grail for collectors and rare as hens teeth.
However in 2025 getting involved with the amiga scene is a huge rabbit hole as the community is so large there are always wonderful projects (such as PiStorm) for enhancing and extending the life of these now very aged machines.
Sorry, this ended up a bit of an essay on what was only supposed to be a quick note...
> "The A500" mini console which comes with pre-packaged games (but also lets you run your own once you've got to the end of enjoying the 30 or so pack-ins).
I count to 26, plus one free download they provide for testing out the USB feature.
Amiga Forever in Windows (or in WINE) is about as easy to run, plus it comes with nice pre-configured system images to boot into Workbench. Not having much real Amiga experience I struggle a bit with making use of those. I tried to install some freeware Amiga applications (trackers and such) but not much success.
I spent less on getting my MiSTer up and running than I did getting my A500+ and a lot less than getting my A1200 setup running. And I have the original Ultimate MiSTer setup.
With the RetroRemake and QMTech setup you're up and running for the 8/16-bits for under $200 all-in which for most people in tech in the US isn't a big ask. The experience is also much better than emulation IMHO.
If you're not sure to invest in special hardware, cloanto offers bundles including most kickstarts and some software (games / apps).
That's the easiest and cheapest way to get started. A500mini might also be a relatively cheap option with some modern possibilities (SD cards instead of floppy disks).
I have multiple real Amigas (jesus, that's a lot of amigas meme), but since I installed PiMiga on a rpi400 with its monitor, that's like 99% what you need amiga for. I even prefer it to my commodore 1084s fleet. Even though I need a CRT shot now and then.
A lot of of OSS is subpar or even terrible and end users have low tolerance for this kind of stuff.
GIMP is a great example. For decades anyone asking about "open-source Photoshop" would be redirected to GIMP even though GIMP is nowhere near as good as Photoshop. Years pass and some simple things that are a no-brainer in Photoshop are still a nightmare to do in GIMP. Text stroke is one of such examples, there's no easy way to do it with GIMP and the method you can see online looks bad and can't be easily changed afterwards. Why? Or something as simple as picking a size of a brush - why is selecting small sizes such a pain while selecting gigantic brushes that hardly anyone uses is not? Shouldn't it be the other way around?
Desktop Linux is an another example. It's always presented as an alternative to Windows (or even better than Windows) and when someone tries it out and it doesn't work for them the end user gets blamed for using the wrong distribution, having wrong hardware, not being able to solve issues right away despite being a beginner or even hit with the legendary "works on my machine". It's always the user who is in the wrong and never the software.
All of this gives OSS a bad name. There are always a bunch of small, annoying problems that affects end users and which often go unfixed for years. Whenever one of these end users brings up these problems they either get told to use a bizarre workaround or get a snarky response about submitting a PR or something. This kind of contempt towards the end user seems to be surprisingly common in OSS circles.
I don't think this is fixable. It would require the OSS community as a whole to change and this will never happen.
> they either get told to use a bizarre workaround or get a snarky response about submitting a PR or something.
Generally, those sort of responses are given to people who didn't pay or contribute in any way, and want something for nothing. OSS developers don't work for you; they're generally solving problems that they're having, and if you happen to be having the same problems, then they may get attention. If you'd like some piece of open source software changed, you are free to change it or to hire someone to change it; that's the deal. Expecting work for nothing is ridiculous.
But that's the thing -- the end user is an afterthought. People write OSS software for two reasons: either it's for themselves or someone is paying them to do it. If you, as an end user, wants to "steer the ship", then you have to contribute in some way.
There's simply no point in buying that console when it has like what, 7 exclusive titles that aren't shovelware? 7 titles after 5 years? And this number keeps going down because games are constantly being ported to other systems.
It's quite annoying to use Instagram on a mobile with adblock, and it also has quite a lot of ads (one every two posts!), not to mention the "organic" ads. I wonder if those are counted as well.
Software is built on abstractions - if all your app code is written without unsafe and you have one low level unsafe block to allow for something, you get the value of rust for all your app logic and you know the actual bug is in the unsafe code
This is like saying there’s no point having unprivileged users if you’re going to install sudo anyway.
The point is to escalate capability only when you need it, and you think carefully about it when you do. This prevents accidental mistakes having catastrophic outcomes everywhere else.
I think sudo is a great example. It's not much more secure than just logging in at root. It doesn't really protect malicious attackers in practice. And it's more of an annoyance than it protects against accidental mistakes in practice.
Unsafe isn’t a security feature per se. I think this is where a lot of the misunderstanding comes from.
It’s a speed bump that makes you pause to think, and tells reviewers to look extra closely. It also gives you a clear boundary to reason about: it must be impossible for safe callers to trigger UB in your unsafe code.
That's my point; I think after a while you instinctly repeat a command with sudo tacked on (see XKCD), and I wonder if I'm any safer from myself like that?
I'm doubtful that those boundaries that you mention really work so great. I imagine that in practice you can easily trigger faulty behaviours in unsafe code from within safe code. Practical type systems are barely powerful enough to let you inject a proof of valid-state into the unsafe-call. Making a contract at the safe/unsafe boundary statically enforceable (I'm not doubting people do manage to do it in practice but...) probably requires a mountain of unessential complexity and/or runtime checks and less than optimal algorithms & data structures.
> That's my point; I think after a while you instinctly repeat a command with sudo tacked on (see XKCD), and I wonder if I'm any safer from myself like that?
We agree that this is a dangerous / security-defeating habit to develop.
If someone realizes they're developing a pattern of such commands, it might be worth considering if there's an alternative. Some configuration or other suid binary which, being more specialized or tailor-purpouse, might be able to accomplish the same task with lower risk than a generalized sudo command.
This is often a difficult task.
Some orgs introduce additional hurdles to sudo/admin access (especially to e.g. production machines) in part to break such habits and encourage developing such alternatives.
> unsafe
There are usually safe alternatives.
If you use linters which require you to write safety documentation every time you break out an `unsafe { ... }` block, and require documentation of preconditions every time you write a new `unsafe fn`, and you have coworkers who will insist on a proper soliloquy of justification every time you touch either?
The difficult task won't be writing the safe alternative, it will be writing the unsafe one. And perhaps that difficulty will sometimes be justified, but it's not nearly so habit forming.
Because only lines marked with unsafe are suspicious, instead of every line of code.
Also the community culture matters, even though static analysis exists for C since 1979, it is still something we need to force feed many developers on C and C++ world.
I refuse to read anything that seems to be obviously AI generated. If they can't be bothered to write down what they think then I don't have any reason to bother with reading what they've posted either.
>In fact, this paper found that more than that, it thinks American.
I think that's because it seems to be primarily trained on reddit and therefore mirrors everything reddit stands for. Not a good thing considering just how overrun the site is with bots and political activists of all kinds.
You're absolutely right! Social media like Reddit are overrun with bots, sycophants, and trolls trying to provoke reactions by engaging in controversial topics. This forms echo chambers, which is a sub-par source for training data, and reflects those biases in LLM responses.
