• 5 Posts
  • 94 Comments
Joined 1 year ago
cake
Cake day: July 17th, 2023

help-circle





  • Yeah, there’s a reason why they suddenly have a lot of trouble selling their military hardware even to countries that haven’t sanctioned them.

    Well, other reasons in addition to the fact that the stuff they’re fielding themselves in Ukraine keeps getting blown the fuck up and they have had to replace it with something that was initially being built for an outside customer. “Yeah you remember those tanks you ordered? Weeelll you’re not going to be getting them quite on schedule, there’s been some… uh… complications. The turrets… they, uh… experienced rapid unplanned disassembly caused by… uh… assembly workers smoking in the crew compartment. Definitely not caused by inferior westoid antitank missiles in Ukraine, our cope cages work against those 100% of the time and it’s not like we’d use your tanks in combat, no siree Bob”












  • I’ve been learning Swift recently, and I have a really ambiguous feelings about it as a language. It has many things I like, but it also feels like the dictionary definition of “designed by committee” with a billion features bolted on to it, with often multiple different ways of expressing the same thing (quick, how many syntaxes are there for closures?), and it feels like it’s overly complex because it has too many abstractions for doing approximately the same thing but not quite. Like concurrency and memory safety for example, where you have async and actors and tasks, the new isolation region stuff, the concurrent memory access rules that apply even outside of async contexts, borrow / consume etc. etc. and all of which interact in sometimes frankly fairly confusing and not too well documented ways.

    Especially the concurrency and memory safety side could use some sort of overarching abstraction instead of a dozen different ones that get bolted on one at a time on top of each other as problems are discovered with the earlier ones. While eg. Pony isn’t a simple language as such, at least for me its reference capabilities + actors are much easier to reason with than Swift’s async + actors + tasks + isolation regions + memory access conflict rules + borrow / consume + kitchen sink setup