As far as I can tell Jakt's reference counting is not optional. So it may be closer to Swift.
That being said I've seen a few people here suggest it's easier to use rust's Rc and Box for everything and treat it like Haskell or Scala. So it might not be so different in practice.
Wait what. Doesn't go have a proper garbage collector or do I need to get reeducated?
Yes, it does have a garbage collection, I wasn't trying to imply it uses reference counting.
(Though to be fair reference counting can be considered a rather rudimentary way of doing garbage collection.)
TBH Jakt defaults to reference counting, which makes it compete more with Swift and Go rather than C/C++/Rust.