For a game I'm making, I have a helper function that takes in a specified time (as a float) and returns a (heap based) wait instruction. The times are literals sprinkled throughout the code base of callers of this function, so I maintain a cache of time -> wait instruction to reduce allocations.
Wouldn't your life be much simplier if you'd represented time as integer milliseconds? I totally get it being too late now, but I think that's an argument for making floats a little bit unpleasant to start working with.
In that case and in some others it doesn’t, but in general it does:
https://stackoverflow.com/questions/17661428/async-stay-on-t...
Probably it makes sense to say that async await can try to use a continuation passing style or run on a different thread because there is no actual guarantee that it will use one or the other.
"Today, Scott Guthrie, Microsoft's executive vice president of the cloud and enterprise group, said in an interview, "it's about half now, but it varies on the day because a lot of these workloads are elastic, but sometimes slightly over half of Azure VMs are Linux." Microsoft later clarified, "about half Azure VMs are Linux.""
I think they meant majority of azure clients (i.e., people running vms on azure) running linux, not that azure itself runs on linux. Linux was above 40% sometime last year in azure stats, and I think it crossed 50% sometime recently.
While it's great that you've never had one rejected, what would happen if that event occurred? Imagine a situation where you submit a proposal for a completely unrelated project, that you really want to happen, and they deny it? Further conversations, talks, they don't budge. What then?
Anecdotal counterpoint: I develop java and python at work, C# and C++ at home, use / have used Eclipse, IntelliJ, ST + plugins, vim, Visual Studio Code, and Visual Studio for development. Of all of the above, I've found that Visual Studio is by far the most pleasant to work in environment (for C# and C++), hands down.
Arguably, the most important place for clean code is everywhere, but the largest use-case for it is in projects that are expected to live, or in places that the code is seen / used by people who are not the original developer(s).
If your goal is to "ship it and forget it", great. Do whatever you need. Outsource it to some other country if it's cheaper, who cares? You're not going to be maintaining it anyway. Does this make something good? No. Is it excusable? Maybe.
