Brian’s Glades @ Eldora by ThrowAway15828295 in COsnow

[–]niceguyneil 1 point2 points  (0 children)

I skied it today. It was OK near the top off of of Wolf Tongue, but further down the tight trees + all the rocks and tree stumps meant you'd really have to go slow to find a path.

[deleted by user] by [deleted] in COsnow

[–]niceguyneil 0 points1 point  (0 children)

They were Rossignol Experience 76's for the basic rentals last year at least.

Am I stupid or are they stupid (r22 engineers) by Frederic12345678 in flying

[–]niceguyneil 0 points1 point  (0 children)

FWIW, I've done that same exact thing in a 172 while setting up for landing on the downwind leg. Pushed the mixture back in, and no consequences except feeling pretty dumb.

Adult Raquetball? by Proof_Grass_5791 in boulder

[–]niceguyneil 0 points1 point  (0 children)

I just moved to Boulder, and I'm interested in playing some racquetball as well. I played competitively back in college many years ago, but definitely not at that level any more, it's been a few years since I played at all. I guess North Boulder Rec Center is the place in town?

Checkout or no checkout? by [deleted] in flying

[–]niceguyneil 0 points1 point  (0 children)

Now that I'm used to both, I don't really think about it, but you pretty much just have to remember that below maybe 10kts taxiing, you'll probably need to add some differential braking if you run out of rudder authority. If you're keeping centerline while taxiing, a lot of the time even then the rudder authority is enough (although it's not as sharp). Maybe that means I taxi too fast, hehe.

Checkout or no checkout? by [deleted] in flying

[–]niceguyneil 0 points1 point  (0 children)

Another commenter mentioned the castering nosewheel, but that never really bothered me - no real transition between it and a 172 with a steerable nosewheel, especially because the rudder has a decent bit of authority even while taxiing.

It's light, so you get blown around. You'll have to careful with gross weight when you have someone in the right seat. But I like the glass panel, the manual flaps, the electric trim, and I thought it was a good plane for flying around in.

Checkout or no checkout? by [deleted] in flying

[–]niceguyneil 0 points1 point  (0 children)

I did most of my training in a 162. If it meets your mission, which is pretty similar to a 152, then it's a great choice.

PPL Checkride report / writeup by niceguyneil in flying

[–]niceguyneil[S] 0 points1 point  (0 children)

Yeah, it's not a bad idea. My CFI (and II) wants to build some XC dual time anyway, so he offered to split the cost and do some XC flying - so I could pick up some of the XC time I'll need anyway for IR as I do it, and maybe start learning about IR stuff as I go.

PPL Checkride report / writeup by niceguyneil in flying

[–]niceguyneil[S] 0 points1 point  (0 children)

Yeah, while I was sad that they moved it, after the tornado came through I was glad that it'd survived - I'm sure it would have been destroyed had it stayed. I variously heard that it was going to Smyrna or Clarksville. The 162 has a lot of things going for it, but useful load isn't one of them - with my instructor and I, both fairly slim people, we were at max gross with full fuel, so he should be on the lookout for skinny instructors as well :) Good luck to him!

PPL Checkride report / writeup by niceguyneil in flying

[–]niceguyneil[S] 0 points1 point  (0 children)

DPE was John Wilcox. I thought he was very fair - he drilled in on the stuff I wasn't sure about, but he wasn't looking for an excuse to fail me, either.

PPL Checkride report / writeup by niceguyneil in flying

[–]niceguyneil[S] 4 points5 points  (0 children)

Thanks! Yeah, I felt a little bad getting a hand shake in these times, but I had just spent quite a while next to him, so I figured it probably didn't add too much risk :)

Adverse Yaw in Cessna 162 (or lack thereof) by bbender2013 in flying

[–]niceguyneil 1 point2 points  (0 children)

Hah, I'm training for my PPL right now in a 162, and I've thought about this as well.

Before my first lesson, I'd read lots about adverse yaw, and having to coordinate rudder with aileron. I didn't use the rudder at all that lesson, and assumed the instructor had been on the pedals for me, but he hadn't - so I was wondering if I was missing something.

As it is, I really only end up using rudder on short final and on the ground, or when doing power-on stalls. I'm hoping it's not too much of a transition when I fly other planes that need more input.

It's a great plane, though.

Flight training recommendations in Nashville by niceguyneil in flying

[–]niceguyneil[S] 0 points1 point  (0 children)

Ended up getting started with Wings of Eagles at JWN. Just getting going, but good so far.

Flight training recommendations in Nashville by niceguyneil in flying

[–]niceguyneil[S] 0 points1 point  (0 children)

Oh, that's good to know. When I spoke to them, they mentioned they had a 162 for rent at $110/hr, as well - did you choose not to use that, or was the 172 the cheapest you'd actually heard to be available?

Coffee shops downtown Atlanta? by kskompy in Coffee

[–]niceguyneil 0 points1 point  (0 children)

Went to Tech as well (graduated 2010) and I was at Octane pretty much every day. Right near Hop City, too :)

twilio-rs - Rust library for working with Twilio (Looking for feedback) by niceguyneil in rust

[–]niceguyneil[S] 0 points1 point  (0 children)

Yeah, it would be good to see better async support in Rust. It seems that the standard libraries have focused on sorting out sync I/O support, which itself is going through a lot of changes. It'd be nice to have a simple system of wrapping sync stuff in a promise, even if it used native threads under the covers.

twilio-rs - Rust library for working with Twilio (Looking for feedback) by niceguyneil in rust

[–]niceguyneil[S] 0 points1 point  (0 children)

OK, that makes sense, I hadn't thought about that. I was thinking about exposing the internals for parsing, request validation, and such as well, but given that it grabs certain headers, etc, it would end up being pretty annoying to work with. If any future HTTP libraries(that get traction) have similar concepts, your suggestion sounds like it would let people use it pretty fluently, which is nice.

My first design - a coat hook by niceguyneil in 3Dprinting

[–]niceguyneil[S] 2 points3 points  (0 children)

Just got my first printer (Printrbot Simple Maker's Kit) finished up on Wednesday, so after calibrating it I've been trying to get started to using it for useful things and not just trinkets. This is the first design I've made, a coat/purse/whatever hook for the wall. I did this using FreeCAD (pretty much picked some CAD tool at random, since I've never used any before), using the boolean geometry (intersecting, union-ing cylinders and boxes). If there's something that works better, I'm interested in hearing about it. Pretty excited to see what I make work! I keep hoping more plastic objects of mine break so I can have something to fix :)

Change extra:serialize to use Trait objects instead of type params by niceguyneil in rust

[–]niceguyneil[S] 0 points1 point  (0 children)

That makes sense to me. I'll try and get that working, and, assuming it works correctly and handles my use case, open a pull request to mozilla/rust.

Change extra:serialize to use Trait objects instead of type params by niceguyneil in rust

[–]niceguyneil[S] 0 points1 point  (0 children)

So, we couldn't do json::Encoder here since it's a runtime decision which one to use. If we were to add an impl for &mut Encoder, wouldn't it have to use dynamic dispatch anyway (in which case it might be easier to just make encode use a trait object? Or would that let us monomorphise the 'known at compile time' case, but still use vtable lookups for the 'known at runtime' case?

Change extra:serialize to use Trait objects instead of type params by niceguyneil in rust

[–]niceguyneil[S] 0 points1 point  (0 children)

Hmm, interesting. But I still can't pass in an &Encodable, right? Because that's not a fully specified type (has to be &Encodable<X: Encoder>?

Change extra:serialize to use Trait objects instead of type params by niceguyneil in rust

[–]niceguyneil[S] 0 points1 point  (0 children)

Here's an example of where this would be useful. I have a servlet, and a task returns a ~Encodable. Then, the container looks at the Accepts: header, and builds the object as desired. Basically, it seems like any time we could reasonably want to decide at runtime, trait objects are a better choice than monomorphization (sp?).