byuu

108 ms·

811.
by byuu 12y ago
For me, it's 7822x4096. Or even 7112x4000 if you must. This really should be called 2160p, but you know, marketing. Also really loving my 976GiB "terabyte" hard drive, and my "ten meg" 1.25MiB/s broadband.
812.
by byuu 12y ago
FreeBSD has GEOM/geli, which is a block-level (sub-filesystem) encryption method written by Paweł Jakub Dawidek (a Pole). It allows your choice of several data integrity verification algorithms, several encryption algorithms, and the u
813.
by byuu 12y ago
Tom Wheeler happened. Despite his industry and lobbying connections, he raised a lot of money for Obama's campaign, so he was appointed as the new FCC chairman.
814.
by byuu 12y ago
If I want an environment for my cell phone or tablet, I'll use an environment designed for a cell phone or tablet; like Metro, Gnome, Unity and Android. If I want an environment for my desktop, I'll use an environment designed for
815.
by byuu 12y ago
Thanks to a curious Google search four days ago, I just found the obituary for my father, who died after a long battle with cancer ... three years ago. Didn't specify which kind. I never really knew him: all added up, I spent maybe two
816.
by byuu 12y ago
The Japanese Famicom didn't have a CIC lockout chip, which let you hotswap games and then soft reset, preserving all of the RAM (a power cycle doesn't decay all RAM instantly, but it deteriorates rapidly.) People would play Mario,
817.
by byuu 13y ago
If you wanted two separate threads to share data on the stack of one thread, why not just pass the second thread a pointer to the first thread's actual stack data, instead of relying on stack-relative addressing? For your ASM example,
818.
by byuu 13y ago
> Threads should already have separate stacks don't they? There are two type of threads: cooperative and preemptive/parallel. Coroutines with stacks represent cooperative threading. There's only ever one actual hardware th
819.
by byuu 13y ago
It's always nice to fix up software, but it adds maintenance costs. If you get your patch submitted upstream, it can take months or years before it's in official repositories. And it could be declined. You can wrap all the changes
820.
by byuu 13y ago
Well, we are currently connecting to the controller port because it's really easy to connect to those. But of course you can only hammer at those registers at around 40KB/s. So yeah, a friend made a PCB and found some female edge
821.
by byuu 13y ago
I was able to build a serial bridge between an SNES and a PC on a simple breadboard with stock parts: http://i.imgur.com/sPKGvl.jpg (the output is from a Teensy that is running as a USB<>serial device, so the PC sees
822.
by byuu 13y ago
Regardless of the merits of this particular case ... I'm always happy to see people improve their lots in life through education. If someone can learn to program and earn significantly more money, they should go for it. However, I am c
823.
by byuu 13y ago
Half the people tell me that CS grads have to create new programming languages, write compilers, toy operating systems, computer emulators, learn thousands of complex algorithms, etc. And then the other half tell me that there are CS grads
824.
by byuu 13y ago
That is terrifying D: And this is why I won't even say a single word of Japanese when I go the local Japanese restaurant (and yes, they definitely speak it as I can hear them talking to each other and their Japanese patrons.)
825.
by byuu 13y ago
> Well, if you used the kanji then we wouldn't have to guess ;) It was a trick: kami was used as a portmanteau of KAeru (frog) and MIso, so in this case, kami = frog-flavored miso soup :P
826.
by byuu 13y ago
Well there's always hanja, but I know 99.99% of Korean is written in hangul (beautiful system, by the way.) The only major downside I see to Korean is that it joins only Japanese and Mongolian in being an SOV language. "As for the
827.
by byuu 13y ago
> 的 de/di, 地 de/di, 长 zhang/chang, 重 zhong/chong, and 行 xing/hang are all quite common in both pronunciations. Ah, see I only know around 30 readings for Chinese characters (since I don't trust any Japanese
828.
by byuu 13y ago
A very insightful article. In my experience though, having studied both; and also from a friend who is moderately fluent in both; I believe Japanese is more difficult than Chinese. When it comes to the writing system, a Chinese character ca
829.
by byuu 13y ago
I really would love to go the immersion route, but just cannot do so. In my 20's, I was always far too poor. Perhaps I should have gone the student loan route and tried harder then, but unfortunately I didn't. In my 30's now,
830.
by byuu 13y ago
I've been attempting to pick up Japanese for about 15 years now. I've found a general pattern that I can go at it intently for 6-12 months, with about 4-6 hours a day of study. With that, I ultimately get to a point where for each
831.
by byuu 13y ago
Yes, it's definitely causing me discomfort to look at them. I see the blurred area, and try and fail to focus on it. 3D effects really don't translate well to a 2D display. I get what they're going for, but I'm personall
832.
by byuu 13y ago
> If you want safety, stop thinking in terms of blame and vengeance But that's the thing, I don't think anyone is really doing that in the industry. It's not the solution to start blaming the programmer, but it's a pa
833.
by byuu 13y ago
> I think the reason you don't see this as a real language problem is because of status quo bias. If we could go back and revise C before it became widespread, it'd probably be wise to do so. In a cross assembler and scripting
834.
by byuu 13y ago
A dead code analyzer would be even more effective than making a non-backward-compatible change in a 40-year old language. I'm not convinced enforced {} is such a compelling advantage, just because of one company's screw up. I&#x27
835.
by byuu 13y ago
But would you say it makes more sense to put extra burdens on the majority of good apples to protect the few bad apples? If we accept this as just an honest mistake, then can you name anything a programmer could do that you would consider j
836.
by byuu 13y ago
That would really start to hurt readability. There are plenty of instances where the body is very similar save for a small change, and having it lined up in a grid makes it much easier to read. As a contrived example, you can look straight
837.
by byuu 13y ago
> The fact that bugs can also be introduced via an erroneously designed switch statement is a red herring. I really didn't think so. Nor did I think it was slippery slope. If our goal is to make a language that's safe against t
838.
by byuu 13y ago
No, I'm more claiming that there's too much eagerness to blame ones tools. And that's very dangerous to me, because they blunt my tools in the name of safety. So you have these advocates coming in, saying we should stop using
839.
by byuu 13y ago
I really don't see how enforcing {} syntax on all conditionals is going to make us so much safer. Yes, people make mistakes, but this is a pretty huge screw-up. If you are modifying an unbraced if-statement and aren't paying atten
840.
by byuu 13y ago
If he becomes the new CEO of the Javascript Corporation, possibly. There weren't boycott calls when Eich was CTO of Mozilla.

More ›