jeran

android @netflix | formerly @lyft | formerly @snapchat | formerly @vsco | all bugs are my own

[jeran @jeranfox]

built a new Modifier this weekend

fun Modifier.chromaticAberration(
translateX: Float = 0f,
translateY: Float = 0f,
color: AberrationColor = AberrationColor.CMY,
): Modifier { ... }

[jeran @jeranfox]

spotify: your top songs were sardine, halibut, and flounder

your top genre was fish

[jeran @jeranfox]

"decades ago clothing was made to last you a long time, and now its not ... what it's meant for is to generate the company as much profit as possible with as little expense necessary"

yeah, somehow this is also the problem with software

[♡ elena ♡ @languidreamer]

when this happened to me i was getting comments that i mustve worn them too much or that my tabis were fake. the truth is, high price tags are no longer a signifier of quality. people would rather defend a company than accept that theyre being deceived

[jeran @jeranfox]

@grantheinlein @SandyofCthulhu came here to say this

[jeran @jeranfox]

@Sp4ghettiCode do you think this was true when it was called twitter? i feel like i remember a golden era several years ago, but I haven't really found any great discussion recently.

[jeran @jeranfox]

me switching to front end

[critter @BecomingCritter]

When I was younger I had a friend that went to Stanford but she transferred to a state school because she couldn’t tolerate not being the smartest person in the room

I still think about that

[jeran @jeranfox]

git branch -m main master

[Zach W. Lambert @ZachWLambert]

This photograph was taken two days ago at the FBI Academy in Quantico and submitted to the NYT under the condition of anonymity.

If a picture is usually worth a thousand words, this one is worth millions.

[jeran @jeranfox]

@billedabear balatro has ruined me

[jeran @jeranfox]

kotlin developers pretending they’re not writing singletons

[ƪ(˘⌣˘)ʃ @need_da_cash]

you can put objects anywhere

[jeran @jeranfox]

@benxedel don’t get me started on long press to fast forward

[jeran @jeranfox]

@Proto_arts i thought that was pomni

[jeran @jeranfox]

@MartinaIsho could’ve stopped after the third word

[jeran @jeranfox]

@trashh_dev is there one? show me

[jeran @jeranfox]

@Andercot what kind of names are Mon and Sub?

[jeran @jeranfox]

@ThePopTingz is this a mr beast video

[jeran @jeranfox]

and some of you have the gall to put two spaces after periods

[† lucia scarlet 🩸 @luciascarlet]

oh, it appears as if you have summoned me

there are several reasons as to why:

1. macOS does not use hinting
hinting is a technique to improve the sharpness of text on low-resolution screens and allow outline fonts to be rendered as bitmaps at a variety of sizes. it works by having fonts contain full-blown programs that instruct the renderer on what to do with outlines when rendering and where to place them on the pixel grid. this results in the shape of a glyph being altered so that it fits into the pixel grid, rather than the original shape of the glyph being maintained. while this can look acceptable (good, even) if a font is meticulously and manually hinted—an arduous process that can take literal years to do by hand and requires knowledge of some extremely arcane software—this is no longer nearly as much of a requirement with monochrome/bitmap rendering no longer being something you'd need to care about and screens being higher resolution on average. therefore, the norm for most new fonts is for them to just go through an auto-hinting process, perhaps with slight manual fixes where needed. this is typically Good Enough™, but… well, really, it's not. there are a handful of issues with this: glyphs will not render consistently at different sizes, stems may be aligned towards the incorrect pixel or aligned when they shouldn't be at all, and it generally will destroy the intended overall character of the font by significantly altering the shapes beyond recognition (something you could argue also holds true for manually hinted fonts, but often, the type designer will take this into account as part of the design itself in those cases).
if you've ever noticed things like a font looking weirdly tall or short at specific sizes only, a font just looking nothing like it's advertised or like how it does at large sizes at all, glyphs like "E" having off-centre bars, "9" having a weirdly tiny or large bowl, or "g" having a small bowl that isn't aligned with the baseline, (crappy) hinting is to blame for all of those. what you're seeing is the renderer bending the glyph into the pixel grid in a way that is either Not Necessary or Not Correct. macOS, by simply ignoring these instructions, avoids all of these issues, which allows glyphs to look correct at the cost of looking softer and fuzzier.

2. Windows (usually) does not perform vertical anti-aliasing
Windows has, generally speaking, two font renderers: DirectWrite (the New Good One) and GDI+ (the Old Terrible One). and generally, you are meant to perform anti-aliasing in both the vertical and horizontal direction for it to be Useful. ClearType in its original GDI+ implementation simply does not bother to anti-alias glyphs vertically at all—only horizontally—which results in glyphs like "s" and "a" ending up with a distinctly jagged appearance. they are literally only half-anti-aliased. DirectWrite is actually able to do vertical anti-aliasing, allowing these glyphs to look much smoother and more pleasant, but for some arsefucked reason that completely eclipses my understanding, it does not do so by default, and necessitates the use of a special flag. MacType can force this flag, and Firefox also has the ability to enable this flag in about:config, although of course, it is not enabled by default, resulting in markedly inferior rendering.

3. macOS does not use subpixel anti-aliasing
subpixel rendering is an ancient technique dating back to when users began transitioning from CRTs to LCDs that aims to improve the horizontal resolution of text by taking advantage of the uniform horizontal RGB subpixel grid on LCDs. while it technically, to some extent, works, it brings about a LOT of complications: it cannot be trivially alpha-blended against dynamic backgrounds, it relies on a specific subpixel grid layout and native resolution, and it creates visible coloured fringing artefacts that may cause eyestrain for some (including myself), manifesting as text that doesn't look purely black, but rather black with a bunch of green and yellow crap around it. subpixel rendering is thus unsuitable for things like OLED screens (which all tend to have hilarious and made-up subpixel layouts for some reason) and setups that mix horizontal and rotated vertical monitors, which are actually quite common among enthusiasts. while there is arguably *some* merit to this technique, the benefits are simply are vastly outweighed by its drawbacks. Windows in most cases employs a very aggressive form of this (which I perceive to be rather abrasive and unpleasant to look at), while macOS sticks to basic greyscale anti-aliasing, which is far more reliable and does not result in unpleasantly fringed text.

4. macOS always uses fractional glyph positioning
traditionally, font rendering had been done by rendering an atlas of glyphs once, and simply referring to it for each new glyph, with the position of the glyph being rounded to the nearest pixel. unfortunately, this is not sufficient in order to faithfully reproduce the spacing of glyphs as was intended by the type designer and as is encoded in the font, as kerning and spacing happens at a much, MUCH finer scale than even a high-DPI pixel, let alone a low-DPI pixel. rounding glyph positions to the nearest pixel therefore tends to result in inconsistent and off-pissing kerning that Doesn't Look Right. fractional glyph positioning addresses this by actually rendering glyphs individually in between pixels, so that the intended spacing and kerning that the type designer spent days carefully tuning can be reproduced accurately on-screen, even at small sizes. it is very easy to determine whether fractional glyph positioning is in use by typing one character in quick succession and seeing if all of them look the same or not:
iiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii
if all of these look the same, then fractional glyph positioning is not used; if they look different, then it is. Windows's God-awful GDI+ renderer indeed does not use it, but macOS, as well as Windows's good DirectWrite renderer do use it. (thankfully, your browser most likely does use DirectWrite to render text, unless it is so old that it creaks upon being clicked on)

5. macOS performs intense stem darkening
to compensate for gamma correction during the AA stage resulting in perceived thinner and lighter text due to simply not covering enough pixels, particularly on low-DPI screens, macOS's text renderer performs a rather noticeable amount of stem darkening, something that it confusingly refers to internally as "font smoothing". this simply expands the stems by a small amount in relation to pixel size, increasing their coverage of the pixel grid, which enhances the contrast and results in glyphs appearing darker. this allows text to remain easily readable even at small point sizes on low-resolution screens. if so desired, stem darkening can actually be disabled using a terminal command in macOS.

in short: macOS treats fonts with respect and dignity, and Windows mercilessly beats and tortures them to death and throws their mangled, desecrated corpses by the roadside all while laughing about it

[jeran @jeranfox]

am i reading this right?

[Andreas Stütz @sturtz_]

Animated Mesh Gradient for #Compose #Multiplatform
Inspired by the #SwiftUI MeshGradient

[jeran @jeranfox]

@ferret5557

[jeran @jeranfox]

@100o111 imagine getting stopped for this at security

[jeran @jeranfox]

@MitchBech all bangers