G Ross Photography. has added a photo to the pool:

NSW

A week ago, I had launched this site using QuatroSlab for page titles and Google’s Slabo for body copy. For those that have been around awhile and are familiar with SMACSS, you might recognize QuatroSlab from that site. I like the font and started off with it to see how I’d feel about it on the this new design. Then I chose Slabo as a font that I felt paired well with it.

For the most part, I was fine with it but after finally getting a blog post written and posted under the new design, I was feeling less than thrilled with my choices.

Over yesterday and today, I decided to do some research on fonts and came across Pangram Pangram Foundry. They have some delectable fonts that make me want to do some interesting designs with them. This led me to Fragment. I looked through all the variants and Fragment Text felt just right for the body copy. It felt softer and rounder and more open and friendly than Slabo.

My only complaint is that I want some of the discretionary ligatures in the list of standard ligatures like the Th and ft. The rest of them are too much flourish for body copy. I enabled the ligatures for headings, at least, where some flourish is warranted.

For page headings, though, I wanted something bolder. This is where Pangram Pangram’s Pangaia comes in. I like the slightly retro-modern funky feel that this font brings to the table.

The CSS

From a technical perspective, this is the first time I’ve taken advantage of OpenType feature capabilities and I found it confusing as I couldn’t find a good explanation of what liga or dlig or ss03 mean or how to know whether a font even supports these.

I’ve learned that you can turn these on or off via CSS’s font-feature-settings property.

font-feature-settings: "ss02", "ss03", "ss04", "dlig", "zero", "onum";

Declaring the value turns them on. You can alternatively, specifically declare them on or off using the words on or off or the numbers 1 or 0. The following would enable features ss02, ss03, zero, and onum; it would disable ss04 and dlig.

font-feature-settings: "ss02" on, "ss03" 1, "ss04" off, "dlig" 0, "zero", "onum";

The question then became about how to figure out which of these features exist in a particular font. For this, I used FontDrop!. It will show you what features are available and what those features look like for that font. FontDrop! is all client-side, too, which is nice. I didn’t want to be uploading files that aren’t mine to someone’s server.

Up Next

I suspect I will end up tweaking which of these features are on or off as I add more content to the site and decide what works well for a given scenario.

An anonymous reader quotes a report from Ars Technica: Big changes are coming to Android apps, but they're not the changes Google wanted. The settlement between Google and Epic that aimed to put to rest the companies' long-running antitrust battle is being withdrawn, and that means third-party app stores are coming to the Play Store. Google has confirmed that it will begin distributing rival app stores next week, setting the stage for competing platforms to take a bite out of Google's Android revenue stream. [...] Google and Epic were set to return to court on July 16 to argue in favor of the settlement. However, the writing may have been on the wall. In a recent expert analysis provided to the court, MIT economics professor Nancy Rose noted that the settlement was "unlikely to enable Google Play's potential competitors to overcome their long-standing network-effect disadvantage in a timely manner."

With settlement approval looking increasingly unlikely, Epic and Google agreed this week to call the whole thing off. Here's how Google Trust and Reputation Communications Lead Dan Jackson explains the company's decision: "We've agreed with Epic to withdraw our motion to modify the US Court's injunction rather than prolonging this process which creates uncertainty for the ecosystem. This allows us to focus on executing our recently announced global business model evolution to deliver greater app store choice, lower prices, and more opportunities for developers and users. We remain committed to maintaining Android's industry-leading security and fostering a competitive ecosystem where every app store and developer has the freedom to compete. In parallel, we continue to comply with the US Court's injunction."

In a brief filing (PDF), Google's legal team informs the court that Google is prepared to begin distributing third-party app stores in Google Play on July 22. Under the terms of Judge Donato's original injunction, these stores will have access to the full catalog of Google Play apps by default. Developers will have the option to opt out of distribution in these stores, and Google has a support page explaining how to do so. Google also has documentation on how app stores can get access to the Google Play catalog. It won't be mirroring those apps in any shady storefront that asks. The court has allowed Google to charge reasonable fees to cover its security and compliance review of third-party stores, which will be $5,000 per year.

Google will also require approved stores to block malware, respect intellectual property, and include mechanisms to update and uninstall apps. App stores can be removed from the program if more than 1 percent of attempted app installs appear to be malware or unwanted software. It's unclear if there will be separate, possibly more stringent requirements for storefront distribution in the Play Store. However, Google is prohibited from unreasonably blocking third-party store clients uploaded to Google Play. The changes Google has announced under the Epic agreement will proceed for now. That means Registered App Stores will happen globally, but they will probably only appear in the Play Store for US users. Google hasn't specified if there will be any differences in the features available to the stores downloaded from Play versus registered stores.

Read more of this story at Slashdot.

FreeBSD 16 has removed the last GPL-licensed code from its base system, retiring the old GNU 'dialog' implementation after the installer moved to 'bsddialog' and the final dependency was disabled. Phoronix reports: This ticket to retire dialog was opened back in February while is now merged to the FreeBSD source tree for what will become FreeBSD 16.0. With dialog removed, the latest FreeBSD code now retires the GNU sub-tree of the FreeBSD base system now that no more GNU code remains. FreeBSD 16.0 is working its way toward release that is expected to happen in December 2027.

Read more of this story at Slashdot.

BertvB posted a photo:

A dramatic sunset over the North Sea coast, captured from a high vantage point overlooking a row of beach cabins.

Thomas Hawk posted a photo:

Thomas Hawk posted a photo:

Verse beelden, veel Lamers. ja het heet ook niet voor niets archief. En oude wijn in nieuwe zakken: Jongeleen doet een geenstijltje. Waanzinnig zakkende Simon Schrikker. Sorry! zegt Lamers. Ralph van Meijgaard – IM Lamers [Meer...]

Het Argentijnse elftal heeft woensdagavond de halve finale van het WK voetbal gewonnen van Engeland. Dat betekent dat de Argentijnen zondag de WK-finale spelen tegen Spanje, dat…

Dave Brown, a 19-year veteran of AWS and member of its S-team leadership cabal, is leaving Amazon for parts undisclosed. It's hard to overstate Dave's impact on AWS; the few times I've met him, it was very clear that there was nothing I could trot out in the realm of "arcane EC2 trivia" that he didn't go orders of magnitude deeper on with zero forewarning. This is a titanic loss for AWS, because that's roughly how deep Dave routinely dove. He'll be handing the reins over to fellow S-team member Dave Treadwell, currently the head of Amazon Retail's "eCommerce Foundation" (itself an upscale term for "bargain basement"). Brown probably isn't going to be a direct competitor (though he's definitionally going to some Amazon competitor short of his next move being "philanthropy"), unless the two-week notice period is simply a bunch of Amazonian goons beating the tar out of him in a dark room around the clock until August. But the interesting part to me is that suddenly Dave Treadwell has an enviable job. Think about it for a second: Amazon retail was, for a time, the largest AWS customer — and certainly one of the most complicated. If I think I have beef about AWS-isms, there's no doubt that "Tread," as he's apparently called, has mountains to my molehill of complaints. So if I can slip into his role for a second, here would be my to-do list if I were coming from an Amazon Retail background and suddenly had EC2 bequeathed to me to run: GPU capacity acquisition: Special people get special allocation rules, balanced between Capacity Blocks, war-clicking past InsufficientInstanceCapacity screens, and having to know a guy. Amazon has an entire internal project to solve this for its own teams. If I'm Tread, take a page from retail and smash Spot Fleet dynamics into a proper capacity marketplace. "Only 2 p6-b300.48xlarge left in stock. Ships from and sold by GPUZ4LOLZ (91% positive feedback)." Savings plans / Reserved Instances archaeology: These sometimes-but-often-not overlapping discount vehicles were clearly designed by folks who never had to explain them to a CFO with anger management issues. Treadwell has a golden opportunity here to roll out dynamic raw pricing: on-demand rates that themselves fluctuate hourly like a third-party listing on discontinued and incompatible printer ink, replacing traditional commitment vehicles with a "Subscribe & Save 5%" toggle on vCPUs. Instance type proliferation: As of this writing, there are 1,354 EC2 instance types available in us-east-1 alone, and the console picker assumes that you already know the correct answer. Riiiight. There's a solution here! "Customers who launched m7i.large also launched ..." combined with sponsored placement by EC2 sub-departments means the top result is now suddenly the instance family that AWS overbought. Is this the best instance for the customer? Who gives a rat's ass; it's what's best for Amazon, a north star that Amazon Retail has been chasing for years. SageMaker is someone's empire-building project: There are over 35 SageMaker products, or features, or whatever the distinction is supposed to be at AWS. Tread should leave this alone, and introduce the amazing source of truth that is Customer Reviews. "1 star. Not as described. Arrived as Jupyter notebook; what the hell do I do with it?" They can repurpose their fake review detection to take down fraudulent reviews from other SageMaker sub-teams. Quota request supplication: You know the drill; beg, plead, and wait for the privilege to give AWS more money. The fix here is almost too easy; y'know who doesn't have to wait for quota increases? That's right: Amazon Prime members. That's the easy punch list if it were me. But I'm me, and Tread is not. I'm sure he's got planned more treats with far greater nuance and customer hostility; we'll know for sure that he's settled in when the EC2 section of our AWS bills starts including ads - and when Josh Pigford's excellent Knockoff extension starts working in the EC2 console. ®