One of the main reasons I shoot with an actual camera body is exactly because it has a camera body. The ergonomics of shooting with a phone are terrible.

Obviously phones will never fit in your hand like that, so both will continue to exist because they serve different purposes. I am glad that phone sensors are getting bigger since when you don't have your camera on you they do a fine job (when you avoid the in-cam processing by shooting raw)

> One of the main reasons I shoot with an actual camera body is exactly because it has a camera body. The ergonomics of shooting with a phone are terrible.

For me it's that and the conscious decision to get a camera ready and take it along for the ride.

I'm not sure if it makes senses, but to me that's an attitude shift in how I take photos.

For what its worth, the volume up button is the shutter button too which helps sometimes. It used to work with wired headphones too.

For video I much prefer iPhone with a gimbal though. And the gimbal, with its built in stick and tracking, makes me much more creative for stills than I am with my traditional cameras.

Both pale in comparison to the creativity I feel with a 360 camera though. Image quality ain’t everything.

You can get a grip accessory that makes it feel more ergonomic.

go doesn't have null safety or adts though? (sum types)

I think you can have null safety in Go and you certainly can have adts.

But even then, what about Ada?

I’m also not an expert, but I assume between C#/Typescript/haskell/swift that you can find all those things in many GC/safer languages.

Go does not have compile-time null safety or sum types :)

    foo := Foo{"hello"}
    fooPointer := &foo
    fooPointer = nil
    fmt.Println(fooPointer.Bar)
    > panic: runtime error: invalid memory address or nil pointer dereference

In a language like Kotlin a compile time error would prevent `fooPointer.Bar`, and in Rust `nil` does not exist. Go also does not have sum types, see for instance https://making.pusher.com/alternatives-to-sum-types-in-go/

Yes, Ada. Maybe. I will have to look at it.

The rest all are missing basic things. Like, I love TS, but it's absolutely bonkers because js is js. I once worked on a 250k loc project of js/ts, and we had nothing but trouble

indeed you should use your hips instead of head/shoulders to weight the board, but it doesn't actually move more weight to the back (think about it, to go forward, the board needs to feel more weight on the front, for which it compensates by accelerating = increase speed + levels the board)

the weight distribution doesn't change, but your body had much more control over the distribution.

That's a better way to put it. I tend to phrase it like I do because ideally your natural reaction should always be to lean back on the one wheel which for me in position ends up feeling like I'm standing one footed and pushing down with the other.

Steering with your backfoot takes some getting used to if you've never board sported before. I've not snowboarded but I've been told it's like that?

Also skid plates are a life saver. You're going to have to do a drag stop at some point, might as well do it on a something easily removable.

That’s interesting. I’ve spent years snowboarding, used to skate as a kid, little bit of surfing, and they all have transferable skills. The thing that I found so different about the OW is the LACK of rear foot push since you only have a single contact point with the ground. Like other person said, I move hips to control speed, squat to turn heel-side, but I don’t feel like the foot control is anything like board sports that have more contact with ground/snow/water. Maybe I do it subconsciously with super tight turns for trails but not with flow and carving.

Did you replace your rear pad and/or? I put one of those like... skateboard style ones on the back, might be changing what I'm doing to steer/the feel of it. Board control is for sure different. The only conscious change I made to my riding style was intentionally keeping my hips further back. It's also been about a year since I sold mine so I might be misremembering.

No, I haven’t changed my footpads, haven’t even sent out for my GT recall pad, yet, which I need to do. Do you like the new pad in terms of control? Got link?

Not too familiar with C++, but what is "what people write c++ nowadays" that deals with this?

what is your take on caffeine consumption?

can you give an example of where typescript fails to protect you against nulls in your own code? (apart from the use of any

You can turn off strictNullChecks, and there's also noUncheckedIndexAccess which unfortunately isn't enabled by default even in strict mode. You can also introduce flaws via @ts-ignore, casting, etc.

Still, typescript equips you to catch these errors, even if you can technically circumvent it. In practice it can be nearly bullet-proof if you follow good practices.

Aside from explicitly turning off null safety and tricky use of casting, an easy example is interfacing with JS.

If you're using either a library that wasn't written in pure TS (maybe JS or JS with .d.ts) or interacting with some unconverted JS from your own codebase, you can easily pass a null through entirely by accident. The problem really stems from the JS end of things, but 9 times out of 10 you're going to be touching JS at _some_ level when using TS so I think it's fair to point out this gap.

Abusable things:

- !

- as x

- @ts-ignore

Im not sure I understand. Did your nvidia card not work on mojave? What were you gaining not being on mojave?

It doesn't work correctly, no. Apple stopped allowing signed Nvidia drivers starting with Mohave and the drivers from Apple for the device are buggy and cause issues.

Maybe the driver issues you experience are resolved in more recent macOS versions. I run macOS 10.14.6 on a Mid 2014 MacBook Pro with GeForce GT 750M. No issues here.

possibly... I don't actually use my laptop, and when I did my hardware refresh a couple months ago, I went linux from my older hackintosh (nvidia gtx 1080)