Thanks Craig. It's a bit crushing.

Thank you!

Thank you! 🙏🏻💙

Don't suppose you've got a lead on a role? 🤞🏻

I can't speak on her behalf 🤷🏻‍♂️

I haven’t, but mostly because it’s not worth paying for when I can just slap the hands of my team enough times that they learn XD

There’s a lint rule that requires all variables have a type, which I’d _love_ to use… but it’s a bit too aggressive. (For example, if I’m using bloc, `on<MyEvent>((event, emit) {})` would become `on<MyEvent>((MyBlocEvent event, Emitter emit) {})`, which is unnecessarily verbose.)

I don’t think dot shorthands provides _me_ any benefits. Sure, it may be less code to _write_, but when I’m trying to _read_ the code, it actively works against me.

I spend a good chunk of my time _reading_ code (e.g., PRs)… so anything that slows me down there should be actively discouraged.

But that depends on context, of course. That need not always apply.

I very much hate that. I have no idea what type will be produced. Also, depending on where that's defined, it would run on every rebuild.

```
late final MyType myVal;

@override
void initState() {
super.initState();
myVal = fn();
}
```

I hate it when I have to review code that doesn't have the type next to it. You set a variable and then perform some action on it later? Ok, cool... But when I'm reviewing your code, how can I contextualize it without having my IDE evaluate it?

Also 1000% agree with the linting.

Let me know if you get the camera working

And it's still an inferior game

I would absolutely put Linux on my surface book if there were drivers for all devices

Seems like you should follow the @f4mi.bsky.social lifestyle

I'll be your first 👍🏻. Just need to find time to build an app around it.

Kinda jealous