Working on a ground up design for a mechanical keyboard while I get my cancer treatment. There’s lots of projects that make this easier but I wanted a challenge and wanted to go from the ground up specifically.
Originally I picked a SiFive microcontroller but found that all of the ICs which mediate USB/JTAG/etc are hopelessly sold out. I switched over to a microchip based ARM chipset with built in USB. I’ll probably need to pick up a JTAG probe to do some debugging but that’s fine.
It’s been fun and very educational. I hope I get to finish it.
Lyme Disease and a bad spider bite took my grandfather's life before I was born. From what I understand, nowadays they treat the disease by basically nuking it with antibiotics. Its probably best to talk with a doctor and see if you can get some more advice from them, or perhaps seek out a dedicated support group online. They'll probably have more tips and tricks.
That, and do some research on how to prevent the tick bite in the first place. When I was young my mom always made sure to point out that we needed to be careful during the times when lyme disease was most prevalent. If you're in an area with a lot of brush and you see deer around, you'll want to be careful. Deer ticks are the primary carriers of the disease. We'd always make sure to keep an eye out for the telltale bullseye shaped rash - luckily we never saw it outside of pictures online.
I'm using Chrome on Windows and I'm noticing that when I have my Chrome window on one half of the screen, the responsive design breaks a bit. Basically, if I try to scroll to the right, about 1/4th of the "Ready-to-Code XCode" is cut off.
Depends on how much you want to spend. The Macbook Pro models generally have faster CPUs so you'll see a benefit there in terms of compilation time and general snappiness.
The MBP gives you the option of the Retina display though. My personal opinion is that that in and of itself is worth the extra cost :P. If you're going for the 13", be aware of the fact that it can be a little bit laggy when you're trying to something graphically intensive. Depending on your use case, you might be better off getting the standard MBP if that bothers you.
Maybe its just VirtualBox or some other variable in my config but I've found the virtualization experience to be sub-par even when running a very light Arch/XFCE setup. Maybe if I was just using the terminal it would be fine, but laggy drawing really annoys me.
Right now I've got a small Linux partition on my laptop and I've been very happy with that.
I don't see how giving certain users an upgrade could be extrapolated as bad - It's not like they are retroactively crippling people's existing hardware or anything. The reality of the situation is that certain companies are going to have different board/bios configurations on their GPUs and I don't think it is reasonable to expect AMD to provide a BIOS upgrade for all of these variations on their own.
Somethings tells me that the cards that are getting the BIOS upgrade are going to be the ones using reference designs (maybe it was stated as such in the article but the author's writing style is kind of bleh).
The author sounds like a videocard fanboy who's throwing a tantrum. He didn't get the bios update from his favorite video card company that the reference cards got, so now he's calling them dirty names on the internet.
Its awesome that Valve releases their toolkit and I agree that most of the tools are pretty decent. Hammer (the level editor) is getting really long in the tooth though - it hasn't changed much fundamentally since Half Life 1 was released. And even then, it was pretty much just a third party editor for Quake (iirc - some of the details may be off).
> Xeon Phi does not run anything any "local OS", Xeon Phi is a CPU arch. A computer based on Phi may run linux as a local OS, that does not magically mean the OS needs not be aware of the architecture and how to communicate with it.
I think that zvrba's post was referring to the fact that Xeon Phi cards are internally running an embedded version of Linux. The host system doesn't need to know about that technical detail due to drivers on the host system hiding that away, but he is still correct [edit: in that there is a Linux subsystem present.]
"Meanwhile on the software side of things in an interesting move Intel is going to be equipping Xeon Phi co-processors with their own OS, in effect making them stand-alone computers (despite the co-processor designation) and significantly deviating from what we’ve seen on similar products (i.e. Tesla). Xeon Phis will be independently running an embedded form of Linux, which Intel has said will be of particular benefit for cluster users."
Go Daddy has already backtracked on their support of SOPA.
To answer your question directly - probably not. Unless your site caters to developers and other technically-inclined people, you probably won't be hurt by using Go Daddy. At least not directly.
There is a reason why so many people are angry about SOPA. Under the bill's current language, SOPA will cause more problems than it claims to solve. I will leave it to you to do some research on the language in the bill, but to summarize; SOPA will break DNS. SOPA will have chilling effects on freedom of speech on the web in the United States, and possibly abroad. It will put an unnecessary burden on small businesses and startups by forcing these companies to strictly police user generated content. Piracy is obviously a real problem that hurts developers, artists, and many others. But by and large, the tech community doesn't think that SOPA is a good way of dealing with the issue of piracy.
Go Daddy threw their support behind this bill, which will probably end up hurting most of their customers in some way. They were arrogant about it too, in that they basically brushed off the boycott as being a nonissue to them. Obviously, they changed their minds after people started transferring domains en masse.
If you have no qualms with supporting a company that doesn't care about keeping the web a level playing field for small and large business, then keep on using their services. Personally, I transferred my domain over as soon as I found out they supported the bill.
Originally I picked a SiFive microcontroller but found that all of the ICs which mediate USB/JTAG/etc are hopelessly sold out. I switched over to a microchip based ARM chipset with built in USB. I’ll probably need to pick up a JTAG probe to do some debugging but that’s fine.
It’s been fun and very educational. I hope I get to finish it.