Sylvestre's blog

@Jorg because crates are directly shipped into the final binary. No work has been done to minimize the size.

There are some options to do it: https://github.com/johnthagen/min-sized-rust

Interesting project!

Can you elaborate, why the Rust package is so much bigger than the C package?

On the one hand, I’d absolutely love using well written utilities that I spend 50% of my terminal time on.

I bet they would add colors and what not.

On the other, I have to wonder if the people writing the new stuff understand things in and out enough to be able to cover every last case. I mean if my cp is silently doing data corruption in some edge case, that won’t be worth the productivity I gained from using better developed new tools

https://lobste.rs/s/jdqu4m

Regardless of the decision to stop the debian migration endeavour, it definitely has had positive ripple effects on code quality throughout the vast free software ecosystem.
Thanks for all your effort Sylvestre! : )

I think stopping the goal of switching is a mistake. LLVM has better sanitizers (which help portability and security), more frequent releases (which make it easier to adopt new versions), and seems to be the basis for a lot of new research in compilers.

The bugs that prevent the switch are, at this point, generally real bugs in the code.

what is shipping?
what is USD or EURO for swiss army knife?
how much for umbrella and hat together/?

I think Clang should stop having just a single command line toolset. It should have a compatibility interface for gcc, with same switches and warning/error handling as gcc, and a Clang main frontend, with possibily different switches and different default settings for warnings/error.

@teh 1

> what’s the general reason why everything won’t compile on Clang?
There are various reasons:
* bad code that gcc accepts
* non standard C code accepted by gcc (variable length array for example)
* -Wall (+ -Werror) does not enable the same set of warnings
* clang is C99 by default, not gcc.
* etc

Out of pure intellectual curiosity, what’s the general reason why everything won’t compile on Clang? Is it that GCC ignores errors and alows non-standard code? Or is it Clang that didn’t implement everything according to standards? (In terms of C and C++ standards)

You might be interested in the Gentoo tracker for Clang-specific failures:

https://bugs.gentoo.org/show_bug.cgi?id=408963

Amazing decrease from 9.5% to 5.7%.
I guess it will be possible to compile a full Linux distribution with clang in only a few years.

Very nice work Sylvestre.
:)

Aaron, Planet Debian has already an account:
https://twitter.com/planetdebian

Vincent, why not but it would help to get that in a better format (RSS, XML or RFC 822 format).

A Debian Planet feed would be great also. I don’t know if this exists already, however.

Having an account for new Debian maintainer [1] would be cool, I guess!

[1] https://udd.debian.org/cgi-bin/new-maintainers.cgi

Thank you for doing this. I see that a lot of people find it confusing why there isnt a change log between beta releases.

http://gcc.gnu.org/ml/gcc/2014-01/msg00247.html

Amazon gives 10 000 US$/year to Debian for such experiment.

We are building, for now, just for amd64. There are still so much work to do. It would be a mistake to try tackling every issues at the same time.

What is “AWS donation” ?

Are you only building x86 or other arch too ?