This looks like the old logo died, laying in a pool of blood. I would like to imagine that they may be subtly acknowledging the end, or at least the art director is.
livingcoder
But my freedom...
I had to look it up and it looks like you're right. If only my teacher had spent any effort at all explaining that.
When the car is at a stop is when he is most vulnerable. He must fight everyone, right there, until the car starts moving again.
I had a similar experience with square roots, writing both the positive and negative answers. It's wild for a teacher to actively reject correct answers because "that's not what we learned today" (the negative answers, in my case).
# Copy pwd into clipboard using pbcopy
alias cpwd="pwd | tr -d '\n' | pbcopy && echo 'pwd copied into clipboard'"
# grep search the current directory
function lg() {
ls -alt | grep $1
}
The main one that jumped out to me was a scroll issue on iOS when using multiple fingers. I just looked it up to share a link and it may be fixed? It's the mentality of "Eh, we might fix it one day" that is the bulk of why I didn't stick with Flutter. A bug this annoying lingering for as long as it did said volumes to me.
Possibly fixed: https://9to5google.com/2023/12/28/google-fixes-flutter-infamous-scrolling-bug/
I wanted to get into Flutter but it seems like there are some bugs that are either unfixable or that they have actively decided not to fix. I didn't want to end up wasting my time building on such a foundation, but it's definitely nice for certain projects that fit within the supported functionality.
Can anyone explain what this means to me like I'm 5?
Cast Away. Tom Hanks.
It's a movie that starts really goofy, gets serious for a long time, and is then oddly goofy again.
This was a good blog post. I have started using approach #3 as well for just about every situation where I was originally planning on just using a enum type by itself. Inevitably I end up needing to apply shared state to all of my enums (create date, parent table ID, etc.) and this approach has really worked out very well. You can also add some convenience functions for returning if the kind is one of the variants (ex:
IsKeywordSearch
) to make if-statements easier to read (and a match on the type enum is overly verbose when you don't need the properties contained within the enum itself).