Yoshiya Hinosawa

I wonder if `ansi` is a good name for it. ANSI escape code is not the only spec from [ANSI](https://en.wikipedia.org/wiki/American_National_Standards_Institute) org. What names do other langauges' standard libraries use?

> Having it be std/fmt/colors.ts makes no sense. It's widely accepted in the Deno ecosystem ( https://github.com/search?q=fmt%2Fcolors.ts+language%3ATypeScript&type=code&l=TypeScript ) and that argument ('fmt/colors is confusing') is quite new. Also this issue...

> That's probably because std/cli and std/console didn't exist before. Once we created them, std/fmt/colors looked out of place. Sounds a fair point.

I think the fix #4459 needs more support from the community to be landed.

I personally think the current state is a good compromise between what RFC encourage to do (max-age > 0) and what people believe to work (max-age >= 0). I think...

`perfomance.now()` doesn't return unix timestamp, but it returns elapsed time from some random time origin. If `FakeTime` works with `perfomance.now()` in a similar way as `Deno.now`, that feels confusing to...

> As for discouraging/encouraging the use of `performance.now()`, it really depends on what you plan on using it for. [MDN puts it best](https://developer.mozilla.org/en-US/docs/Web/API/Performance/now#performance.now_vs._date.now): > > > Also, `Date.now()` may have...

Steps needed for this migration: - Run `_tools/convert_to_workspace.ts` and commit the changes. - Start using https://github.com/denoland/bump_workspaces for upgrading versions of submodules (This happens independently from CLI release)

We plan to do this migration right after Deno CLI 1.43 release (which is scheduled on 4/24).

> We plan to do this migration right after Deno CLI 1.43 release (which is scheduled on 4/24). JSR cutover didn't happen yet because CLI 1.43 release was postponed to...