aceperry

I hear a variation of this type of thing from windows fans constantly. "It's your hardware's fault." But never Window's fault. My experience is this; most of my computers are dual boot with windows and linux. When I have a problem with windows, I'll boot into linux and the problem goes away. Same hardware.

I got stumped at the Frobenius norm (11/13). Everything I typed in returned this:

NotImplementedError: the 'axis' parameter is currently not supported on line 7

I used variations of: np.sqrt(m.sum(m.prod())) np.sqrt(m.sum(m2))

It's been a long time since I've taken linear algebra, so I don't remember some of these operations.

What is the AGI problem? I've never heard of it.

Hey, I loved your 10 minute python tutorial!

What's the political situation like there? I hear about things like voter suppression by the Republicans and other shenanigans in those states.

Arch looks like it's got a lot going for it, and I sometimes find myself looking at their documentation when I'm trying to shoehorn a package into ubuntu. Even though I used Gentoo linux for a long time, very similar to Arch in lots of ways, I haven't been able to install and configure Arch successfully on my computers. I'm sure if I spend a lot more time on it, I'll be able to do it, but I just don't have that much time to spare, so I stick to ubuntu and variants. But I really do like what I see on Arch.

I've been using Ubuntu and variants for a long time now. I find lubuntu is ok and small in terms of size. As for older computers, I must have some really slow ass hardware, because even lubuntu is kind of slow on some of my hardware. I stick to standard ubuntu on my desktop just to see what it's like, but prefer xubuntu because I prefer the DE over the gnome crap. I'm used to the more standard keystrokes and shortcuts that you see on windows and the IBM standard which gnome wants to ignore. It's also tough to customize gnome to how I like to do things.

#4 makes me laugh because I had that thought when I was trying to work with bluetooth. I think the real problem is two-fold. The original spec required approval from all members of the consortium. I think a lot of things were left out that are really important, such as security. I know they had security from the start, but really, it's bullshit. Plus the original chipsets were incredibly expensive, and my pure speculative thought is that they cut corners (the firmware part) to bring them out to market. I was really surprised, shouldn't have been with hindsight, to see when bluetooth chipsets started to reach price parity with wifi chipsets.

The second thing is that much of the low level firmware for the stack is closed source stuff that is written in house. I suspect, after working with some of that shit, that it's poorly done and is a major cause of unreliability. Don't know if it would make any difference if it was open sourced, because the hardware/software combo is a lot like what you see with graphics cards. Everyone has their own secret sauce and they don't want to show it to the world.

What kind of documentation do you look at, and how do you document that sort of thing?

There are a few other open-source and crowd-source projects like this that I've seen. It's interesting to see so much volunteer response to the crisis.