GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    Rich Felker (dalias@hachyderm.io)'s status on Sunday, 17-May-2026 00:14:18 JST Rich Felker Rich Felker

    Over the past few months my opinion of Rust has gone from

    "promising technical approach, poor willingness to understand others' past mistakes and how to avoid making them, somewhat hostile to existing standards and ecosystems but likely salvagable"

    to

    to "everything about this language and project is an utter dumpster fire".

    In conversation about 6 days ago from hachyderm.io permalink
    • Embed this notice
      Rich Felker (dalias@hachyderm.io)'s status on Sunday, 17-May-2026 00:14:30 JST Rich Felker Rich Felker
      in reply to

      Like, I'm almost to the point where I want nothing to do with anything written in Rust.

      In conversation about 6 days ago permalink
    • Embed this notice
      Rich Felker (dalias@hachyderm.io)'s status on Sunday, 17-May-2026 00:41:39 JST Rich Felker Rich Felker
      in reply to
      • XANTRONIX

      @xan The language of scabs.

      In conversation about 6 days ago permalink
    • Embed this notice
      XANTRONIX (xan@xantronix.social)'s status on Sunday, 17-May-2026 00:41:41 JST XANTRONIX XANTRONIX
      in reply to

      @dalias It's incredibly baffling to me how frequently it has been demonstrated in the course of uutils development how little people have referenced even coreutils CVE data or taken care to understand really basic things, like, /dev/tty or the file descriptor-oriented calls that make shit safer

      it seems less like an exercise in safety and more a clean room effort to relicense a thing in an ecosystem popular with the kids

      In conversation about 6 days ago permalink
    • Embed this notice
      Rich Felker (dalias@hachyderm.io)'s status on Sunday, 17-May-2026 00:57:01 JST Rich Felker Rich Felker
      in reply to
      • XANTRONIX

      @xan It's not just the LLM usage that's anti-labor, but the friendliness to RIIR projects that exist primarily to displace or outright LLM-copyright-launder existing copyleft and/or LLM-unfriendly upstreams.

      In conversation about 6 days ago permalink
    • Embed this notice
      XANTRONIX (xan@xantronix.social)'s status on Sunday, 17-May-2026 00:57:02 JST XANTRONIX XANTRONIX
      in reply to

      @dalias it's hard for me to call everyone i know using it a scab (in any sense of the word including anti-labour LLM usage) but i'll be goddamned if there aren't a lot of LLM lovers out there who really want to infect the community

      In conversation about 6 days ago permalink
    • Embed this notice
      Rich Felker (dalias@hachyderm.io)'s status on Sunday, 17-May-2026 00:59:54 JST Rich Felker Rich Felker
      in reply to
      • Haelwenn /элвэн/ :triskell:
      • XANTRONIX

      RE: https://hachyderm.io/@dalias/116585071770277275

      @lanodan @xan Yep. And..

      In conversation about 6 days ago permalink

      Attachments

      1. No result found on File_thumbnail lookup.
        Cassandrich (@dalias@hachyderm.io)
        from Cassandrich
        @xan@xantronix.social It's not just the LLM usage that's anti-labor, but the friendliness to RIIR projects that exist primarily to displace or outright LLM-copyright-launder existing copyleft and/or LLM-unfriendly upstreams.
    • Embed this notice
      Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Sunday, 17-May-2026 00:59:56 JST Haelwenn /элвэн/ :triskell: Haelwenn /элвэн/ :triskell:
      in reply to
      • XANTRONIX
      @xan @dalias I think it's not even clean room, because for this you'd actually hunt for all third-party documentation and specifications/standards, which they didn't (like how some of uutils CVEs are blatant "didn't read POSIX") and instead grabbed the coreutils testsuite.

      It's just pure "Rewrite it in Rust" where the only goal is for it to be in Rust.
      In conversation about 6 days ago permalink
    • Embed this notice
      Rich Felker (dalias@hachyderm.io)'s status on Sunday, 17-May-2026 23:49:16 JST Rich Felker Rich Felker
      in reply to
      • Howard Chu @ Symas
      • nxadm

      @hyc @nxadm I deem NOT having a LPM or automatic-dependency-fetching a necessary condition for a viable language in this domain.

      In conversation about 5 days ago permalink
    • Embed this notice
      Howard Chu @ Symas (hyc@mastodon.social)'s status on Sunday, 17-May-2026 23:49:17 JST Howard Chu @ Symas Howard Chu @ Symas
      in reply to

      @dalias yep, same. https://mastodon.social/@hyc/114841502231953489

      Frankly the interminably slow compile times were the first red flag for me. But resorting to AI just yells out "we don't know what we're doing".

      In conversation about 5 days ago permalink

      Attachments

      1. No result found on File_thumbnail lookup.
        Howard Chu @ Symas (@hyc@mastodon.social)
        from Howard Chu @ Symas
        @teriradichel@infosec.exchange but a plane's autopilot doesn't make the plane fly 20% slower. It will always be better to have smarter human programmers who write their own code and thus understand what it's doing, than to have vibe coders who don't understand what was written but are still responsible for fixing whatever's wrong with it. https://chaos.social/@ben_tinc/114839691820680902 You can't replace or shortcut the knowledge that comes from actually doing the work.
    • Embed this notice
      nxadm (nxadm@infosec.exchange)'s status on Sunday, 17-May-2026 23:49:17 JST nxadm nxadm
      in reply to
      • Howard Chu @ Symas

      @hyc @dalias

      What about other contenders like Go (fast compile, less smug about C)?

      In conversation about 5 days ago permalink
    • Embed this notice
      Howard Chu @ Symas (hyc@mastodon.social)'s status on Sunday, 17-May-2026 23:49:17 JST Howard Chu @ Symas Howard Chu @ Symas
      in reply to
      • nxadm

      @nxadm @dalias Go has this weird design mentality of fetching every dependency you're using, straight from github. And no dynamic linking. It's too opinionated, IMO.

      Not to mention it was intentionally designed to be less flexible than C.

      In conversation about 5 days ago permalink
      Rich Felker repeated this.
    • Embed this notice
      Rich Felker (dalias@hachyderm.io)'s status on Monday, 18-May-2026 00:01:07 JST Rich Felker Rich Felker
      in reply to
      • Howard Chu @ Symas
      • nxadm

      @nxadm @hyc Yes, those are all bad for exactly the same reasons.

      In conversation about 5 days ago permalink
    • Embed this notice
      nxadm (nxadm@infosec.exchange)'s status on Monday, 18-May-2026 00:01:08 JST nxadm nxadm
      in reply to
      • Howard Chu @ Symas

      @hyc @dalias

      I don't see the difference with e.g. Java before maven where you had download libraries from weird random sites, or npm today where you know your dependencies will break in a few month. Probably good old Perl had it right with their CPAN model.

      In conversation about 5 days ago permalink
    • Embed this notice
      nxadm (nxadm@infosec.exchange)'s status on Monday, 18-May-2026 00:01:09 JST nxadm nxadm
      in reply to
      • Howard Chu @ Symas

      @hyc @dalias

      (It's not tied to github, it can be anything. It's in practice mostly github because most people publish their libraries there.)

      In conversation about 5 days ago permalink
    • Embed this notice
      Howard Chu @ Symas (hyc@mastodon.social)'s status on Monday, 18-May-2026 00:01:09 JST Howard Chu @ Symas Howard Chu @ Symas
      in reply to
      • nxadm

      @nxadm @dalias yes, but still that's an open door for malware, wherever you point it. https://mastodon.social/@hyc/113999242008616734

      In conversation about 5 days ago permalink

      Attachments

      1. No result found on File_thumbnail lookup.
        Howard Chu @ Symas (@hyc@mastodon.social)
        from Howard Chu @ Symas
        #BoltDB is a Go rewrite of #LMDB (mostly; it has a lot more limitations). It's no longer maintained. Since 2021 some forks had a backdoor giving remote command access to machines. https://snyk.io/blog/go-malicious-package-alert/ All of this is inconceivable for LMDB, since it has no other dependencies. Also, the thought of an embedded DB engine having access to any networking APIs at all is just mindboggling. The Go build system, and its automatic pulling of dependencies from github, is ludicrous. #golang
    • Embed this notice
      Howard Chu @ Symas (hyc@mastodon.social)'s status on Monday, 18-May-2026 00:13:55 JST Howard Chu @ Symas Howard Chu @ Symas
      in reply to
      • nxadm

      @nxadm @dalias if you look at it as an attempt to make human programmers into interchangeable code spewing machines, then Google's new emphasis on AI code spewing machines probably means golang was a failure.

      In conversation about 5 days ago permalink
    • Embed this notice
      Howard Chu @ Symas (hyc@mastodon.social)'s status on Monday, 18-May-2026 00:13:56 JST Howard Chu @ Symas Howard Chu @ Symas
      in reply to
      • nxadm

      @nxadm @dalias also, it's intentionally limiting in its expressiveness. Which makes sense as one of its design goals - it was designed to make projects and programmers at Google interchangeable. There's only one way to do things, so there can only be one "style". In short, it's designed for mediocrity. https://channel9.msdn.com/Events/Lang-NEXT/Lang-NEXT-2014/From-Parallel-to-Concurrent

      In conversation about 5 days ago permalink

      Attachments


      1. https://files.mastodon.social/media_attachments/files/116/590/536/135/120/773/original/675b64fd5ba8210e.jpg

      Rich Felker repeated this.
    • Embed this notice
      Orman (orman@furry.engineer)'s status on Monday, 18-May-2026 01:27:44 JST Orman Orman
      in reply to
      • Howard Chu @ Symas
      • nxadm

      @hyc @nxadm @dalias This is a different aspect of the same point but IMO go is fundamentally unserious at the language level because it focuses on a notion of "simplicity" that makes all complexity the programmer's problem, and failure to handle it their fault.

      e.g. we had no excuse for `nil` after the Java/C# era, but go not only has it, it has to twist itself in knots because having `nil` means that, e.g. your type must have a zero-value, it can't have any RAII invariant, there has to be a well-defined answer to things like "what happens if you await a nil channel receiver" (we block forever)

      I can appreciate that people are getting sick of the Rust team's political and design decisions, but the technical foundation that lets you use "values as certificates" is a vast improvement over almost every other language going.

      In conversation about 5 days ago permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.