Hacker Newsnew | past | comments | ask | show | jobs | submit | quux's commentslogin

Is running an IPFS node and pinning the internet archive's collections a good way to do this?

You don't strictly have to use Xcode to use swift, there's a good LSP for use in other editors.

That said, if you're using Swift to build an app, you're probably still going to want to use Xcode for building and debugging


Yea, I'm building iOS apps mostly, and some macOS apps, so definitely need to use XCode :/

I have a nice workflow going for the iOS apps I work on where I use neovim for all my editing, and Xcode for building and debugging.

That is the plan, but they are stalled on that effort by difficulties getting Swift's memory model (reference counting) to play nice with Ladybird's (garbage collection)

I think there was some work with the Swift team at Apple to fix this but there haven't been any updates in months


I would love it if you would provide a reference I could go look at


Thank you! I look forward to perusing these.

Is there a Mac version of this? I could honestly use it

The designers planned on using a shift register in the 6522 VIA chips to implement fast serial loading, but an undocumented bug in that chip forced them to fall back to the slow bit banging version that shipped

I don't know how many of you have seen a 1541 floppy drive in person either but it is massive, it's heavier and possibly bigger that an actual Commodore 64 and pretty expensive at the time too.

it's fun seeing c64 people on the defensive about it, a nice change from getting lectures from them about how their graphics were the pinnacle of 8-bit computing


Part of the size was the internal power supply. And that thing got hot, too. I used them at school, but at home only had the smaller 1541-II with an external power brick.

The Apple II disk drives, on the other hand, were not only cheap (Apple was different then!) and fast, but were powered by the ribbon cable connecting them to the computer.


Oh its MUCH better than that. Commodore did this because they had incompetent management. They shipped earlier products (VIC-20, 1540) with hardware defective 6522, but:

- C64 shipped with 6526, fixed version of 6522 without shift register bug

- C64 is incompatible with 1540 anyway

They crippled C64 and its floppies _for no reason_.


It was not for no reason. When adding a screw hole in the motherboard so it could be mounted in the case, they accidentally removed the high speed wire, dooming the C64 to the same slow data speed of the VIC-20 with it's faulty VIA.

The C64 data speed actually ended up being even slower than the VIC-20. You can read the full detailed here: https://imrannazar.com/articles/commodore-1541


ah yes, you're right, they did try to fix it in the C64, forgot that whole part of the story.

They finally got it right in the C128 though!


Yes you can, back in the day this is how fast loaders worked, they uploaded an optimized serial protocol to the ram on the drive and called into it.

I kept waiting for the payoff to be "The optimizer reduced the entire series of if statements to a single instruction"


Rust even works on 8-bit via the LLVM-MOS backend for MOS 6502 :)


Looking at the list of affected architectures: Alpha (alpha), Motorola 680x0 (m68k), PA-RISC (hppa), and SuperH (sh4) I think these are much much more likely to be run by enthusiasts than someone needing an affordable computer.


yes


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: