> All of the languages just boil down to syntax to me. Rust's semantics are quite different than C or C++, much moreso than something like Go. Also, go learn some other programming paradigms and you'll quickly learn that there's a lot more than just syntax differentiating them. Haskell, ML, Scheme, J, etc...

This isn't obviously true at all. I wrote C for 20 years, and now cry every time I have to use C instead of Rust. It's like night and day difference.

The only advantages C has over Rust are longevity, compile time, binary sizes, and amount of code in the wild. I've written a ton of C code and maintained even more. Despite being a relatively small language, the surface area for bugs is enormous. I will never use C again unless I have a very compelling reason to. I'm not saying Rust is the end-all-be-all language, but it's WAY better than C.

If the price was closer to NAND, I'd always opt for Optane SSDs. I think everyone would. Instead, they price it ridiculously high, it flops completely in the consumer space, and Micron exits the space entirely. Is it really that much more expensive to manufacture? Or are they artificially holding it back so that it performs just a little better than NAND so they can milk the market for a long time? Judging by Micron losing $400 million and selling it's facility in Utah makes me think it's just expensive to make.

The real problem is a conflict of interest. If all manufacturers provided updates to their phones for 5 years, you could be sure that far fewer phones would be sold each year. So instead they cut off updates to encourage/force consumers to buy new phones more frequently - creating a larger market than it otherwise would be. What we need is a separation of hardware and software so that the hardware can be used until it dies without sacrificing the software security updates.

If this goes through, they should mandate a strict diet of vegetables, fruit, legumes, nuts, seeds, whole grains, fish and water for the duration of their benefits collection period. If this could somehow be enforced, very few of them would be on "disability" for long. By the same token, getting drunk should be considered for disability. The solution is simple. Stop eating processed garbage and eat lots of whole foods instead.

League of Legends is quite a captivating game. Each game lasts usually around 30 minutes. There is a bit of a learning curve though. Once you get over that small hump, the game is a blast to play.

I find this to be a very good move - assuming A,B,C still represents the same grading scale. You either take school seriously, or don't bother. *Anyone*, regardless of intelligence, who puts in an honest effort will be able to get a C in any class. This is already how it's done in college engineering degrees. Anything below a C (and sometimes a B-) is considered failing.

I tried KDE 4.3.5 for a few months, but had to revert back because KMail/Kontact crashed constantly. If I can't use Kontact in KDE, then I've lost half the benefit of using KDE. I wonder if these problems were included in the 7000+ bugs they claimed to have fixed in 4.4.0. Now I'm back to my ol' tiling window manager - Awesome (which also crashes from time to time :/ )... Maybe I'll give xmonad a try.

I still can't get over that clunky fly-out menu that dwarfs each icon I mouse over. KDE 4 in general looks very attractive - much more so than a default Gnome instance... but it just seems to get in my way constantly. Maybe it's just my workflow.

Linus' responsibilities require him to be very strict. If he wasn't so hard-nosed about regressions and code quality, Linux wouldn't be where it is today. Unfortunately, he's also a jerk (or "git" if you'd rather). I've worked with similar people, and they make you want to pull your hair out. There is no excuse for Linus to be so inconsiderate. Alan has contributed an enourmous amount of work to Linux, and the least Linus could do is show him a little courtesy when conversing with him.

I don't understand why people are so surprised that C is still very popular. C is the king of performance and likely always will be. Many amateur developers don't like it because it takes a bit more effort to learn and use correctly. C > C++ > C# > Java They may have combined C and C++ staticstics, but to include C# would have been completely obsurd.

I switched to Dvorak 2 years ago. Before that I had typed Qwerty for about 20 years. I feel that I have a good sense of the strengths and weaknesses of both. On paper, Dvorak looks great and Qwerty looks terrible. But Dvorak isn't without its warts, and Qwerty isn't all that bad for those who don't experience discomfort from it. In my experience, Dvorak relieved the pain in my hands and wrists (although the right pinky took some time to stregthen). My hands and fingers would tire very easily when typing Qwerty. As for speed, I feel they are roughly equivalent, although my speed has increased approx 10 wpm. I know some very fast Qwerty typists (~160 wpm), and some very fast Dvorak typists (~165 wpm). As for me, I peaked at about 95 wpm. As a side note, Dvorak isn't the only alternative layout that I have worked with. I also spent some time on modified version of the carpalx BULPKM layout and stuck with it until I was up to about 60 wpm. That layout was extremely comfortable to type on (noticeably better than even Dvorak), but it was apparent that comfort was the goal as opposed to speed.