Bank of America Unlimited Cash Rewards for the win :) My only regret is not realizing sooner that it existed since I used the Citi Double Cash card for so long.
>“I have autism” is a better statement than “I’m autistic” because autism doesn’t define me.
If that sort of thing is useful for you, go for it, but I'm also leery of these attempts to redefine language when they involve larger campaigns. Most people don't consider "I'm X" to define them when it comes to other concepts and honestly it seems like it could be helpful to consider such things are part of your identity. I'm black/autistic/diabetic/etc puts in a larger community. It doesn't define who you are overall, but does give you some sense that one of your attributes is shared with others.
I reviewed a CL from Hyrum at Google where he was trying to remove a `set_timeout(float)` method in favor of `set_timeout(absl::Duration)` and changed the former to delegate to the latter. It turned out that there was some special handling of inf/nan in the legacy API, despite no mention in the documentation, and his CL broke a number of tests. It was amusing to experience Hyrum's law so directly :)
Something else to consider is compile time versus runtime validation with formatting libraries, e.g. due to passing the wrong number or type of arguments. The Abseil str_format library does compile time validation for both when possible: https://abseil.io/docs/cpp/guides/format
{fmt} certainly does this too. It works quite nicely with the clangd language server flagging a line as an error until the format string and arguments match.
But isn't that what the "lifecycle" target date funds do? The argument is that you will know the schedule you want to rebalance on for your custom personal needs, better than the generic target-date "lifecycle" fund will?
Sorry, I didn't check comments for a while. The target date funds tend to have higher management fees and yes, worse composition of stocks versus bonds compared to holding a mix yourself, IMO, based on your goals.
- God/faith in the first line of profile
- credit score
- homeowner status
- have a job/career
- vaccine status
- political party (and demands for the partner’s party affiliation)
- FlatEartherism and other outlier conspiracy theories
- the “three sixes club”
- Dan Savage’s “GGG”
The C API for Julia also has almost no documentation. There is a getting started guide, which is great, but if you want to do anything more advanced (e.g. creating structs like in your example), you'll end up reading the source code to try to puzzle through which functions to use in julia.h. There's also an apparent limitation that whichever thread initializes Julia is the only one that can later eval code, which was surprising. The language itself is very cool, but it has a long way to go to be easy to embed like Python is.
The good news is that you don't need the C api nearly as much because you don't have to call out to C whenever you want performance. Also, the extent to which the python C api is documented has actually been a major problem for them since it has effectively frozen a ton of python's implementation in majorly detrimental ways (eg the GIL)
Calling out to c "because you want performance" is only only one dimension of the issue, and assumes that your main application code is written in python or julia. In many cases (e.g., robotics), application code is written in c++ or c, and python bindings serve as simulation harnesses and visualization tools. Pybind11 is absolutely brilliant for this. The last time I looked, similar tooling for Julia was substantially less mature and definitely didn't look like something I'd want integrated into a production workflow.
