@alexcleac not sure what the "there" is, and I am surely missing a bunch of context, but my answer (as a software developer, sysadmin, infosec person, and a user of technology in 2020) is: software engineering is still largely missing the "engineering" part.
By that I mean the ethos and the risk aversion, and the personal responsibility in case of catastrophic failure.
Because we are having way too many catastrophic failures in IT still. This needs to be fixed.
define "everyone", please 😉
I'd almost say the opposite: there are simple concepts, simple algorithms and so on, but their structure is insane.
You can build GCC on an x86 Linux (glibc) so that it will builds statically linked binaries for Windows x86_64 (newlib-cygwin) on a AArch32 running NetBSD (for several languages).
The simple fact that Canadian crossing is possible and supported should give an insight about the internal #complexity of #GCC.
With GCC you also build `libgcc` a library against which each GCC built binary is linked to ease some optimizations. This is another hint: compilers are not as simple and modular as one might think from an high level description of them.
Finally it's not entirely true that you can disable every optimization: not only because there is no real difference between optimizations and other transformations during the compilation process but also because most of the combinations of optimizations have never been really tested.
So I'd argue that for a tester, modern compilers are the one of the worst possible nightmares of today computing.
Yes, they are functional, but I'd guess nobody would live enough to seriously test each possible combinations of options of a single GCC release to ensure it maps each possible input to the correct output.
@Xipiryon @ekaitz_zarraga @suetanvil@mastodon.technology
Actually, I think that this is the real answer to the @ekaitz_zarraga's question.
I don't know about #clang, but GCC's (huge, overwhelming) complexity is mostly due to the supported combinations of
- languages
- architectures
- operating systems
- optimizations
- diagnostics / debug
- internationalization
Reading this from top to bottom might give you an insight: https://gcc.gnu.org/install/configure.html
#GCC is not just a #C compiler but the #GNU Compilers Collection.
It tries to maximize the possible use cases, including several niches and corner case that are simply not considered by simpler C compilers.
Why?
Well, there is obviously an ideological aim: providing #Software #Freedom through an high quality compilers suite to everybody, no matter how peculiar are their needs (to reduce the attack surface from proprietary software).
But there is also a reasonable architectural goal: maximize the reuse of a large high quality code base that is common among the various combinations of need.
The price of this is a huge complexity, due to the tensions between different perspective on how computing should work.
I don't like such complexity (really, I hate it), but it's very short-sighted to blame it without understanding the overall vision that GCC pursuits.
@suetanvil@mastodon.technology @codewiz
I'm not.
As long as the implemented behaviors are properly documented, undefined behaviours can be useful hooks: don't forget that C is a language designed to be used in a wide variety of use cases: portability is valuable in many of them, but sometimes is not relevant at all.
C'è una profonda differenza fra andare dove ci sono persone in catene per liberarle e mandare persone a farsi incatenare o sponsorizzare/normalizzare i carcerieri.
Essere su #Facebook e #Twitter per raggiungere le persone che vi sono intellettualmente recluse è necessario. Ma bisogna spingerle fuori.
Non si può linkare (ovvero alimentare con i dati di tutti i visitatori che non usano uMatrix) un sistema di sorveglianza e poi non condividerne "il modo di comunicare".
L'unico modo per usare questi sistemi senza esserne usati è postare link a contenuti esterni.
@filippodb @madbob@mastodon.technology
On January/February 2020 I'm going to give #GNUnet a new try with some italian friends (after a decade or so...).
May we ask you some questions if in throuble? Do you have any specific reading to suggest?
I mean beyond https://gnunet.org/en/use.html and https://docs.gnunet.org/handbook/gnunet.html
It appears I'm the first who updated their #GNUnet nodes to 0.12 release.
Can only see my other* node in connection monitor.
* With another one recompiling at the moment.
Linguists Hear An Accent Begin - Scientific American
https://www.scientificamerican.com/podcast/episode/linguists-hear-an-accent-begin/ #linguistics
"Today, the difference between a programmer and a nonprogrammer is that the programmer was told to overcome obstacles while the nonprogrammer was told to give up."
Rv8 – RISC-V simulator for x86-64
https://rv8.io/
(submitted by lelf)
@Blort join the #VOICE group and test with us! Reports on the tests we've done so far are (or will be) here:
https://hub.libranet.de/channel/voice
But TL;DR based on my experiences so far ...
I guess we are all programming bitches, after all... 😂
Google is blocking niche Linux browsers from accessing services like Gmail https://www.omgubuntu.co.uk/2019/12/couldnt-sign-you-in-google-browser-error-linux