News for hackers. Stuff that matters.
Re:Elm 0.19 Broke Us by kjeetgill on Saturday August 25, 2018 @07:50PM (#17843267)
I think rust went through a huge amount of simmilar changes pre-1.0. I think everyone was better for it. I appreciate they're taking their time to get it right pre-1.0. 1.0 is a fairly solemn promise and I respect them for not taking it lightly.
Re:Elm 0.19 Broke Us by bjz_ on Saturday August 25, 2018 @11:05PM (#17843991)
The difference in Rust's case is that whenever anything was removed it was replaced with something that was better designed. It provided escape hatches available to allow for workarounds (ie. unsafe, and a nice FFI), and to allow C libraries to bridge the gap while the ecosystem was still developing.
Re:Elm 0.19 Broke Us by noncoml on Saturday August 25, 2018 @07:54PM (#17843286)
That’s exactly the kind of answers I got instead of giving me one good engineering reason on why primes were made forbidden just like this. Thanks for the demonstration.
Re:Elm 0.19 Broke Us by star-techate on Saturday August 25, 2018 @08:10PM (#17843360)
The actual reason is probably "when people use primes, they post code that gets syntax-highlighted by tools that don't know about primes, and this results in Elm code looking broken and stupid."
Re:Elm 0.19 Broke Us by noncoml on Saturday August 25, 2018 @08:16PM (#17843397)
Which is not a good reason to ban them completely from one release to the next. It only shows that they don’t really care about their users that much.
Re:Elm 0.19 Broke Us by vmchale on Sunday August 26, 2018 @09:58PM (#17848983)
Rust has FFI that doesn't shit the bed lol