17 ms·
Weird architectures weren't supported to begin with
- gsnedders 6y ago"The absence of official builds means that" [incomplete sentence]
- woodruffw 6y agoWhoops, that was a transposition. Thanks, fixed.
- deleted 6y ago[deleted]
- nerdponx 6y agoNo free work for platforms that only corporations are using. No, this doesn’t violate the open-source ethos; nothing about OSS says that you have to bend over backwards to support a corporate platform that you didn’t care about in the first place.
- avereveard 6y ago> Your user base is unhappy It isn't the owner user base if it comes from an unsupported third party build.
- woodruffw 6y ago> It isn't the owner user base if it comes from an unsupported third party build. Maybe this is strictly true, but it isn't how the maintainer/packager model has historically worked: packagers do point users to the upstream for troubleshooting, and the upstream points prospective users to the packagers for installation. It's a marriage of convenience (and philosophy), but it doesn't imply the arbitrary patches and/or changes to the project itself are somehow supported by their upstreams.
- alisonkisk 6y agoNo. Package manager should never send a bug reporter upstream. It's the package manger's job to investigate the issue and file a bug with upstream including proper context, unless the bug is reported on multiple distributions.
- account42 6y agoThat is just unreasonable. For build issues, especially ones that the packager can reproduce - making sure that all that is reported properly makes sens. But most bugs are not that - playing the telephone game here helps no one.
- Lammy 6y agoWhile technically true, that doesn't mean users will understand that and send their bug reports to the right place. For some historical examples of maintainer burnout and community clashes, see QuodLibet vs Gentoo in 2005/2005: https://bugs.gentoo.org/101619 https://bugs.gentoo.org/101619 / https://bugs.gentoo.org/124595 https://bugs.gentoo.org/124595 And GAIM (Pidgin) vs Gentoo in 2003 (https://bugs.gentoo.org/35890 https://bugs.gentoo.org/35890), where we can see that nothing ever really changes, RE: "You don't happen to be using an architecture other than x86, do you?"
- ziml77 6y agoWow, what a shitty exchange between Gentoo maintainers and Quod Libet's developer. They actually told the dev to do the work of fixing the distro's packages! Is the Gentoo community still that awful 15 years later?
- Lammy 6y agoNah, this was like funroll-loops-dot-info era and we all grew up. I don't know what distro Kids These Days prefer.
- titzer 6y agoI thought very hard about this problem as I've developed Virgil [https://github.com/titzer/virgil https://github.com/titzer/virgil] over the years. Bootstrapping any system, not the least of which a new programming language is a hard problem. Virgil has an (almost) hermetic build. The compiler binaries for a stable version are checked into the repository. At any given revision, that stable compiler can compile the source code in the repo to produce a new compiler binary, for any of the supported platforms. That stable binary is therefore a cross-compiler. There are stable binaries for each of the supported stable platforms (x86-darwin, x86-linux, JVM), and there are more platforms that are in the works (x86-64-linux, wasm), but don't have stable binaries. What do you need to run one of the stable binaries? 1. JVM: any Java 5 compliant JVM 2. x86-linux: a 32-bit Linux kernel 3. x86-darwin: a 32-bit Darwin kernel* [*] sadly, no longer supported past Mavericks, thanks Apple The (native) compiler binaries are statically-linked, so they don't need any runtime libraries, DLLs, .so, etc. Also, nothing depends on having a compiler for any other language, or even much of a shell. There is test code in C, but no runtime system or other services. The entire system is self-hosted. I think this is a decent solution, but it has limitations. For one, since stable executables absolutely need to be checked in, it's not good to rev stable too often, since it will bloat the git repo. Also, checking in binaries that are all cross-compilers for every platform grows like O(n^2). It would be better to check in just one binary per platform, that contains an interpreter capable of running the compiler from source to bootstrap itself. I guess I'll get to that at platform #4.
- breakfastduck 6y agoQuestion from a point of ignorance - why would you target 32bit for something that is being actively developed? Are we not at a point where 64bit should be the expected target?
- nickysielicki 6y agoThere’s a weird mental leap that rust evangelists, militant atheists, and hyper-progressives have in common. I like rust as much as the next guy but the zealotry is unbelievable. It’s almost getting to the point that I’m rooting for rust to fail and for C++ to just continue to get better, just so that these people who claim to take memory safety so seriously might shut the fuck up about it. The gentoo folks “complaining” about this have contributed more to LLVM (and, by extension, rust) than 95% of the people arguing that they’re in the wrong. edit: what I ultimately have an issue with is tearing down the past because we see a brighter future on the horizon. The baby is being thrown out with the bath water.
- steveklabnik 6y agoRust has contributed a lot to LLVM, see here for a recent summary: https://twitter.com/pcwalton/status/1366058442276790274 https://twitter.com/pcwalton/status/1366058442276790274
- wizzwizz4 6y agoTrue, but most Rust zealots (including me, though I'm reformed) haven't contributed anything to LLVM. Most Rust developers aren't Rust zealots. It's largely people who are new to the language, I think.
- steveklabnik 6y agoThe original person said "evangelists" and then slid into "zealotry." And I find a lot of anti-Rust folks seem to think anyone who likes Rust is a "zealot." YMMV. I think that this is just a hard conversation to have, with a ton of different groups who all want different things, and have different incentives.
- nickysielicki 6y agoI like rust. What I don't like is people who pretend that unsafe rust is any better than C++ or C.
- thesuperbigfrog 6y agoIt seems like the easiest answer is to fork the cryptography library: - current maintainers and those who are on supported architectures can use the Rust implementation. The current maintainers no longer want to maintain the C implementation and that is their prerogative as this article describes. - new maintainers and those on unsupported architectures can continue to use the C implementation. Not everyone in the current user base (to include some distribution maintainers) is able to use the new Rust implementation at this time, but they still need the library. It's not ideal, but it seems like the only practical way ahead that meets everyone's needs.
- Chyzwar 6y agoThere is a high chance that there is no pyca/cryptography users on these niche platforms that Gentoo is trying to support. If there are any, they should pay for support not expect maintainers to support theirs fridge platform.
- viraptor 6y ago> support theirs fridge platform. I love this typo in context of s390!
- sanxiyn 6y agopyca/cryptography was an indirect dependency of Gentoo's package manager, Portage. Portage is written in Python. So by definition, there were users. "was", because after this incident, careful review revealed that it isn't necessary, and dependency got removed. So yes, probably no users now.
- msla 6y agoSpeaking of fridge platforms, does LLVM target any PIC ISAs?
- toast0 6y agoIf Gentoo doesn't work on fridges, what's up with this: > The Gentoo/s390 Project works to keep Gentoo the most up to date and fastest s390 distribution available. That's a declaration of support, and if that's not what they mean, they could list some limitations on their wiki. [1] A lot of system distributions declare some platforms as supported and others as best effort and still others as probably not working, but you're welcome to try. That's reasonable, of course, but it's nice if you're upfront about it. [1] https://wiki.gentoo.org/wiki/Project:S390 https://wiki.gentoo.org/wiki/Project:S390
- alisonkisk 6y agoThis yet another example of why gift economy members need to understand that you don't owe anyone support. If you publish As-Is, thank you. If you promise to support the OS/Hardware in your lab, thank you. If you accept patches from users with weird use-cases, thank you. If you get too much bug spam, you need to set up filters and auto replies and volunteer helpers to help you find the reports you care about. You don't owe anyone support.
- macksd 6y agoThis is definitely the most reasonable case I've heard made from this argument, and it's changed my stance on the issue. That said, I feel the cryptography project handled this poorly. I encountered the issue when one day, installing a Python Ansible module the same way I did the day before required a compiler for a different language that I've never used before and that is hardly used, if at all, in the rest of my stack. The Ansible project seemed to be taken by surprise, and eventually I found the root upstream issue, where the initial attitude was "too bad". Some people making those comments worked for Red Hat / IBM, Ansible is heavily backed by that. What company cares more about Linux on S390 than Red Hat / IBM? I would suggest none. So the fact that they had this attitude and community reaction to me suggests the problem is not one of expecting free work for a corporation on a non-free architecture. It was IMHO a combination of a lack of forethought, communication, and yes, perhaps a change that is overdue and will just be a little painful. The suggestion to maintain an LTS release while people figure out how to proceed is the right move.
- steveklabnik 6y ago> Some people making those comments worked for Red Hat / IBM, Ansible is heavily backed by that. Okay, so, I don't mean to pick on you here, but I've seen this sentiment cropping up a few times. Not everyone can be familiar with everything, but I would caution you against immediately assuming corporate politics are at the root here. Anyone familiar with Alex Gaynor and his work over the last few years would know that he cares about Python, and memory safety. That has remained consistent regardless of his employer. Immediately assuming that this has something to do with company politics, rather than just a tireless open source contributor working to improve the things that he cares about, for years, is making a bit of a category error, in my opinion.
- macksd 6y agoI agree - I don't feel picked on :D I guess my point is that it's overly dismissive to say "no free work for companies on niche architectures" when projects backed by the same company were a bit blind-sided by this and a bunch of people lost time chasing down what happened and why. To me that's a sign that this isn't just a mismatch of ideology or someone wanting free work: it was a failure in communication and mismatched expectations. If it had just been on a major version bump, I wonder if we'd even be having this discussion.
- hedora 6y agoI’ve noticed I can predict a lot about the quality of code an engineer produces by listening to their opinions on testing in strange environments. People interested in stamping out undefined / nondeterministic behavior / compiler warnings welcome bug reports from platforms that find new bugs. They also are more conservative about including dependencies, and their code is much, much more maintainable over time.
- alisonkisk 6y agoSomeone dedicated to debugging complex software on strange environments probably writes no code at all, since they spend all their time investigating bugs. Your comment is rudely dismissive of people giving you the product of their labor for free.
- asguy 6y agoDo you disagree with their personal experience? Does it not match yours? Their experience matches mine. It’s one of the reasons I appreciate projects like Net and OpenBSD, who actively keep old hardware around. They find bugs, by actually exercising their code base in unplanned ways (e.g. endian differences, alignment constraint differences).
- sgift 6y agoIt doesn't match mine since there's usually far more work to do than time available to do it. Most projects have to heavily triage bug reports and "your program fails on my platform that no one has built in 30 years" has a very low rate of "helpful to anyone else but the bug reporter".
- asguy 6y agoDo you never stop and think “why is our code base busted in this person’s environment?” I mean, it could just be that the bug filer just hasn’t done their due diligence on upgrading (why won’t win 3.11 play crysis). It also could be that your code quality sucks and you’re writing something non-portable.
- h2odragon 6y agoIf I fire up an Alpha CPU today, I'm not expecting that the latest versions of all my favorite free software is going to run on it. Asking maintainers to "fix it for me" then would be unreasonable. Part of running hardware that far out of date is hunting for the last versions of anything that supported it; whether that was FOSS or commercial its still the way the world is and has been. It'll be interesting to see how the Rust community responds to this; are they so eager to absorb everything that they'll put effort into supporting niches to get more users,or will they take the opportunity to be "opinionated" and exclusive and shed the effort of catering to obsolescence?
- cbmuser 6y ago> If I fire up an Alpha CPU today, I'm not expecting that the latest versions of all my favorite free software is going to run on it. Asking maintainers to "fix it for me" then would be unreasonable. No one does that. What people complain about is that code that used to be perfectly portable for years suddenly becomes locked to a very limited set of targets with the argument that memory safety is more important than anything else. > It'll be interesting to see how the Rust community responds to this; are they so eager to absorb everything that they'll put effort into supporting niches to get more users,or will they take the opportunity to be "opinionated" and exclusive and shed the effort of catering to obsolescence? Rust just needs to help get one of the several alternative Rust implementations based on gcc officially supports similar to gccgo. Then the portability issue will have been fixed once and for all and Rust will be chosen even for code on obscure targets such as Elbrus 2000, Sunway or Tricore.
- pornel 6y agoThe code that used to be perfectly portable still exists, fork it and keep using it. But if you're asking for a project to be maintained, then it means you want maintainers to put more work to keep new code working on an old platform. Constraints of old/niche platforms cause extra work for developers when adding new features or improving security.
- longcommonname 6y agoThey can pin an older version and have it work.
- ris 6y agoProblem is that ARM & AArch64 were considered a "weird architecture" by the non-Android linux stack until really very recently, and the migration to a new architecture is still not plain-sailing in many peoples' experience. Without the assumption that most open source package authors are implicitly trying to be architecture-independent to some degree, we will literally all be stuck on x86_64 for the rest of our lives (the migration to amd64 itself I remember as being a number of years of people working on "unsupported" stuff FWIW). For users on "weird architectures" to be petitioning that a move the pyca authors are making is causing inconvenience to them is perfectly reasonable in my eyes.
- steveklabnik 6y agoIncidentally, aarch64-unknown-linux-gnu became a Tier 1 supported platform in Rust recently, in part because of the support of ARM themselves. (My day job involves a lot of Tier 2 ARM work, and I don't personally run into any more bugs than Tier 1 platforms. YMMV.)
- rodgerd 6y ago> Problem is that ARM & AArch64 were considered a "weird architecture" The ARM world is a blizzard of proprietary, undocumented implementations with limited support for the upstream kernels, often can boot only a vendor-specific distro that is quickly abandoned, and full of boards that blink in and out of existence at the drop of a hat. It absolutely is a weird architecture. > For users on "weird architectures" to be petitioning that a move the pyca authors are making is causing inconvenience to them is perfectly reasonable in my eyes. Yes, this is exactly the sense of entitlement that the author is talking about when he describes the destruction of people's interest in working on open source.
- ris 6y ago> this is exactly the sense of entitlement Now come on with your "entitlement". It's not as though we're talking about some random people who made some little package for their own use and decided to make it available in case anyone else found it useful, and now the community demands from them are becoming too much and are something they never asked for. This is a group that have named themselves the Python Cryptographic Authority and have chosen the prominent pypi package name of just "cryptography". They couldn't have done any more to encourage the broader community to depend on it and make it a core part of their stack. In comparison, I couldn't imagine the python core team (also largely unpaid) doing this with one of their stdlib modules and then dismissing those objecting as "entitled". (FWIW I'm not particularly interested in taking a side in this issue, but think your labelling as "entitled" is unhelpful)
- arithmomachist 6y ago> Companies should be paying for this directly: if pyca/cryptography actually broke on HPPA or IA-64, then HP or Intel or whoever should be forking over money to get it fixed or using their own horde of engineers to fix it themselves. This about sums it up.
- SAI_Peregrinus 6y agoPackagers often fork software, but confusingly don't give the fork a new name. If an upstream project includes build scripts, then they're part of the project and any changes to the build scripts constitute a fork. Any patches to the actual code are even more clearly a fork. The article lists the following 5 things packagers sometimes do: 1. Build your project with slightly (or completely) different versions of dependencies This doesn't necessarily require a fork. If you use static linking of dependencies it mostly does, but things like libc are often dynamically linked. 2. Build your project with slightly (or completely) different optimization flags and other potentially ABI-breaking options If you're providing a build script, and they're changing this, it's a fork. 3. Distribute your project with insecure or outright broken defaults If they're changing the provided code or configuration defaults, it's a fork. 4. Disable important security features because other parts of their ecosystem haven’t caught up It's a fork. 5. Patch your project or its build to make it “work” (read: compile and not crash immediately) with completely new dependencies, compilers, toolchains, architectures, and environmental constraints It's a fork. Project packagers should rename projects they fork. Project authors should make it easy to rename forks, preferably with a single location that defines the project name. Forks aren't a bad thing. But not labeling them correctly leads to quite a bit of confusion.
- Spivak 6y agoIf you’ve ever poked around the spec files for Fedora, CentOS, or RHEL you know that this wouldn’t work. Everything is extensively patched. You might as well just call everything rhel-$project. Some projects genuinely have a hundred separate patches. Linux distros simply wouldn’t work without this. Once you have two pieces of software that depend on different versions of libfoo or two different versions of glibc it’s over. Nix is doing heroic work in this space but it’s also doesn’t care that you have 12 different versions of zlib that in an enterprise world still need security backports because upstreams don’t do that.
- genuine_smiles 6y ago> You might as well just call everything rhel-$project. Is this a bad option?
- deleted 6y ago[deleted]
- panny 6y ago>outside of hobbyists playing with weird architectures for fun These are also the most likely people to be able to remove dependency on your project making it less relevant. That's what happened with Gentoo. They didn't bother forking. They found an alternative and python-cryptography is now dead to them. This doesn't even get into what a bad idea it is to build crypto code with mystery binaries like rustc in the first place. Yes, you can bootstrap rust from source if you are really brave/stupid. Nearly nobody does it though, because rust seems purpose built to make you dependent on the official binaries. Building rust version N requires building version 1-N. Latest version is something like 50, which makes bootstrapping it absurd. Memory safety is nice, but Java has been around for decades. Memory safety didn't solve everyones' problems. People still use C for good reasons. Breaking distros won't win Rust lots of friend.
- ndesaulniers 6y agoThis comes up a lot with my work on compiling the Linux kernel with LLVM. So much so I've made a tier list to describe what I picture as a Venn diagram of support: https://clangbuiltlinux.github.io/ https://clangbuiltlinux.github.io/ Also recently seen on this topic: https://people.gnome.org/~federico/blog/librsvg-rust-and-non-mainstream-architectures.html https://people.gnome.org/~federico/blog/librsvg-rust-and-non... https://www.reddit.com/r/rust/comments/lfysy9/pythons_cryptography_package_introduced_build/gmq9vi8/ https://www.reddit.com/r/rust/comments/lfysy9/pythons_crypto...
- eqvinox 6y agoDoes the "powerpc" listed really mean "ppc64le" and the "s390" really mean "s390x"? Certainly feels like it, but I'm not sure... If you're already making such a nice overview, could you maybe not mar it with such ambiguity? Kinda defeats the purpose :( [Ed.: even "x86" is confusing. x86_64 does work, right?]
- ndesaulniers 6y agoNo. The kernel doesn't make such distinctions. The convention used is what the kernel sources call them under arch/. See arm64 vs aarch64 for example.
- eqvinox 6y agoI guess that means that overview is for kernel developers. Those directory names are meaningless to me as an user... FWIW, I'm actually asking out of a real need. I have two powerpc boxes (no, not ppc64le) here, which we use for testing big-endian compatibility. But last I checked, LLVM supported neither 32-bit PowerPC nor big-endian PowerPC. Actually... I guess the real argument is that the kernel directory names aren't sufficient. Because they specify architecture families, not architectures. [And, funnily enough, LLVM does actually seem to support 32-bit BE PowerPC. Now I'm really confused.]
- ndesaulniers 6y ago
- ncmncm 6y agoIt Seems To Me that a little more attention to cross-compilation support would go a long way toward extending support to all the weird architectures. Really, running a language toolchain on the target machine, where the target machine isn't what everybody has, is largely pointless. We each have loads of machines to run toolchains on. Early in the life of a language, with a compiler meta-circularly written in it, the compiler is the biggest program in the language, so may seem like an effective early test of a port. But, it must be said, meta-circularity is, in large degree, wankage. There are much better choices to demonstrate the merits of your new language than coding its compiler; a compiler is not the persuasive demonstration of language merit it once was. Writing your language's compiler in an unstable and unreliable new language, making it subject to its own bugs and early inefficiencies, is a poor way to help a new and fragile user community up to speed. How did we get on this meta-circularity fetish, anyway? It's easy to see how it happened with C, but aping what C did is no formula for success, anymore. C is, or once was, a pretty simple language to compile, so its compiler wouldn't much benefit from being implemented in a more powerful language, if there had been any. That cannot be said of modern languages, where all the help you can give them is just enough to make a usable compiler. Notably, LLVM is coded in (a dialect of) C++, even the project's C compiler. A cross-toolchain, coded in C++, built to run on Linux amd64 and nowhere else, ought to be all you need to bring up full support for any language on any architecture. As we say about low Earth orbit, it puts you halfway to anywhere in the universe. Even where you don't have Linux, you have a VM you can run it in. Cross-development skills take some investment, but they pay forever after. The overwhelming majority of places you could run code nowadays can't meaningfully host a development environment anyway. Cross skills enable you to program the microcontrollers that manage about everything in the world, today, and phones, and HPC supercomputers alike. A cross-built program can not only be built on your desktop host machine. It can be debugged from there, running in an emulator or on the actual target hardware. The debugger runs on the host, with access to all the source code. What we call a "debug stub", a tiny fragment of code is inserted in the program or target environment that implements the minimal primitives a debugger needs: mostly just peek, poke, and run; maybe watchpoints if the target supports that. The debugger talks to the stub over a network port, or a serial cable, or by blinking lights, if necessary. Linux on amd64 didn't take over the world, with no marketing budget in sight, by being the best place possible place to run programs. (It's just adequate, and better at it than Windows.) Linux got there by being the best possible place to develop software. Make it the best place to develop in your language, whatever the target, and you are halfway to anywhere.
- reidacdc 6y agoI'm not hugely knowledgeable about LLVM, but it was my understanding that a major benefit of it was separating out high-level from low-level concerns. There are lots of practical issues, obviously, but the dream was that the LLVM intermediate representation would take the role of C in the author's description, with the major difference that nobody has to actually hand-write anything in it. So from that point of view, isn't the robust, long-term solution to this and related issues to build LLVM back-ends for all the "weird" architectures? I'm surprised it's not mentioned as a possible way forward.
- qbasic_forever 6y agoYes, the reality is all those weird architectures stopped being developed and actively supported 20 years ago. If someone wants to get some old Itaniums and Alphas and such together to hack in support, go wild and have fun. But the reality is the venn diagram interesection of people knowledgeable enough to create a LLVM backend, people motivated to support vintage architectures, and people that actually have the hardware available and ready to test is basically zero. If people in the community are passionate about it happening then organize and make it a reality.
- rodgerd 6y agoIt's also that - per the article - it goes beyond "willing and able to implement in LLVM". Because that doesn't let the Rust devs or the Python devs test on those vintage platforms.
- kps 6y agoThe problem is that LLVM IR is not stable across releases, so keeping an out-of-tree back end up to date would be expensive.
- deleted 6y ago[deleted]
- tom_mellior 6y agoLLVM IR is not platform independent: https://releases.llvm.org/8.0.0/docs/FAQ.html#can-i-compile-c-or-c-code-to-platform-independent-llvm-bitcode https://releases.llvm.org/8.0.0/docs/FAQ.html#can-i-compile-... There is no "compile to LLVM once, run anywhere with an LLVM backend". If your C frontend doesn't know that you want to compile for System/390, it will not be able to generate LLVM code that you can expect to turn into a working System/390 binary.
- dfox 6y agoI think that main issue in this is the pyca/cryptography library itself and its unfortunate name. It bundles three only marginally related things (high-level symmetric encryption API, X.509 handling and bunch of cryptographic primitives) things into one library that is first result on google for "python cryptography". The end result of this is that another libraries which need only some small part (which is probably better provided by some other python crypto package) depend on the whole library.
- Fordec 6y agoI do think that we're going to see more of this. This is just a relatively early example. Rust and LLVM bring things to the table that make them inevitable if we as an ecosystem, on the whole, value privacy and security. This is where the rubber of the ethos hits the road. C for all it's good work and history, is a leaky mess and the source of so many zero-days, especially the bad bad state actor level ones. If we are to move to a more abstracted and safer system, the ideas behind LLVM are just going to be a fact of life in years to come. The solution to this is to either fund greater LLVM integration (or similar that isn't on the scene yet) or accept the status-quo. I choose the former, but I sincerely hope the future direction leaves as few out in the cold as possible through the effort of smart people. But protecting hobbyists is a stretch goal in my mind compared to improving the security and privacy of the global interconnected world we're in.
- JoeAltmaier 6y agoDon't know about crypto. But any open source package, ported to a new environment (one not explicitly tested by the maintainter) is going to have issues. That's the nature of software. E.g. I just added pnglib to an embedded assembly. Has a display among other things. Wanted to put compressed PNG images into (limited) flash, then decompress into (plentiful) RAM at boot. Of course pnglib didn't build for my environment. Never mind it has a C library. There are 50+ compile switches in pnglib, and I was setting them in a pattern that wasn't part of the tested configurations. It didn't even compile. Once it compiled (after some source changes) it didn't run. More source changes and it would run until it hit some endianness issues. Fix those, and it would do (just) what I wanted, which was to decompress certain PNG image formats with limited features, once. No problem. That was my goal, achieved. But at no time did I blame the maintainers for not anticipating my use case. I would say this: maintainers, flag compile-time options that aren't tried both ways in your test environments. To give me some chance of estimating how hard my job is going to be.
- tptacek 6y agoThe software in this story is working as intended in its new configuration. It's not reasonable to ask for features to be flagged off on the off chance that someone is running your code on an S/390.
- JoeAltmaier 6y agoIf your test cases don't try it, I'd recommend either removing the code or documenting that the flag is not optional? For industrial code that would be an ordinary, expected process. But open source gets a lot of passes on process.
- carapace 6y agoSomething's fishy here... This is the first I've heard of the whole thing, so forgive me if I'm just bloviating. As a political move to advance the cause of memory-safe languages, as Alex Gaynor clearly intends†, this is obviously kind of a fiasco. The arguments about who's going to pay for safer software are uninteresting. It's like arguing over who is going to run into the burning building to save the baby. Put some liability laws in place and see what you get? As for Rust not supporting "weird architectures", are y'all serious about being the new contender or not? C isn't going to give up the title without an epic fight. Love it or hate it, to a first approximation C is programming. †I do not mean that in a negative way. FWIW I'm referring to https://www.usenix.org/conference/enigma2021/presentation/gaynor https://www.usenix.org/conference/enigma2021/presentation/ga... which I just read. Personally, I'm at "Bargaining" stage, I think we can still "turd polish" C into something and Rust seems to me to be waaaaaaaay too complex (to replace C. It sure is fun though, eh?)
- acdha 6y ago> As a political move to advance the cause of memory-safe languages, as Alex Gaynor clearly intends†, this is obviously kind of a fiasco. I’m not sure about that: there’s been a few people vocally complaining but it doesn’t seem like they’re getting much traction. I’d see this working as well for other maintainers saying “people using hardware which has been dying since the 90s aren’t a major constituency and I’d like the huge safety and productivity benefits of Rust”. I find it interesting that you describe Rust as too complex to replace C, when I generally see it as the reverse: I’ve written C off and on since the early 90s and it’s almost always felt like a chore because you have to do so much yourself that newer languages do for you. Rust hit a better comfort level after a couple hours because it was so much more productive that I could start making progress on design refactoring which had been postponed due to how tedious it would have been to do it before.
- carapace 6y ago> I’m not sure about that: there’s been a few people vocally complaining but it doesn’t seem like they’re getting much traction. You don't see the problem with that? People (who already use a memory-safe language!) shouldn't be complaining when their crypto gets rewritten in a memory-safe language. If they are, someone shat the bed. And if your users are complaining but getting no traction, that is a (second!) shitting of the bed. > other maintainers saying “people using hardware which has been dying since the 90s aren’t a major constituency and I’d like the huge safety and productivity benefits of Rust”. We all want safe software. People aren't upset by choices being added, they are upset about something they (thought) they had that has now been taken away. If you break a bunch of people's stuff and then tell them "fuck you, pay us" or "your platform isn't hip enough" it's kind of a dick move, eh? The "optics" are bad. - - - - In re: complexity of Rust vs. C: The measure of complexity of a system isn't the ergonomics of the tooling, it's the time/effort for a newbie to achieve competence, eh?
- pdimitar 6y agoSo, we have to choose between... - A tiny community of hobbyists willing to support niche architectures that have zero relevance to any mainstream computing, OR - Embrace a newer, stricter ecosystem with more guarantees and clearer communicated support tiers that's also constantly improved upon by a big number of both dedicated volunteers who donate their time and effort, and paid professionals. The only tradeoff: it supports less architectures. For now. Am I understanding the article correctly? If so, I am definitely in favor of the latter, and I think many others are as well.
- alacombe 6y agoIt's interesting that the community praising multiculturalism favors hegemony of only a few computer architecture. Portability used to be paramount of design...
- wmf 6y agoMost CPU architectures are "fake diversity"; for example both Alpha and ARM64 are 64-bit little-endian with a weak memory model. Sure, S/390 is 31-bit and supports BCD while in PA-RISC the stack grows upwards and IA-64 is VLIW, but these are trivia that are not comparable to the diversity of human cultures. For decades programmers have wasted their time porting software to different-but-not-better architectures, mostly for the benefit of the vendors who fragmented the market in the first place instead of standardizing.
- alacombe 6y ago> For decades programmers have wasted their time porting software to different-but-not-better architectures Microarchitecture, register layout, ABI also constitute differences which have real-world uses, Not to mention sheer competition to avoid architecture-rot. Only targeting intel & ARM opens yourself to problems, cf. the upcoming nVidia hell ARM is about to experience. Just because Rust-preaching (without practicing it, of course) Starbucks-spipping average HN readers don't know about it doesn't make it inexistent or necessarily wrong-think.
- acmj 6y agoIf I were the maintainer, I would create cryptography2 and put the original cryptography into the bugfix mode. It is time to move to a safer language, but breaking backward compatibility is always bad.
- epage 6y agoWhat is breaking backward compatibility? Using new python features? Using new C features? Bug fixes? To have any sanity as a maintainer, you have to draw the line somewhere.
- AlphaSite 6y agoIt’s continued to support the architectures which it promises to support and its API compatible. I don’t think making a change which breaks a third party, out of tree, port is breaking backwards comparability, this feels more like someone depending on internal implementation details.
- 0xdeadfeed 6y agoBut C4, cancer that it is, finds its way onto every architecture I stopped reading here. If you can’t be objective about a topic, don’t bother posting it on a neutral platform.
- saagarjha 6y agoThis was clearly not meant to be a value judgment.
- yellowapple 6y ago> open source groups should not be unconditionally supporting the ecosystem for a large corporation’s hardware and/or platforms. Then by this logic I'm going to stop developing against pretty much every ISA aside from maybe RISC-V, and even that's a stretch. x86 users can piss off until Intel, AMD, and/or VIA cough up some dough to my single-digit-user-count FOSS projects. ...obviously this idea, if taken to its logical conclusion, basically means the death of open source software development as we know it. The author had a decent point until not only suggesting to refuse to support "niche" platforms entirely, but to make that suggestion the "most important". As a counterexample to the author's point, see OpenBSD's support for platforms unsupported by Rust. The rationale there is not for monetary gain, but for two key reasons: 1. People want to be able to run OpenBSD on whatever hardware they've got lying around, and when they figure out how to do it they might as well help others do the same. 2. In line with the author's point about how most C developers make platform-specific assumptions about the code they write, OpenBSD targeting a bunch of "niche" platforms with oddball conventions helps catch those assumptions early - and with them, any lurking security bugs deriving from those assumptions failing.
- ohgodplsno 6y agoSigh. The HackerNews standard of pushing some logic to its limits and going "HA, GOTCHA" is getting tiring. x86, x86_64, ARM are used by billions of people around the world. It's easy to see that there is actual value for end users by supporting these platforms. John Doe from accounting can easily use your open source software and it will benefit him. The clear benefits of supporting z/OS, aside from helping IBM push out more of their mainframes and making more money, are unclear. Supporting PA-RISC, POWER or any other esoteric architecture whose sole purpose is to make their vendors sell million dollar support contracts should not be anyone's priority, and if indeed they do want this software on their non-standard, non-widely used ISA, they can use some of these millions to fund LLVM development.
- yellowapple 6y ago> Sigh. The HackerNews standard of pushing some logic to its limits and going "HA, GOTCHA" is getting tiring. So is the Hacker News standard of ignoring the entire point just to nag about said supposed standard. Sigh. Said entire point, specifically, being that there are far more reasons to develop and maintain software beyond "value for end users", and that even when targeting that specific reason, developing against esoteric cases does ensure the software is more robust even for "normal" use cases. (And mind you, logic - like software - should be pushed to its limits, because that's the most surefire way to identify its flaws - like, for example, the failure to consider that nearly all computing platforms in existence and use today were and are the product of some large corporation that could be paying your bills but won't, or the failure to consider that it's users, not hardware vendors, who are generating support requests for their hardware)
- platformlover 6y ago"No free work for platforms that only corporations are using." The opposite is true. HP stopped supporting hppa 8 years ago. Intel had last orders for ia64 CPUs more than a year ago. There are no companies who would pay for anything, today maintainance of such platforms is entirely an open source community effort.
- qwerty456127 6y agoWhy can't we just develop an LLVM backend to output C code?