I have a 4 year old, in my mid 40s, and think about this a lot for some reason.
In the 70s during the summer, when I was around 7, we would wake up, eat breakfast, go out and about wherever we wanted, come back for lunch, out again, come back for dinner, and then out again past dark to play flashlight tag.
I think I would be charged with child endangerment these days if my kid (3 years in the future) was doing stuff like that. And frankly, I think I've been conditioned to think that I would be a negligent parent if I did this.
The media is part of the problem. 24/7 news, social media, and channels like ID (real life murder 24/7) scare the bejeezus out of people. But besides that, we have an acceptance of nanny-state government - that the government should be a much closer "partner" in child rearing than 40 years ago.
I always say, there's a consequence for everything, including seemingly innocuous laws to protect people.
But as a parent of a 4-year old in 2017 (and a 7 year old in 2020), I know I would be gnashing my teeth if my kid was roaming the streets and woods all day long...even if I did it.
I've had a couple 27" 1440p monitors since those cheap Korean (QNX and the like) came on the market a few years ago.
The natural upgrade path for me would be to ditch those and get a big-ass 5k monitor eventually, but I don't see the market really moving in that direction in an affordable way.
One 4k isn't going to cut it and I'm worried two 4k monitors is going to be to much from a field of vision perspective....maybe I'm wrong there.
Has anybody upgraded from a couple 1440p monitors to a couple 4k monitors, and what's your experience been?
I'm the last person to talk about type theory, but on the max function example:
fn max(comptime T: type, a: T, b: T) -> T {
if (a > b) a else b
}
fn letsTryToPassARuntimeType(condition: bool) {
const result = max(
if (condition) f32 else u64,
1234,
5678);
}
Then we get this result from the compiler:
./test.zig:6:9: error: unable to evaluate constant expression
if (condition) f32 else u64,
^
Couldn't the compiler infer some kind of union type. You don't know the type at runtime, but f32 or u64 is a legit comparision type.
I like what I'm seeing, but a suggesting regarding shortened keywords. Just go ahead and change compTime to compileTime. I don't see 3 extra characters saving much and makes it less readable. Most modern editors will autocomplete anyway.