|
Matthew Garrett
@mjg59
|
10. sij 2019. |
|
The moral isn't "Don't use systemd", the moral is "Write stuff in better languages than C". rsyslog doesn't exactly have an enviable security record either.
|
||
|
|
||
|
Igor Emelianov
@cyber1human
|
11. sij 2019. |
|
|
||
|
|
Neal Gompa (ニール・ゴンパ)
@Det_Conan_Kudo
|
11. sij 2019. |
|
I wish so-called safer languages supported shared libraries as first-class things, though. It's silly (and sometimes literally insane) to have to build every single thing from scratch for each program...
|
||
|
|
||
|
|
Neal Gompa (ニール・ゴンパ)
@Det_Conan_Kudo
|
11. sij 2019. |
|
The computational complexity and the build-side resource requirements go up *a lot* as you add dependencies that you always have to build. Heck, classical C++ programs like Chromium demonstrate the logical conclusion of such models that are promoted by languages like Go and Rust.
|
||
|
|
||
|
Julian Andres Klode
@JulianKlode
|
11. sij 2019. |
|
So when's the systemd rewrite in Rust going to start? ;)
|
||
|
|
||
|
Jakub Jirutka
@JakubJirutka
|
11. sij 2019. |
|
Yes, but in your case it would not help at all. Most of the security holes in systemd are caused mainly by bad design.
|
||
|
|
||
|
isis agora lovecruft (they/them)
@isislovecruft
|
12. sij 2019. |
|
hi Lennart! we met a long time ago at a FOSDEM speakers dinner. if you want a (free) consult on interfacing with and integrating rust from other languages and platforms i’m happy to offer lessons i’ve learned on other projects
|
||
|
|
||
|
Marco Matarazzo
@elementalstorm
|
11. sij 2019. |
|
When everything else is no longer working, blame the language.
|
||
|
|
||
|
Marcin Juszkiewicz
@haerwu
|
11. sij 2019. |
|
let's boot to BASIC. Like in 80s
|
||
|
|
||
|
Adrian Rueegsegger
@Kensan42
|
11. sij 2019. |
|
I am genuinely curious: what is keeping you from doing so? (E.g. not enough people who are proficient in language X, no clear choice of language X, immature ecosystem og language X, ...)
|
||
|
|
||
|
Andrew J. Bromage
@deguerre
|
12. sij 2019. |
|
IMO the main barrier is maturity. If you write code in Rust today, you need to prepare yourself for the fact that your code will need to be substantially rewritten within the next 10 years. Same as if you wrote C++98 or Haskell98.
|
||
|
|
||