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
    SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 07-Sep-2022 23:09:26 JST SuperDicq SuperDicq

    .

    In conversation Wednesday, 07-Sep-2022 23:09:26 JST from minidisc.tokyo permalink

    Attachments


    1. https://minidisc.tokyo/files/webpublic-a503f71c-feb1-43b0-a33b-bf3b10db114f
    • Embed this notice
      SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 07-Sep-2022 23:13:24 JST SuperDicq SuperDicq
      in reply to

      This is actually there on the page and nobody has addressed this change since May. https://en.wikipedia.org/w/index.php?title=Wirth%27s_law&diff=1088813092&oldid=1081924036

      Please don't be a spoilsport.

      In conversation Wednesday, 07-Sep-2022 23:13:24 JST permalink

      Attachments

      1. Domain not in remote thumbnail source whitelist: login.wikimedia.org
        Wirth's law
        Wirth's law is an adage on computer performance which states that software is getting slower more rapidly than hardware is becoming faster. The adage is named after Niklaus Wirth, a Swiss computer- & information-scientist, who discussed it in his 1995 article "A Plea for Lean Software". History Wirth attributed the saying to Martin Reiser, who in the preface to his book on the Oberon System wrote: "The hope is that the progress in hardware will cure all software ills. However, a critical observer may observe that software manages to outgrow hardware in size and sluggishness." Other observers had noted this for some time before; indeed, the trend was becoming obvious as early as 1987.He states two contributing factors to the acceptance of ever-growing software as: "rapidly growing hardware performance" and "customers' ignorance of features that are essential versus nice-to-have". Enhanced user convenience and functionality supposedly justify the increased size of software, but Wirth argues that people are increasingly misinterpreting complexity as sophistication, that "these details are cute but not essential, and...
    • Embed this notice
      SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 07-Sep-2022 23:15:13 JST SuperDicq SuperDicq
      in reply to
      • \\

      @slash@cdrom.tokyo
      software is starting to compose slower multi celled organisms with more stability in aggregate.That really depends on who you ask. A lot of people seem to agree that increased complexity equals decreased stability.

      In conversation Wednesday, 07-Sep-2022 23:15:13 JST permalink
    • Embed this notice
      \\ (slash@cdrom.tokyo)'s status on Wednesday, 07-Sep-2022 23:15:14 JST \\ \\
      in reply to

      @SuperDicq if you were to look at this adage through a comparative perspective to biology i wonder if the conclusion would ultimately be more like, software is starting to compose slower multi celled organisms with more stability in aggregate. Catastrophic failure is still very much possible, even moreso sometimes than with these single purpose ripspeed programs, but in general there are more adaptable platforms resulting from this kind of coordination in computer science.

      In conversation Wednesday, 07-Sep-2022 23:15:14 JST permalink
    • Embed this notice
      SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 07-Sep-2022 23:24:29 JST SuperDicq SuperDicq
      in reply to
      • \\

      @slash@cdrom.tokyo It is indeed true that when software developers push hardware to its limit they often take out a lot of the safety stuff.

      I mean just look at how back in the day we had C, and it was so easy do unsafe memory stuff, cause stack overflows and other common issues associated with software written in C. But hey, it runs Doom at 60fps.

      Nowadays we got things like garbage collection or languages like Rust that are built completely on the principle of memory safety.

      In conversation Wednesday, 07-Sep-2022 23:24:29 JST permalink
    • Embed this notice
      \\ (slash@cdrom.tokyo)'s status on Wednesday, 07-Sep-2022 23:24:30 JST \\ \\
      in reply to

      @SuperDicq That’s fair, it’s what I meant by catastrophic failure is still very possible. As you increase complexity there are a lot more things that can go wrong and second order effects on other components in a chain for doing something. The tradeoff, though, is that in practice I have had to physically hit the reset button a lot less often because these elaborate setups fail bombastically, but they don’t totally lockup the computer environment beyond recovery as often.

      In conversation Wednesday, 07-Sep-2022 23:24:30 JST permalink
    • Embed this notice
      SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 07-Sep-2022 23:28:08 JST SuperDicq SuperDicq
      in reply to
      • \\
      • Haelwenn /элвэн/ :triskell:

      @lanodan@queer.hacktivis.me @slash@cdrom.tokyo Yeah, but C is older.

      In conversation Wednesday, 07-Sep-2022 23:28:08 JST permalink
    • Embed this notice
      Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Wednesday, 07-Sep-2022 23:28:11 JST Haelwenn /элвэн/ :triskell: Haelwenn /элвэн/ :triskell:
      in reply to
      • \\
      @SuperDicq @slash Nowadays?
      Java is nearly 30 years old…
      In conversation Wednesday, 07-Sep-2022 23:28:11 JST permalink
    • Embed this notice
      SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 07-Sep-2022 23:29:06 JST SuperDicq SuperDicq
      in reply to
      • \\
      • Haelwenn /элвэн/ :triskell:

      @lanodan@queer.hacktivis.me @slash@cdrom.tokyo And I don't know if you ever used Java software back in the day, but everything that used Java was considered bloatware at the time.

      In conversation Wednesday, 07-Sep-2022 23:29:06 JST permalink
    • Embed this notice
      SuperDicq (superdicq@minidisc.tokyo)'s status on Thursday, 08-Sep-2022 00:26:21 JST SuperDicq SuperDicq
      in reply to
      • \\
      • Haelwenn /элвэн/ :triskell:

      @lanodan@queer.hacktivis.me @slash@cdrom.tokyo My point is not to compare Rust to Electron. But if you want to do some stuff in Rust with the same performance as C you'll have to wrap it in unsafe {}.

      In conversation Thursday, 08-Sep-2022 00:26:21 JST permalink
    • Embed this notice
      Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 08-Sep-2022 00:26:24 JST Haelwenn /элвэн/ :triskell: Haelwenn /элвэн/ :triskell:
      in reply to
      • \\
      @SuperDicq @slash Well so is current Rust stuff to be honest.
      It's not electron size (which has roughly as much security as C in a badly configured container) but from a dev perspective it's roughly the same, both have a crazy amount of dependencies beyond any auditing.
      In conversation Thursday, 08-Sep-2022 00:26:24 JST permalink
    • Embed this notice
      SuperDicq (superdicq@minidisc.tokyo)'s status on Thursday, 08-Sep-2022 05:31:34 JST SuperDicq SuperDicq
      in reply to
      • \\
      • Haelwenn /элвэн/ :triskell:
      • Mek101

      @lanodan@queer.hacktivis.me @Mek101@mstdn.io @slash@cdrom.tokyo Depends. On embedded devices it doesn't.

      In conversation Thursday, 08-Sep-2022 05:31:34 JST permalink
    • Embed this notice
      Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 08-Sep-2022 05:31:38 JST Haelwenn /элвэн/ :triskell: Haelwenn /элвэн/ :triskell:
      in reply to
      • \\
      • Mek101
      @Mek101 @slash @SuperDicq Java comes with a GUI library.
      In conversation Thursday, 08-Sep-2022 05:31:38 JST permalink
    • Embed this notice
      Mek101 (mek101@mstdn.io)'s status on Thursday, 08-Sep-2022 05:31:39 JST Mek101 Mek101
      in reply to
      • \\
      • Haelwenn /элвэн/ :triskell:

      @lanodan @slash @SuperDicq Comparing a statically compiled programming language to an entire software framework with a Javascript JIT and HTML engine is ridicolous

      In conversation Thursday, 08-Sep-2022 05:31:39 JST permalink
    • Embed this notice
      SuperDicq (superdicq@minidisc.tokyo)'s status on Thursday, 08-Sep-2022 05:39:00 JST SuperDicq SuperDicq
      in reply to
      • \\
      • Haelwenn /элвэн/ :triskell:
      • Mek101

      @lanodan@queer.hacktivis.me @slash@cdrom.tokyo @Mek101@mstdn.io Kotlin is the more popular language for mobile development nowadays anyway.

      In conversation Thursday, 08-Sep-2022 05:39:00 JST permalink
    • Embed this notice
      Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 08-Sep-2022 05:39:02 JST Haelwenn /элвэн/ :triskell: Haelwenn /элвэн/ :triskell:
      in reply to
      • \\
      • Mek101
      @SuperDicq @slash @Mek101 I think it does with JavaME and I'm not sure if there is other kind of actual Java runtimes for embedded devices that come with a graphical output (a GUI for a smartcard is useless).

      I consider Android stuff to not be Java proper but a fork of it.
      In conversation Thursday, 08-Sep-2022 05:39:02 JST permalink
    • Embed this notice
      SuperDicq (superdicq@minidisc.tokyo)'s status on Thursday, 08-Sep-2022 05:39:42 JST SuperDicq SuperDicq
      in reply to
      • \\
      • Haelwenn /элвэн/ :triskell:
      • Mek101

      @Mek101@mstdn.io @lanodan@queer.hacktivis.me @slash@cdrom.tokyo I don't think Rust comes with a GUI.

      In conversation Thursday, 08-Sep-2022 05:39:42 JST permalink
    • Embed this notice
      Mek101 (mek101@mstdn.io)'s status on Thursday, 08-Sep-2022 05:39:43 JST Mek101 Mek101
      in reply to
      • \\
      • Haelwenn /элвэн/ :triskell:

      @lanodan @slash @SuperDicq > Well so is current Rust stuff

      In conversation Thursday, 08-Sep-2022 05:39:43 JST 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.