@jae@wizard.casa[/tmp] on Nostr: nprofile1q…4w7s7 Curator of Mastodon.art fediblock :newt: nprofile1q…amclj ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqgh2kwz4spt3y4d9kul5fr9yy4hnt2jvhal2sxs9jtstfq0yecw8s24w7s7 (nprofile…w7s7) Curator of Mastodon.art fediblock :newt: (nprofile…ynjf) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq8nexvs44uwvzhjlp3x3ua3f4n8npw45krta6nv9u5rkddecwnfqqramclj (nprofile…mclj) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqhu7u9rylkzk89y7sht98eyevsn3pwkgz7fwphm8e2p8gr6y3hd7q469qqf (nprofile…9qqf)
> But that is exactly the product of developers like that — who need 36 gigabytes or RAM to be productive 🤣
it seems these days it's "cheaper" to buy more hardware to throw at a "problem" than it is to retool and optimize the "problem". i can relate to newt. i had previous job where the laptop they sent (mac) would not allow me to pair-program with colleagues over slack-hangout or whatever it's called because i started paging to disk quickly running the development stack.
it's been over for a while. i could be wrong.
> But that is exactly the product of developers like that — who need 36 gigabytes or RAM to be productive 🤣
it seems these days it's "cheaper" to buy more hardware to throw at a "problem" than it is to retool and optimize the "problem". i can relate to newt. i had previous job where the laptop they sent (mac) would not allow me to pair-program with colleagues over slack-hangout or whatever it's called because i started paging to disk quickly running the development stack.
it's been over for a while. i could be wrong.