Posts by blinkygal@sunny.garden
 (DIR) Post #ARg3pjNtctF1oLSv8y by blinkygal@sunny.garden
       2022-10-22T17:13:40Z
       
       0 likes, 2 repeats
       
       Hi I’m new to :mastodon: and I see #introduction is a fun thing to do.I enjoy #modernart, #abstractart, #paintings, #photographs. I love listening to #music including #drumandbass, #dance, #classical, #pop, #punk, #ska, and #alternative. I am learning #crochet and #piano and into sports like #skateboarding, #rollerderby, #squash, and #hockey. I love #learning and #science.Have a #MSc in #compsci. I make internet #software have better #security. I enjoy #rust but do research with #cpp too.❤️
       
 (DIR) Post #ARsd9jM1HDlTnkNXqS by blinkygal@sunny.garden
       2023-01-21T21:22:25Z
       
       0 likes, 1 repeats
       
       Happy Lunar New Year!
       
 (DIR) Post #Ac4WF9OiNYHFx5SMQC by blinkygal@sunny.garden
       2023-11-22T15:38:38Z
       
       0 likes, 0 repeats
       
       Swift is getting really mature. Stable ABI. Using clang to access and represent C++ types natively. No ffi bindings required. Foundation library available on all desktop platforms. I hope Rust will start putting some serious effort behind C++ migration/interop. Or I can see a future where the C++ industry migrates largely to Swift, with perhaps Rust libraries for specific tasks like codecs. Which is fine but I worry about some companies, that would be willing to use Rust, never catching up to that. C++ code will never migrate directly into Safe Rust. Swift found a middle ground for it that Rust will need too. Unsafe Rust needs to become a language people can do their daily work in that is better than C++. That’s what migration can look like.I was skeptical of Carbon’s plan to build out an unsafe language that is good to work in, since I felt like the safe language is where people should be. I still worry about coming in and building the safe language later, but I can see the value of making an ergonomic unsafe language (nullability for pointers for example), because they are taking seriously the idea of migrating whole C++ codebases to this language. AND understanding that people will be working in that (unsafe) language full time.1/2#Cpp  #Rust #Swift #CarbonLang
       
 (DIR) Post #Ac4WFAlRIY36Br61Ts by blinkygal@sunny.garden
       2023-11-22T15:38:38Z
       
       0 likes, 0 repeats
       
       An unsafe Rust can still solve a ton of safety problems, leaving lifetimes to mitigations like smart pointers (like raw_ptr in Chrome). This seems like the viable incremental migration/adoption strategy for Safe Rust. Swift is nailing this. I think Carbon is trying to go this direction too. Anyway, enjoy an interesting chat with the Swift team manager:https://mastodon.social/@rust_discussions/1114543945221889512/2#Cpp  #Rust #Swift #CarbonLang
       
 (DIR) Post #Ac4WFCO7GEa5E6CQPA by blinkygal@sunny.garden
       2023-11-22T15:47:45Z
       
       0 likes, 0 repeats
       
       Feel the need to clarify a bit: when I say an Unsafe Rust here I don’t mean that all the unsafe functions are included. I mean a middle ground where you can work with pointers, with no lifetimes. Where unsafe blocks are still used access unchecked functions, and also to bridge over to Safe Rust. But are not needed to build pointer-based software.#rust