• 222 Posts
  • 1.44K Comments
Joined 3 years ago
cake
Cake day: June 11th, 2023

help-circle
  • Given the nature of Steam and previous executed data extraction, I’m scared installing and running niche/indie games now. Windows lacks

    A unified GUI framework hasn’t happened yet, not between OSes, nor really within each OS ecosystem. I’m not hopeful about leaps in native interoperability in that regard.

    Web tech interoperability is so established and widely used, packaging and running those natively seems much more viable than any hope for supposed native long term efforts.

    Not everything will be covered by web tech. But for many things, it’s already viable, and exploring native integration of these web technologies is interesting.





  • Git push to Forgejo -> automated build, package, and deploy pipeline -> use secured credentials to upload via scp or ssh or sftp

    Alternatives to copy-upload or upload-package and then extract via command is stuff like rsync (reduce redundant, unchanged file uploads) or a simple receiver service (for example REST endpoint that receives a package with an identifier key and secret key, that it extracts to a configured target folder).

    What solutions are simplest or easiest depend on the target environment, and how much of it you control. If you host the website on Forgejo itself it’s as simple as pushing the static files into the corresponding pages branch.


  • It falls back exactly the way I think.

    This article talks about flashes, and proceeds to say fallbacks should be defined. It explains how fallbacks work, but fails to describe what actually leads to the flashes, how fallbacks get replaced, and fails to say anything about solving that flashing issue they talk about.

    Defining a more similar fallback font may reduce the issue visually, which is not mentioned either, and either way is not a solution for the flashing.

    Dunno why one would expect lower precedence CSS rules be integrated into more specific CSS rules without explicit “inherit”. That’s not how CSS works. Dunno if that’s a common enough misunderstanding to warrant a “not the way you think it is” title.













  • How does Pretext work?

    1. Segment the text; Normalize whitespace, apply Unicode line-break rules, and split the string into measurable units using the browser’s own text segmentation.
    2. Measure with Canvas; Feed each segment through Canvas measureText() to get real glyph advance widths from the font engine. Results are cached.
    3. Pretext.js uses pure arithmetic; Given a container width, compute line breaks by summing segment widths. Multiply line count by line-height. Return height. No DOM, ever.

    Unfortunately, that doesn’t really explain the final integration. And it seems I misunderstood/-assumed at first.

    Looking at the example at the top right, it renders numerous div elements?

    So, presumably, you lose text wrap behavior and clean markup like <p> for a paragraph? I also can’t select text from it in a normal or consistent way.

    This example isn’t very convincing either.

    Seems like a cool visual gimmick more than practically useful and accessible for primary content.


  • I work for a small ~30-person company with various customers, including some very big names. We’re very deliberate about where tools like those could help us, where it’s worth the exploration and investment. We want to be innovative and have the expertise, but at the same time, be reasonable and sound. We’re also very conscious of data sharing and safeguards, in part out of necessity, because we can’t just share our customers’ code or data with third parties.

    Excitement, commitment, use, and hopes of using AI tools differ between colleagues. What we can use and how differs between projects.

    So yes, there are definitely other kinds of companies and environments out there.