I’m not sure I understand what you mean.
I’m not sure I understand what you mean.
For an API there should always be a version parameter/endpoint, imho.
Edit for further context: Ideally, a parameter.
You’re in luck! The book I’ve generally heard recommended to beginners for Python is available for free online!
The biggest reason for me is that it’s less data to send over a network. Especially when I’m working with lists of objects, including null fields can add a noticeable chunk to the payload.
There are some cases where it might be worth it to differentiate “No value” and “No attribute”, but in most cases they can be treated the same, since the data should really be validated against a schema anyway.
Yeah, I’m also confused. If an attribute is null, I would prefer to simply not serialize it.
I’m sure there are edge cases where someone might prefer to include null attributes, but generally they should be treated the same either way.
I say we ditch this nonsense altogether and go back to vague descriptions of the Sun’s position in the sky.
That used to be the case, back when Steam Sales were a chaotic feeding frenzy of discounts. These days it’s pretty much the same throughout.
The first and easiest thing I’m seeing is to up that meager developer hardware budget.
Haha well that’s uhh…
Ngl that’s a interesting idea. Would definitely want it running locally, though.
I think I’d be okay up until you pulled intellisense, at which point I would literally deflate like a balloon.
When I quit at McDonalds to start a career in welding, the owner of the store happened to be visiting. He took me aside and told me “You know, those guys at… (Sorry, what was that place called again? Right…) You know, I’ve heard the people there aren’t as nice as we are here. Are you sure you want to leave?”
I’ve never wanted to punch an old man so much in my life. In that moment, he was the personification of class warfare to me, trying to “trick” me into throwing away my future just so he could have more cheap labour. And the fact it was so blatantly obvious added insult to, well… insult.
Anyway, it’s not the same, but the “wallpapers” thing definitely gives me the same vibes, lol.
I used to have to put !g (redirect to Google) on like half my searches to get the results I wanted. These days, I actually generally prefer DDG’s results over Google’s.
Haha no way! At this point I can’t think of a reason to switch from VLC, but I’d love to see a Winamp renaissance.
I wonder how much of this idea that you can be “too old to learn” came from the advent of schooling and childhood education. Like, in a time before everyone went to school up until a certain age, did people still have this mindset?
Regarding the TTS specifically, I remember looking into TorToiSeTTS back when this stuff was first coming out. You can generate ElevenLabs quality audio with it, but it’s insanely slow. In fact, when I was looking into it, it seemed like ElevenLabs may have been using a (much faster at the time) version of TorToiSe TTS, given the output is so similar.
According to the linked Github page, they seem to have solved the speed issues now, so it might be worth looking into. Of course, the other commenters have provided solutions that are pre-integrated into the LLM, but if you’re just looking for TTS this could be worth checking out. Also worth noting that this requires an NVIDIA GPU.
I run JF in a docker container, and although I don’t have backups of my config files yet (because I don’t really care about setting up from scratch if need be), it would be trivial to simply backup the mounted config volumes. Makes upgrading safe and easy, too.
That’s probably how I would recommend going about this, personally.
The prediction that NVIDIA’s open GPU Linux kernel driver would be the default for Turing and newer GPUs, I assume.
It’s true. I even live in a place where the “Software Engineer” title actually does require a special designation, and I’m a “Software Engineer”, and I have no such designation, so there’s that.
Those are two very fair points - I agree.