abstreet VS min-sized-rust

Super awesome! I like how you just color roads to show time. When you calculate polygons to try and cover the whole area in some 5-10 minute bucket, you can wind up with all sorts of odd holes far away from roads. Keep it simple.

https://github.com/a-b-street/abstreet/pull/1075

A|B Street does some of that, but it is not a game: https://github.com/a-b-street/abstreet

You can build it out in a cool simulator and show it off.

The tool you want exists, but you'll need to actually build the city in it. It's really an incredible program!

Active Travel England | Software Developers and Data Engineer | Full or Part Time | https://www.gov.uk/government/organisations/active-travel-en...

Active Travel England will be developing tools to support evidence-based investment and policies to support sustainable transport. We're hiring 3 roles at present (there will be more jobs in January): https://www.civilservicejobs.service.gov.uk/csr/index.cgi?SI...

We are already working with the transport simulation and scenario development tool A/B Street and the Low Traffic Neighbourhood design tool: https://a-b-street.github.io/docs/ and plan to create new web applications to transform active travel infrastructure design, monitoring and evaluation.

An exciting thing about these jobs from a software engineering perspective is that you will be starting with a relatively blank slate. In the UK we already have tools like https://bikedata.cyclestreets.net and https://www.pct.bike/ but need to go further than this. Long term, the 7 strong Data and Digital team that you will be part of will develop a comprehensive map based design support tool to provide data of the type in BikeData (and more datasets), drawing tools, and automated assessment of proposed interventions.

These opportunities will enable you to shape the future of tools for active travel investment and policy in England and, because the software develop as part of these roles will be open source, beyond.

These high profile jobs will have a large impact, see here for context: https://twitter.com/Chris_Boardman/status/159648662743800217...

I don't know the topic well enough to be sure, but isn't this what you're looking for: https://github.com/a-b-street/abstreet

https://github.com/a-b-street/abstreet - project to plan, simulate, and communicate visions for making cities friendlier to people walking, biking, and taking public transit.

This is a good guide on building small Rust binaries: https://github.com/johnthagen/min-sized-rust

This talks about going to extreme lengths on making the smallest Rust binary possible, 400 bytes when it was written, https://darkcoding.net/software/a-very-small-rust-binary-ind...

The thing is, you lose a lot of nice features when you do this, like panic unwinding, debug symbols, stdlib… for kernel and some embedded development it’s definitely important, but for most use cases, does it matter?

Oh it was 137, haha. I will link you to this older comment of mine: https://news.ycombinator.com/item?id=29408906

See also https://github.com/johnthagen/min-sized-rust

Are you sure? If so then this is awesome news, but I'm a bit confused; the commit in that min-sized-rust repo adding `build-std` to the README was merged in August 2021: https://github.com/johnthagen/min-sized-rust/pull/30

Are you saying that at that point the feature still hadn't "landed in Rust nightly" until recently? If so then what's the difference between a feature just being available in Rust nightly, vs having "landed"?

Rust binaries are by default nowhere close to 500MB. If they are not small enough for you, you can try https://github.com/johnthagen/min-sized-rust. By avoiding the formatting machinery and using `panic_immediate_abort` you can get about the size of C binaries.

A useful reference: https://github.com/johnthagen/min-sized-rust

That must be without stripping. Also there are ways to reduce binary size. See e.g. [min-sized-rust](https://github.com/johnthagen/min-sized-rust). I've gotten stripped binaries of small cli utils less than 400KiB without doing anything special, less than 150 KiB by customizing profile settings and compressing with upx, and less than 30 KiB by replacing the std with the libc as the link shows. Haven't tried with fltk though...

This is not quite what you're asking, but it does also address the underlying concern: https://github.com/johnthagen/min-sized-rust