this post was submitted on 29 Nov 2023
1 points (100.0% liked)

Lisp

55 readers
3 users here now

founded 1 year ago
MODERATORS
top 4 comments
sorted by: hot top controversial new old
[–] mdbergmann@alien.top 1 points 1 year ago

I can't generally comply with this. I've developed a bunch of applications over the last 10-15 years for macOS. All of them practically still work with only minimal effort. If you stick to the provided APIs and frameworks it's much less a pain. The provided native framework are excellent to work with.

C libraries and such things where CL is depending on for some libraries are of higher rate of change. That's probably where the frustration comes from.

[–] love5an@alien.top 1 points 1 year ago (1 children)

I can't agree more with the point that Apple is waging a constant war against its users, especially developers. Developing anything for the platform is practically impossible without owning their devices and operating systems. And moreover, their licensing policy. Ugh... I can't remember any other software company which treats developers so badly today.

[–] zyni-moe@alien.top 1 points 1 year ago (1 children)

Developing anything for the platform is practically impossible without owning their devices and operating systems.

And it is easy to develop for Windows without this? Yes I know that macs are more expensive than cheapy windows boxes, but this is not a good argument.

[–] Shinmera@alien.top 1 points 1 year ago

I've developed most of my libraries for windows on linux and used wine for testing and development, only using a VM for final confirmation.

Unfortunately Darling still can't even run SBCL.