It's not there in Chrome or Safari.
It is there in Firefox.
Edit: found the culprit in "monospace-web.css":
::-webkit-scrollbar {
height: var(--line-height);
}
Turning that off brings the scrollbar back.Fixed: https://github.com/Thomascountz/thomascountz/commit/dc7d810d...
Left having leaned that you can switch Tail Call Optimisation on or off in Ruby code.
> There was some talk of enabling tail call optimization by default around the time that Ruby 2.0 was released, however this hasn't come to be for a number of reasons: Primary concerns were that tail call optimization makes it difficult to implement set_trace_func and also causes backtrace weirdness due to the absence of a new stack frame.
http://blog.tdg5.com/tail-call-optimization-in-ruby-backgrou...
Also came for ea, and also wrote my thesis (master's) on it (check my profile), so have a soft spot for it. I like how it can be used for all kinds of problems. We actually also use these traditional optimizations processes/algorithms quite a lot at work, even more than ML that's quite hyped, as it's just more in line with the problems we actually face.
Cool article, OP, I like the esthetics of the final image.
https://medium.com/@JuliusHuijnk/experiment-in-evolving-the-...
To be honest I haven't yet read the original article, since it's huge. It seems to aim for something compareable.
Here's my one https://fingswotidun.com/blag/shaderpic1/ You can drag and drop images to set a new goal image.
I used coloured triangle pairs with a small set of combination operations and a soft edge falloff.
A write up of sorts at http://blag.fingswotidun.com/2016/05/evolved-images-using-sh...
I'll look later when the rush dies down to see how they compare.
[edit] I just realised it's been almost 10 years and I'm back to doing the same thing in a different domain. Right now I have a computer training an AutoEncoder to make the best 128 byte 32x32RGB images it can.
I had to dig up the original post by Roger Alsing[1] as it seems to have inspired a few people. I hadn't thought of evolutionary algorithms being used for image compression before; evolving from pixels to polygons creates a tool artistic expression, but also has utility for data compression (even if it's lossy). I wonder what other data formats could be compressed via evolution!
[1]: https://web.archive.org/web/20170116042711/https://rogerjoha...
I didn't notice a link to any code, would you be open to sharing the code? I'd love to take a look at how you did things and play around with it myself.
I did something similar in Julia a while ago in an attempt to learn the language: https://www.basjacobs.com/post/2020-11-18-image-triangulatio...
[1]: https://www.basjacobs.com/post/2020-11-18-image-triangulatio...
Sorry for my strong Italian accent Hahah :D
A monospaced font with narrow line spacing. 40 years of typesetting tech and 500 years of typography and insights on what makes a text readable thrown out of the window.
To get what exactly? Some fake retro charme?
I gave up reading after the first three paragraphs.
I don't think it was the nicest font, but I have no problems reading a monospace font. I rather despise some fancy looking but actually hard to decode font some blogs use instead.
"40 years of typesetting tech and 500 years of typography and insights on what makes a text readable thrown out of the window"
Also not everyone did study that and not everyone wants to hire a style guide. I bet the person writing it, just choose a font he liked. And focused on the content.
You can read or download the raw markdown format, hosted on Github[2], if you're interested in the content in a different format.
The font is from iA Writer[3], called iA Writer Duo, which arguably is not meant for a wall of prose, but I chose it because I found it easier to read than its contemporaries.
[1]: https://news.ycombinator.com/item?id=41370020
[2]: https://github.com/Thomascountz/thomascountz/blob/main/_post...
> some fake retro charme?
That’s a bit hyperbolic, and borders on just being a bit mean. There is no right way to do typography… and that is what 500 years of typography has taught us. We had monospaced typewriters in global widespread use for a hundred years. We still use monospaced fonts for programming computers… and for style in many different contexts. You do you, it’s fine if you personally prefer certain fonts, but please don’t speak for the rest of us. Almost everyone can read monospaced fonts just fine.
[1] https://snats.xyz/pages/articles/optimizing_images.html [2] https://arxiv.org/pdf/2106.14843