I'll be curious to find out if the MacBook Neo, with its A18 Pro chip and only 8 GB of RAM, feels too slow when compiling Rust.
-
I'll be curious to find out if the MacBook Neo, with its A18 Pro chip and only 8 GB of RAM, feels too slow when compiling Rust. I like Rust a lot, but it's infamous for long compile times, especially for release builds with link-time optimization.
-
I'll be curious to find out if the MacBook Neo, with its A18 Pro chip and only 8 GB of RAM, feels too slow when compiling Rust. I like Rust a lot, but it's infamous for long compile times, especially for release builds with link-time optimization.
@matt And if not, that means that people could conceivably realisitically use their phones for development. Modulo Apple's policies.
-
I'll be curious to find out if the MacBook Neo, with its A18 Pro chip and only 8 GB of RAM, feels too slow when compiling Rust. I like Rust a lot, but it's infamous for long compile times, especially for release builds with link-time optimization.
@matt Probably will be too small. Multi-thread performance on the neo is not that great, as expected.
-
I'll be curious to find out if the MacBook Neo, with its A18 Pro chip and only 8 GB of RAM, feels too slow when compiling Rust. I like Rust a lot, but it's infamous for long compile times, especially for release builds with link-time optimization.
@matt I write Rust all of the time on an M1 MacBook Air. I have to replace it, but only because the keyboard is breaking after all these years (I bought it on release day). The opt builds are all cached on BuildBuddy anyway:) https://sayrer.com/blog/whats-in-a-tweet/#bazel
-
I'll be curious to find out if the MacBook Neo, with its A18 Pro chip and only 8 GB of RAM, feels too slow when compiling Rust. I like Rust a lot, but it's infamous for long compile times, especially for release builds with link-time optimization.
@matt @ekuber I don’t think it will be that bad honestly but we’ll see. I regularly work on fairly large Rust codebases and compile times aren’t high on my list of complaints.
Bits of context:
- I was a macOS / iOS developer for years. Compile times WERE a top complaint there.
- The M1 doubled or quadrupled compile speeds from the previous gen Intel at the time. I still use my M1 Max, 4+ years later.
- Some rust codebases are slow but it’s gotta be a REALLY heavy dep like DataFusion. -
I'll be curious to find out if the MacBook Neo, with its A18 Pro chip and only 8 GB of RAM, feels too slow when compiling Rust. I like Rust a lot, but it's infamous for long compile times, especially for release builds with link-time optimization.
@matt I really want to see and play with one. I don't need it but I want someone to buy it and come by so I can take a look. haha
-
I'll be curious to find out if the MacBook Neo, with its A18 Pro chip and only 8 GB of RAM, feels too slow when compiling Rust. I like Rust a lot, but it's infamous for long compile times, especially for release builds with link-time optimization.
@matt i am actually wanting to know how much wx dragon takes on a mack to build? It makes my laptop dy lol.
-
I'll be curious to find out if the MacBook Neo, with its A18 Pro chip and only 8 GB of RAM, feels too slow when compiling Rust. I like Rust a lot, but it's infamous for long compile times, especially for release builds with link-time optimization.
@matt I think the 8GB RAM will be a problem rather than CPU
-
I'll be curious to find out if the MacBook Neo, with its A18 Pro chip and only 8 GB of RAM, feels too slow when compiling Rust. I like Rust a lot, but it's infamous for long compile times, especially for release builds with link-time optimization.
@matt Along with other idiosyncrasies of the Rust language as well. It's got a ways to go before it can truly compete with C.
-
R relay@relay.publicsquare.global shared this topic
