Yeah, being awoken by an alarm in pure darkness is grim which, longitude 15 solar noon minutes west of where our timezone is set and at our latitude is very possible in winter.
With pure standard time we would never have sunset before 5 pm but daylight savings puts half the year's 7 am before the sun has risen, and if you are an early riser as I have become, before the dawn breaks.
It also gives us four months where it's very hard to get children to sleep after 8 pm and for me it's even hard to start winding down.
I think summer time is really non-optimal for most purposes, changing the clocks sucks, and most individuals that work do so for too many hours a day. It's a local maximum in terms of how we socially manage time and people mistake optimising our society towards it to be optimising towards a global maximum.
Imagine if there was no DST and someone said "let's change every clock...", I would think it's a classic XY problem.
Yeah, it’s interesting how the desktop metaphor evolved over time but increasing display size and the ability to have multiple workspaces surely is a huge part of what makes tiling almost work.
And tiling still largely doesn't work with small windows.
And every argument I hear from the pro DST group is really just an argument for ending adult work at 15.30 rather than 17.00 and maintaining a 9.00 start time.
It blows my mind that we are all meant to wrap our lives around bullshit jobs.
I remember going into my networking unit and absolutely destroying it through the use of the command line. Everyone else was clicking through the wireshark GUI and I just grepped every answer. Finished the hour long practical assessment in about 15 minutes having run everything twice.
CLI is so valuable because rather than explore a presentation of the data you plan your RE etc and then run it and it either returns the answer or it doesn't.
There are some TUIs I quite like (LNAV as a pager) but I think if you really know what you're dealing with the CLI is better almost every time.
There's a layer above that, when CLI and bash and sed and tshark are becoming too hairy or slow, and it's 'just' parsing the pcap frames in your language of productivity. Over the years I've built layer over layer of optimized Java code to parse and analyze pcap/pcapng files with either visitor patterns or active iterations (and multi-pass analyses through indexation, or just interfacing with duckdb for months-long-capture analysis to surface low signal-to-noise-ratio events). It builds a good understanding of all the layers and brings the power of a full-featured workbench (language, IDE, libraries, visualization options...).
Built it in Java, and rebuilt it in Ada, and Rust. I find it's a good exercise to learn about a programming language... bonus point, once I have a parser, plugging it live behind libpcap, dpdk, xdp, or just raw sockets is easy.
however, ~99.8% of 18 year old students have never used any command line tool in their lives. they do not know what grep is. they can navigate a gui because they have used a gui all of their life.
when im teaching networking for example, using a gui means i only need to teach one thing (networking), where if i use a cli i have to teach two things (cli + networking)
>I think if you really know what you're dealing with the CLI is better almost every time
to be clear, i was not making an argument that gui is better in general.
i am speaking as someone who teaches introductory networking courses at a 1st-year college level. no one i teach "really knows" what they are dealing with because it is the first time they are learning about it.
With pure standard time we would never have sunset before 5 pm but daylight savings puts half the year's 7 am before the sun has risen, and if you are an early riser as I have become, before the dawn breaks.
It also gives us four months where it's very hard to get children to sleep after 8 pm and for me it's even hard to start winding down.
I think summer time is really non-optimal for most purposes, changing the clocks sucks, and most individuals that work do so for too many hours a day. It's a local maximum in terms of how we socially manage time and people mistake optimising our society towards it to be optimising towards a global maximum.
Imagine if there was no DST and someone said "let's change every clock...", I would think it's a classic XY problem.
reply