• 2 Posts
  • 506 Comments
Joined 3 years ago
cake
Cake day: June 20th, 2023

help-circle





  • His quote from the article:

    “[…] I need to come to terms with the fact that the level of dopamine I’ve been getting from interacting with LLMs…with doing more and more and more and more…is not healthy for me or good for the world. It is careless, and has disconnected me from where people are on this.

    I was talking about this with [my wife] Katherine last night and she did not pull any punches. Frankly, neither did [my brother] John. Neither of them think I’ve been being healthy. I need to readjust.”

    Not really knowing the drama before today, it seems like he is being very rational and speaking honestly about the effects LLMs are having on his behavior and that he identified he needs to change, which is what the whole article is about.


  • Well if the requirements.txt is pinned to a specific version of a dependency of a dependency, you might not know or really care why that’s set. But then this becomes a nightmare and dependency hell laterif you want a newer version of some package, and that newer version requires a bunch of newer packages and loses the others. At that point you probably will toss your old file and start a new one from scratch piecing together all the requirements with like pip freeze in a new virtual environment.

    Sure you could omit the versions, but then everytime you deploy, you don’t know what you’re going to get and a deployment today would be very different next week with a whole bunch of different versions of dependencies.


  • Yes exactly, like if I know my app needs the requests library, I will just put that in requirements.in but after compile requirements.txt will include the exact version of requests and every version of each dependency. So that every time pip install is run, all dependencies are always the same despite what happens upstream


  • Curious what others have to say, but my go to is to have a requirements.in with direct packages I need for the project, and then run pip-compile to generate all the dependencies with their exact version at the time so that deployments are repeatable. This works well for deployment, but if I were writing a library for others to use, I think you put the direct dependencies in setup.py









  • Nintendo is being singled out because they’re withholding the tariff refunds for tariffs they never paid and passed on to the customers. When the tariffs were imposed, no one really blamed Nintendo and knew it was the Administration’s fault. If Nintendo didn’t want sales to drop because of higher prices, they could have eaten the additional tariff cost until it all got sorted out. Had they done this, then they’d be entitled to that tariff refund money. Instead they passed on the tariff cost to customers, which sucks for customers but was really the only sensible thing Nintendo could have done given the circumstances, and most people aren’t really blaming Nintendo on that decision. But now Nintendo is trying to have it both ways, not pay any of the tariffs and keep all of the tariff refunds which is why they’re being singled out. It’s pure greed on their part with blatant disrespect to their customers.



  • Probably going to get hate for this and reveal my age a bit, but i’ve been on Ubuntu since 2006 back when they’d actually mail you CDs for free. My desktop’s hardware has been a ship of theseus since then, and no dist-upgrade really ever broke things, and I think the last time I did a full OS reinstall was in like ~2011 when I got an SSD that was a smaller side than my old HDD, so I couldn’t just clone the drive with dd. Everything works well for what I need it for, and don’t need the bleeding edge.