Where I landed was as such: I hated the very concept of AI. My post history, if you look, deliberately referred to the tech as LLMs, and I mostly still do.
I've been behind the 8-ball at $dayjob, for reasons I don't have a say in, nor does anyone in my entire CoC. Vendors are delayed, we have hard shipping deadlines on our end.
Work pays for an expensive "AI" sub. I used it because I'm in a jam and deadlines are tight.
It worked. I'm a decent engineer/programmer. The tech saved me a month, at least. I think the money around all this tech is wrong and bad, but in a vacuum the tech works.
Well since you mentioned it, I posit that most of the financial issues the world is facing today is because the GFC wasn’t allowed to occur, it’s been a slow bleeding out ever since.
The point of the law was to generate money for the state to fund the same mistakes France and GB are currently reeling from. Reducing power had nothing to do with it.
> The point of the law was to generate money for the state to fund the same mistakes France and GB are currently reeling from.
Which mistakes of France and GB are you referring to? The money (90%) will go to health care spending. So, yes - vastly overpriced crap - France spends half for universal care with better outcomes.
Oh man, they answered the question in the beginning:
> The reason, according to the researchers, has to do with the information environment AI systems can access.
Amusingly:
> The researchers also found that incorporating X search amplified left-leaning recommendations in Japan, the opposite of expectations based on the U.S. discourse environment.
Twitter in Japan is more comparable to Instagram in the US in terms of usage (both being the third largest platforms, on which over half of their respective citizens have an account).
I guess “something” meant a vetted web of trust. My children will be better off if they don’t need to learn to navigate the internet cesspool, so either you’re wrong and it sucks for them, or you’re right and it sucks for them. Either way, well-played! Very clever!
Oh wow, hi! I think my biggest “gripe” with docker is that everyone grabs it as a hammer and views many problems as a nail. Am I way off base with that? What was your original vision for how docker might be used in the wild?
I actually enjoy sports gambling, and since its been legal and the apps hit, I have won more than I've lost over the past what, 3-4 years now. Not a lot more, but enough to where I haven't had to deposit money in a few years. Call it an entertaining hobby, my goal isn't to make real money, just to feel smug about being smarter than the odds-makers.
I completely agree with you. Watching gambling ads makes me irrationally angry. They should absolutely, 100% be banned from advertising, similarly/identical to cigarettes. Nuke them from orbit.
Whenever I write I library I don't allocate memory. If memory needs to be allocated, the program calling into the library allocates memory and passes a pointer (or reference I suppose) into the library call.
Clearly this can't be enforced, but I've always found it bad practice to allocate memory inside a library.
How to you manage the API when caller doesn't know the right size to allocate? I mean you could pass an allocator object (ala zig/C++ stdlib etc), though I'm not sure I like the extra arg on functions... I guess a quasi-global-variable approach (e.g. a "context" object, passed to all functions, which can hold an allocator, or equivalently implicit arguments in a functional language) would be one way to achieve that without the "noise" of explicit allocators passed everywhere.
You can also design a "dual-pass" API. Basically you have an API call to estimate or calculate the memory usage needed and then another parameter / API call to actually do the operation.
For example the WideCharToMultiByte [1] function of Win32 handles UTF-16 to UTF-8 conversion. If you pass your destination pointer as NULL, then it purely calculates the number of bytes you'll need in your buffer. Then the main program actually allocates the memory and calls it again with the populated destination pointer.
It's not really practical to do this outside of simple cases. For example, a modern userspace GPU driver must allocate lots of memory in hundreds if not thousands of places to implement a standard API and there's no way around that.
I've been behind the 8-ball at $dayjob, for reasons I don't have a say in, nor does anyone in my entire CoC. Vendors are delayed, we have hard shipping deadlines on our end.
Work pays for an expensive "AI" sub. I used it because I'm in a jam and deadlines are tight.
It worked. I'm a decent engineer/programmer. The tech saved me a month, at least. I think the money around all this tech is wrong and bad, but in a vacuum the tech works.
reply