1,362 karma · joined July 16, 2017
The reasons: Writing parsing code by hand tends to be verbose, error prone (such as off by one errors), ad hoc, and full of temporary strings. Editor syntax highlighting (and also sites like regex101). Lastly regexes are matched in one go (match /no match) which is good for readability.
I do avoid making regexes long if I can.
If your brain does not get exposed to the ‘right’ set of hormones at the right time while you’re in the womb, your brain can develop a different gender identity than the rest of your body. This can be the explanation for some trans people, but I don’t know how many.
// A syntax error this is and compile it will not
Then a compiler could try to reason about the computation and decide that overflow does not happen if all values are within bounds, and just add checks at the function boundaries.
There are speculations one could make that imply a minimum size, I recall a reading a prediction of 10^50 times bigger or so.
Hahaha
https://en.wikipedia.org/wiki/Singularity_(operating_system)
1: dates close to the current date, such as flight dates, meetings, delivery dates. 2: birth dates and similar (wedding date, start of employment), often a long time ago.
For “near future” dates, date pickers are somewhat handy because you can see the day of the week, and glance the number of days compared to other dates.
For date of birth, date pickers are useless. You don’t need to pick anything, you will just know it by heart in most cases and you can type it fast enough.
Programmers like date pickers, because you can’t choose nonexistent dates, you can’t confuse day/month number, and you can’t enter ambiguous 2 digit years. And they like consistency, so the same design is used for all use cases.
Please realize that consistency != usability.