996 karma · joined July 7, 2014
https://git.io/stephen
https://mastodon.social/@oid
https://twitter.com/niedzielski
--experimental-transform-types: https://nodejs.org/en/blog/release/v22.7.0#experimental-tran...
I do hate JIRA. JIRA adds all the beauty of a government bureaucracy to what should be post-it note management. It's hard to overstate how demotivating JIRA is to my work and especially to my planning. Worse, everyone in the organization has to use it.
[source-map-explorer]: https://github.com/danvk/source-map-explorer
[Lighthouse Treemap]: https://umaar.com/dev-tips/270-devtools-lighthouse-treemap/
In my experience, however, as soon as my tasks section got large enough that a separate file was needed, it became long-running enough that I wanted a generic file dependency-aware builds which required a make-like solution. What should large projects do that need to build assets or perform long-running work as part of a build process without dipping into another clunky tool?
I have similar issues with threading development-only import maps that reference local modules in a polyrepo during development and sharing common Deno configs. Customization doesn't scale well to task one-liners even though I want it to. Do folks know of open-source polyrepo reference that serve as a paradigm for patterns that scale?
In case you're interested, I wrote some examples on how the system clipboard is also a great integrator for migrating data to and from the CLI: https://github.com/niedzielski/cb#examples
tic-tac-toe: tic.o tac.o toe.o
cc -o '$@' $^
%.o: %.c; cc -c $^ [difftool "meld"]
cmd = meld "$LOCAL" "$REMOTE"
[mergetool "meld"]
cmd = meld --auto-merge --output "$MERGED" "$LOCAL" "$BASE" "$REMOTE"I would enjoy the flexibility to ship types but personally don't have any need for it. Seems like "boiling the frog" for type-checking in the browsers to me but I personally like the idea of encouraging more typing in native JavaScript.
$truncate($if2(%albumartist%,%artist%),143)/$truncate($if($if2(%originaldate%,%date%),$left($if2(%originaldate%,%date%),4) )%album%,143)$if(%discsubtitle%,/$truncate(%discsubtitle%,143))/$truncate($if($gt(%totaldiscs%,1),$if($gt(%totaldiscs%,9),$num(%discnumber%,2),$num(%discnumber%,1))-,)$if($ne(%tracknumber%,),$if($gt(%totaltracks%,99),$num(%tracknumber%,3),$if($gt(%totaltracks%,9),$num(%tracknumber%,2),$num(%tracknumber%,1))),) %title%,138)
I think the truncations are necessary to avoid exceeding filename length limits on some systems. The if2s are to fallback to another field. Similar to yours, there is also logic for zero-padding as needed on discs and track numbers and to omit discs when there is only one.https://picard-docs.musicbrainz.org/v2.7/en/extending/script...