#tradeoffs — Public Fediverse posts

https://www.evshift.com/375446/the-trade-offs-of-a-500-ebike-gotrax-efold/ The Trade-offs of a $500 Ebike | GOTRAX eFold #$500Ebike #BudgetEbike #CheapEbike #ebike #EbikeEscape #EbikeReview #eFold #ElectricBike #ElectricBikes #ElectricMotorcycles #ElectricVehicles #EV #FoldingEbike #gotrax #GOTRAXEFold #motorcycles #SingleSpeedEbike #Tradeoffs #UL2271 #UL2849 #WalmartEbike

Ah yes, the groundbreaking revelation that programming languages have *tradeoffs* 🙄. Let's spend the next 1,000 words rehashing this ancient wisdom, with a sprinkle of personal anecdotes for flavor. Spoiler alert: no one emerges victorious in this epic battle of #Go vs. #Rust vs. #Zig 🏆🤡.
https://sinclairtarget.com/blog/2025/08/thoughts-on-go-vs.-rust-vs.-zig/ #programminglanguages #tradeoffs #techhumor #epicbattle #HackerNews #ngated

"Breaking News: 🎉 Developers discover that coding is hard! 🚨 In a groundbreaking revelation, we learn that every decision is a tradeoff – who would've guessed? 🙄 Next up, find out why adding more code might be necessary... because apparently we needed an article to tell us that. 🤦‍♂️"
https://programmersstone.blog/posts/why-is-this-hard/ #codinghard #tradeoffs #developernews #programminghumor #techrevelations #HackerNews #ngated

@ctietze A lot of my target use case hinges around this: how can I change the attributes of a character (name, gender, species, etc.) in a document without doing a potentially-catastrophic search-and-replace across the entire document? Preserving the character’s function and role within the work despite changing almost anything else about them.

In the #troff world you can do this pretty easily with the .ds macro to build a library of direct string substitutions.

\*[fuHERO] overcomes \*[paHERO] foe!

Perhaps there is a more native way to do it in #LaTeX than I have found; I haven’t researched it thoroughly. You can definitely set up data structures in #Emacs #lisp and pick out the attributes with #orgmode macros.

{{{fu(hero)}}} overcomes {{{pa(hero)}}} foe!

Here using `fu` for “full name” and `pa` for “gendered possessive adjective” (his/her/their/its).

In favor of #troff is the lower-level stuff. You can use macros to define strings en masse and then override individual choices for particularly weird characters. The downside is that you end up building up a library of macros to supplement your chosen package so that the main body of your document looks more like semantic than physical markup. And you probably need a #Makefile to assemble anything beyond a trivial document.

In favor of #LaTeX is mostly the higher-level stuff, and the short distance to semantic markup. #orgmode shortens this even further, and you can build your document in a single command (C-c C-e l p). But now the low-level stuff becomes annoying.

Perhaps with more research I can find the appropriate packages, but that may obviate the benefits of #orgmode altogether. Hopefully a well-fitting puzzle piece is out there, somewhere…

It’s all #tradeoffs but it’s not for paid work so I only have to worry about whether or not it works for me.

@ctietze A lot of my target use case hinges around this: how can I change the attributes of a character (name, gender, species, etc.) in a document without doing a potentially-catastrophic search-and-replace across the entire document? Preserving the character’s function and role within the work despite changing almost anything else about them.

In the #troff world you can do this pretty easily with the .ds macro to build a library of direct string substitutions.

\*[fuHERO] overcomes \*[paHERO] foe!

Perhaps there is a more native way to do it in #LaTeX than I have found; I haven’t researched it thoroughly. You can definitely set up data structures in #Emacs #lisp and pick out the attributes with #orgmode macros.

{{{fu(hero)}}} overcomes {{{pa(hero)}}} foe!

Here using `fu` for “full name” and `pa` for “gendered possessive adjective” (his/her/their/its).

In favor of #troff is the lower-level stuff. You can use macros to define strings en masse and then override individual choices for particularly weird characters. The downside is that you end up building up a library of macros to supplement your chosen package so that the main body of your document looks more like semantic than physical markup. And you probably need a #Makefile to assemble anything beyond a trivial document.

In favor of #LaTeX is mostly the higher-level stuff, and the short distance to semantic markup. #orgmode shortens this even further, and you can build your document in a single command (C-c C-e l p). But now the low-level stuff becomes annoying.

Perhaps with more research I can find the appropriate packages, but that may obviate the benefits of #orgmode altogether. Hopefully a well-fitting puzzle piece is out there, somewhere…

It’s all #tradeoffs but it’s not for paid work so I only have to worry about whether or not it works for me.

Now available Ahead of Print! "Population Dynamic Consequences of Context-Dependent Trade-Offs across Life Histories" by Louis Bliard, Maria Paniw, Dylan Z. Childs, and Arpat Ozgul: https://www.journals.uchicago.edu/doi/10.1086/730111

#populationDynamics #lifehistory #heterogeneity #covariation #tradeoffs

^-----

toot to amplify upthread toot, by adding content hashtags:

#Golang
#programming
#latency
#instrument
#instrumentation
#APIs
#measure
#measuring
#metrics
#stats
#monitoring
#observability
#perf
#perftools
#performance
#scale
#scaling
#scalability
#benchmarks
#tuning
#regression
#optimize
#optimization
#time
#compute
#tradeoffs
#software
#concurrency
#threads
#multithreading
#goroutines

USGS Study Estimating A Monetary Value For Floodplain Ecosystem Services In The Chesapeake Bay And Delaware River Watersheds
--
https://www.usgs.gov/centers/chesapeake-bay-activities/science/floodplains-provide-millions-dollars-benefits-every-year <-- shared technical article
--
https://doi.org/10.1016/j.jenvman.2023.118747 <-- shared paper
--
#GIS #spatial #mapping #model #modeling #spatialanalysis #spatiotemporal #flood #flooding #floodinnundation #innundation #extremeweather #climatechange #watersheds #floodengineering #floodplains #nutrients #sediments #sedimentation #fluvial #soils #erosion #floodwaters #agriculture #farming #economics #accounting #mitigation #tradeoffs #management #landforms #geomorphology #ecosystems #publicsafety #communityhealth #appliedscience #water #hydrology #benefits #benefitstransfer #regulation #quantification #value #loss #lossanddamage #lossadjusting #Hazus #ChesapeakeBay #DelawareRiver
@usgs

@CarlG1VIF #JT65 was responsible for my best distance/power ratio to date. Despite being such close cousins, and knowing the approximate #tradeoffs between the two modes, I somehow find #FT8 to be less compelling. Technically impressive, nonetheless. It’s never fun to discover the #bandwagon (#pun at your discretion) has moved out from under you.