wiener - 1 -- [3:31]
wiener - 2 -- [3:32]
wiener - 3 -- [5:39]
wiener - 4 -- [4:01]
wiener - 5 -- [5:42]

http://www.fsf.org/blogs/community/supreme-court-bilski

Here's hoping the supreme court does something good. Fingers are crossed.

1 Comment

newt - 1 -- [13:04]
newt - 2 -- [13:26]
newt - 3 -- [4:54]

I got a while back this ASUS eeePC 901, with a 1.6ghz Atom and 20GB of SSD. When I first got it I upgraded the RAM to 2GB, and installed Windows XP. It wasn't that great, so then I tried Win7 pro on it, which almost worked, but would just freeze for lengths of time for no apparent reason. The keyboard is tiny and has a very different arrangement from what I'm used to. It sat idle for a while, and since I have been developing on Linux (hello, SWELL/generic), I decided to install Ubuntu on it. The new verdict:

I love it. It's reasonably fast for compiling, installing new stuff is easy (apt-get ftw), Firefox w/ flash is fine, Xchat is decent enough, the stock mail client is very usable. The best part is that the battery life is fantastic, the screen is bright, there are very little moving parts, and it feels really solid. Yes, a bit like a toy, but I'm not worried about breaking it. Anyway, I'm fully on board with the netbook thing. Maybe next time I'd get one with a slightly larger keyboard, though...

Oh yeah and the other part of what I'm saying is: I'm definitely appreciating where Linux distributions for the desktop have gotten. Almost there... ;)

I get that the "strict aliasing" optimization of recent C/C++ standards allow for great optimization. And I get that gcc has some anciently-designed optimizing, but at any rate, it annoys me that gcc will detect strict-aliasing violating code, and still go ahead and generate code that is obviously wrong -- i.e. when it knows that two pointers ARE in fact pointing to the same memory, it assumes that they can't possibly, and optimizes as if they don't. LLVM probably doesn't have the same problem, heh. Oh well I'll use -fno-strict-aliasing and meanwhile go through and use unions (and occasionally C++ templates) to make our stuff compatible with strict aliasing optimizations.

Of course, on performance sensitive code this is a huge time sink -- I ended up (on our anti-denormal code) looking at the output of many iterations of the same code on gcc i686, x86_64, vc6+icc10, vc2005+icc10, icc11 on osx, gcc ppc, etc, to try to find source code that worked properly and produced decent assembly code. The variety of code produced by each combination is staggering. Also, I found that often the code I thought would be fastest was not, when benchmarked. Oh well.

9 Comments

A better delivered post of something I've been telling people for years -- that execution is way, WAY more important than ideas. Yes, the ideas still need to be reasonable, but beyond that, it's how you do what you do that counts.

10 Comments

theman

freeform jam with brennewtnoj

freeform jam with chr

After seeing a slashdot post about people running OS X on the Nokia n900, I read some more info about the n900. It seemed like great hardware, and was debian-linux based, so it seemed like a good platform to play with. Enticed, I found it on Nokia's site, complete with a 14 day return policy.

I should mention, I have/use an iPhone 3GS. Apple ends up pissing me off to no end, but I really end up liking the 3GS. It's a great phone/browser/apprunner/notetaker/calendar/ipod/etc. If it wasn't locked down so tight, I would like it even more. So really I end up disliking the idea of the iPhone, but liking it in reality.

The n900 is pretty much the opposite -- the idea is great. Having a phone I can ssh into and install g++ and make on and build stuff and run on, is great. On paper, everything's there. This is what I found:

• Screen: the screen looks good. It's high resolution, but the touch sensitivity of it isn't great, it ends up feeling clunky.
• Storage: on paper it has 32GB of flash. This is great. What's stupid is that the root fs is only 256mb of NAND memory, and while you can install extra packages via apt-get etc, if those packages aren't carefully designed, it ends up filling your root filesystem. Even the obvious things like making /var/cache/apt point to the big disk, they could do, but haven't. So basically you have to do one of many hacks if you wish to install much. The biggest thing I found was moving various /usr/[share|lib|bin]/xxx directories -- all stuff nonessential to booting -- to the bigger disk and symlinking them. Anyway, it's dumb that you should have to do this. Complete pain in the ass. I eventually got everything I wanted installed, but if the point is to have an open extensible phone, you gotta make it do that out of the box.
• WiFi: support seems solid. When the phone is sleeping, you can still ssh to the phone (if you installed OpenSSH, which is easy). RAD.
• SSH: awesome. Fast, the thing really feels quick. It is 600mhz, and for command line linux that is super fast. I remember my P133 being quick, too.
• Web: the browser is pretty solid, and flash support kinda works (wasn't really fast enough for YouTube, but there seems to be an app for this).
• Keyboard is usable. Better than the iphone's, for me, but not fantastic either.
• No AT&T 3G support. I don't care whose fault it is, but come on?!.
• Camera: quality was decent. The video recording was pretty good, sound seemed better than the iPhone 3GS's. Here's a youtube video we did as a test (apologies for the content).
• General UI: Some things are super fancy (nice blurs, transitions), but other things are not even half baked. There's a nice standard for "close window" or "go back" button locations, but 90% of the time the buttons for those are not visible, yet if you click them they are there. Silly stuff.
• Multitasking. Mmmm. so good. I like. Hear that, Apple? It's not even a pad...

So I sent the thing back. It didn't last 24 hours. The dealing with root fs, I could get past that. The lack of AT&T 3G support, that made the decision easier. I really tried. I wanted to like it.

6 Comments

Thanks to a user on the REAPER forums: 1000s of ways to die: Greateful Bed.

Doesn't seem like a show I'd watch, but amusing to see REAPER on it, at any rate. Now if only it ended up on It's Always Sunny in Philadelphia. Then we would have made it.

1 Comment

freeform jam with brennewt

freeform jam with chr and tele

freeform jam with brennewt

Some people picked through them for a bit... Then poof, they all disappeared. Nobody took the sign, though.

4 Comments

CRTs, MHz, megabytes, and Linux. Making usable boxes from junk, to donate.

8 Comments

freeform jam with newt

freeform jam with brennewtchr

brenchr - 1 -- [7:17]
brenchr - 2 -- [20:27]

(after spending much of the day banging my head against the wall)

#include <stdio.h>
struct test1 {  double b; };
struct test2 { int a; test1 b; };
test2 foo;
int main() 
{
  printf("%d\n",(int)&foo.b.b - (int)&foo);
  return 0;
}

What does this print? On Windows, it prints 8. On OS X (or linux), it prints 4. Which means, if you access foo.b.b a lot, it will be slow. UGH. I guess that's why there's -malign-double for gcc. Now if I can just figure out how to enable that for Xcode...

Recordings:

freeform jam with brennewtnoj

7 Comments

freeform jam with brennewtnoj

freeform jam with brenchr

Woohoo! Recommended listening/viewing (apologies for so much Jason Lytle fanaticism).

1 Comment

On 28th street and 6th, fall 2009

Comment...

1 Comment

freeform jam with chr

I wish I could provide as good a present to the world this Christmas as this:

Jason Lytle's "Merry Xmas 2009" :)

I'm listening now, very happily.

Edit: updated the URL. mmm I cant wait for his next album too.

2 Comments

freeform jam with brennewt

freeform jam with newt

freeform jam with chr

My previously mentioned new program, SnapEase, is now available with source!

6 Comments

england, earlier this year

3 Comments

I took this in 2000, on slide film.. but here it is, processed and uploaded with snapease heh (testing it)

Comment...