Timeline for Question closed due to "lack of research"
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 30, 2020 at 23:05 | history | edited | Ramhound | CC BY-SA 4.0 |
Improved formatting; corrected spelling; fixed grammar; improved formatting; corrected spelling; fixed grammar; improved formatting; corrected spelling; fixed grammar
|
| Jun 30, 2020 at 22:56 | comment | added | Hashim Aziz | ...but I assumed there would at least be enough Bash experts. I have made a slight edit to the question to make it clearer what I'm after, but aside from that I cannot see how the question can be improved any further without changing the focus of it. If it still fails to be re-opened I'll probably just ask it and any similar questions in the future on SO or even U&L since it's clear SU only selectively keeps these kinds of questions around (and as ever, unclear on what basis it chooses to do so). | |
| Jun 30, 2020 at 22:55 | comment | added | Hashim Aziz |
If you're referring to the "references" to how to run time, I've already stated why including benchmarks isn't a solve for my question and would only help to narrow it down unnecessarily. My question doesn't mention the use of Cygwin because it's an unnecessary detail. There are lots of things that could affect bad benchmarks, reliable benchmarking to determine an objective speed across systems is hard. You might be right about SU not being home to enough programmers, something I had a hunch about myself before asking the question...
|
|
| Jun 30, 2020 at 22:05 | history | answered | Ramhound | CC BY-SA 4.0 |