16 ms·

This is a really interesting point of view... i don't think that there is a VALID possibility to determine always matching example projects, neither i think, a

This is a really interesting point of view... i don't think that there is a VALID possibility to determine always matching example projects, neither i think, a COMPILER should collect statistical data over time (what, if i lose this data?), but i like the approach. Perhaps it should be a tool, that can be executed on git repositories for existing projects and plot a compile time graph to identify fishy commits... sounds interesting though.

tracker1 7y ago
Man, I sometimes feel old seeing these kinds of complaints... and I do appreciate it. When I start certain kinds of projects with an interactive build/rebuild the first pass is S-L-O-W but interactive changes are instant (ie: node/webpack). In rust for a hello world rocket app (just learning rust), it's 0.17s for debug build, 0.18s for production. I have no real frame of reference other than OMG it's so tiny (executable and running in-memory). I'm also starting to work with ARM/Pi devices so Rust is making a lot more sense for that space.