Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mastodon.social/users/eliasp/statuses/110764681484511845">Elias Probst (eliasp@mastodon.social)'s status on Monday, 24-Jul-2023 07:04:26 JST</a><a href="https://mastodon.social/@eliasp" title="eliasp@mastodon.social"><img src="https://gnusocial.jp/avatar/5204-48-20220814104135.webp" width="48" height="48" alt="Elias Probst" style="position: absolute; left: 0; top: 0;">Elias Probst</a><div><a href="https://mathstodon.xyz/@ColinTheMathmo/110762459405729818" rel="in-reply-to">in reply to</a><ul><li></ul></div></section><article><p><a href="https://mathstodon.xyz/@ColinTheMathmo">@ColinTheMathmo</a> I developed <a href="https://mastodon.social/tags/Perl" rel="tag">#Perl</a> quite a few years for a living.<br>This clearly showed, that the codestyle policies and their enforcement within a project/team makes all the difference for non-opionated languages like Perl.</p><p>Some of the best structured, most readable code I ever saw was in Perl - but at the same time, you can write valid Perl code which is indistinguishable from trying to <a href="https://mastodon.social/tags/OCR" rel="tag">#OCR</a> paint splatters:<br><a href="https://www.mcmillen.dev/sigbovik/" rel="nofollow noreferrer">https://www.mcmillen.dev/sigbovik/</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/1836847#notice-3602848">In conversation</a><time datetime="2023-07-24T07:04:26+09:00" title="Monday, 24-Jul-2023 07:04:26 JST">Monday, 24-Jul-2023 07:04:26 JST</time> <span>from <span><a href="https://mastodon.social/@eliasp/110764681484511845" rel="external" title="Sent from mastodon.social via ActivityPub">mastodon.social</a></span></span><a href="https://mastodon.social/@eliasp/110764681484511845">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: www.mcmillen.dev</div><h5><a href="https://www.mcmillen.dev/sigbovik/">93% of Paint Splatters are Valid Perl Programs | Colin McMillen</a></h5><div></div></header><div>TLDR: read the paper and view the gallery of pretty Perl programs. In this paper, we aim to answer a long-standing open problem in the programming languages community: is it possible to smear paint on the wall without creating valid Perl?</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Elias Probst (eliasp@mastodon.social)'s status on Monday, 24-Jul-2023 07:04:26 JSTElias Probst
in reply to
- Colin the Mathmo
@ColinTheMathmo I developed #Perl quite a few years for a living.
This clearly showed, that the codestyle policies and their enforcement within a project/team makes all the difference for non-opionated languages like Perl.
Some of the best structured, most readable code I ever saw was in Perl - but at the same time, you can write valid Perl code which is indistinguishable from trying to #OCR paint splatters:
https://www.mcmillen.dev/sigbovik/
In conversation2 years ago from mastodon.socialpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: www.mcmillen.dev
  93% of Paint Splatters are Valid Perl Programs | Colin McMillen
  TLDR: read the paper and view the gallery of pretty Perl programs. In this paper, we aim to answer a long-standing open problem in the programming languages community: is it possible to smear paint on the wall without creating valid Perl?

Public

Embed Notice

HTML Code

Corresponding Notice