Asklemmy

43940 readers

534 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
[email protected]: a community for finding communities

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago

MODERATORS

[email protected]

706

What is your "inexpensive" hobby that turned out to be expensive/ you gradually invested lots of money into? (sopuli.xyz)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

810 comments fedilink hide all child comments

Edit: so it turns out that every hobby can be expensive if you do it long enough.

Also I love how you talk about your hobby as some addicts.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago (1 children)

Same. I'm lucky for software to be my hobby/career. It's practically free. Contrary to popular misconception, it doesn't require any kind of special or more powerful hardware (for most dev, at least). Maybe $150 for a second monitor, for sanity, but that's not actually necessary.

...I mean, I do have good hardware too, but that's for my gaming hobby, not my software hobby.

[–] [email protected] 2 points 1 year ago

To be fair, if C++ or Rust is your thing... let's just say I'd have a Threadripper if they weren't five grand.

I once had to (repeatedly) compile a C++ codebase on some Lenovo shitbook. It ended up being so infuriating (thirty seconds, minimum) that I wrote a few load-bearing shell scripts to rsync everything to my desktop, build it, and copy the binary back... which was ultimately about five times faster.

Man, I wish I could have just used MicroPython for that project.