#bevy has outgrown ab_glyph and must choose a better solution to deal with fonts and text in #rustlang. We've opened a new working group to handle this migration, and decide between cosmic-text and parley.
If you have strong opinions or expertise about text and fonts, I'd really appreciate hearing from you.
#askFedi#fediHelp Is the following pattern known and does it have a name?
I have a number of classes (call them C1, C2, etc) that all derive from the same class B. I have a superclass (template, actually) D that derives from C1, C2 etc. To have a single B, the standard solution is to go with virtual inheritance to close the diamond (so far, so good).
@oblomov most of the newer languages (eg. #RustLang or #GoLang) don’t support inheritance between classes/structs. They only support implementation of traits, which only define interface and not implementation. In general, using inheritance for implementation reuse is brittle and I like to avoid it.
oct can now set up cards in #KDF mode, the text output format was improved for readability, and some minor bugs were fixed.
Finally, version 0.11.0 uses #rPGP, a pure #Rust OpenPGP library 🦀.
As a result, the binary on #Linux links to four fewer dynamic libraries, while at the same time being 10% smaller.
Straw-people love to say that #rustlang is terrible for quick-and-dirty scripting tasks: just write Python or Perl!
My experience with it has been great though: CLIs are so smooth to write, there's great crates for all the dumb little things you want to do, and path + string processing is super easy. And then you can actually read / modify the script in the future. We've been working on a generate-release script for @bevy with multiple contributors over the last month; it's been lovely.
This week in the Bevy ecosystem we see Tiny Glade ship a Steam demo, live VJ sets powered by Bevy, screen space reflections in the deferred renderer and more.
We've also got the usual showcases and a couple really interesting crate release for 2d lighting systems and gpu particles.
Hi! It's time for this week's edition of the #bevymergetrain. If this is your first time here, every week a do a round up of the community-reviewed PRs for @bevy, the #opensource#rustlang engine for #gamedev that it's now my full-time job to help maintain!
There's a whopping 20 PRs ready this week; let's check in on and each of them and I'll make the final call:
I just started a plain typescript project, and was too lazy for a docker setup so I just installed Node with apt and went on my way.
I installed Typescript, that went fine, but when trying to use it it gave a vague error.
Quick search fixed it, but... I'm amazed by the cause: Typescript didn't support the version of Node I had installed, which sure.. That's okay. But why didn't NPM tell me this? NPM does not have node version constraints?!?
@jaapio While composer is useful, it's not always the bee's knees, especially during major updates involving multiple packages.
Some of the error messages are completely useless and I have spent hours trying to find the problem. I have often wished I could switch to another language because I was stuck in composer update hell.
For example, I have fewer problems with Go modules and rust dependencies via rusts cargo. Both update more smoothly.