Web packaging technology is torture.
The last week, I've been fighting webpack, parcel, #rollup, babel and bili, just because vue stopped supporting #browserify and I had to figure what to use as a replacement in #beast.
^^^ If that sentence sounds like it has too many web tech buzzwords, that's *exactly* the problem.
And it's only a fraction of packages I had to deal with...
Most packages have documentation, but only provide tiny puzzles of a much bigger picture that is revealed nowhere...
@luebbermann solche Bits?
Also, try asking around in communities (like subreddits) you already like for people that also have mastodon accounts. The lobste.rs recently did that, found some nice connections there:
@beli3ver Setz einen Server mit Nextcloud auf (geht auch per Docker). Die Nextcloud app kann deine Fotos u.a. automatisch auf deinen Server sichern.
@liw Commit counting can also give the wrong impression to peers or employers.
I was once asked about my low count during a period where I did mostly review and commit approval in bugzilla
It's easy to create lots of whitespace "correction" commits, but the real work is done elsewhere.
Case in point, here is a *one-liner* that took me and an AppImage developer hours to investigate and create a reproducible recipe for: https://sourceware.org/bugzilla/show_bug.cgi?id=25263
In terms of commit counts, that'd be a net loss.
@liw Uhm, not again "who's made the most commits"...
That often makes people (especially younger ones that might still feel like they have to prove something) try to game the measurement techniques, possibly just subconsciously.
E.g. it can give an incentive to commit individual files independently (with minimalistic reasoning), instead of as a coherent logical group with adequate description.
Or even split commits by function in a file, just to inflate the counts.
@liw Can you describe your understanding about how leaderboards could be applied to collaborative projects?
Do you want a comparative ranking display between collaborators? Between bugs / feature requests? Or between related projects?
Or something else entirely?
@ajuvo good n8
That's still unfinished though, why do I always need bleeding edge features?
Time for bed I guess, maybe the edge looks less bleeding tomorrow... ;-)
@federicomena for two selectors that have the same specificity, the latter one should be selected. So that either needs to be included in your specificity calculations, or the selectors should be picked by reverse order of definition, instead of a randomized iterator (which is a nice feat by rust btw)
Last Tuesday #Beast 0.15.0 was released.
This is most probably the last release that supports the #Gtk+ Beast UI. We have most of the bits and pieces together to move towards the new EBeast UI and a new synthesis core in the upcoming months and will get rid of a lot of legacy code along the way...
@nobru Thanks for the link! That was a long but very eye opening reading.
I kept checking back all the things Clay talks about really already existed in 2003, incredible insights given this was 16 years ago.
@openmastering thx, great!
Beast version 0.15.0 is released.
#Beast is an LGPLv2+ music synthesizer and composer (#DAW), for #Linux.
This release supports Jack as PCM driver and the experimental Ebeast frontened got many style updates, play position pointers and supports the Space key.
Here's a suggestion I've picked up from the Podcaster scene. Create a public Amazon wishlist, that you link to from your Website or Mastodon profile. At $10, it's possible that some community member browses the list, steps up and buys it for you and then it gets removed and shipped to you...
DSP + UI developer on the Beast DAW, Free Software author + advocate, contributor to ALSA/GNOME/procps/LibreOffice/etc.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!