felixguendling

If you optimize one criterion, it's simple: lowest is best or highest is best. If you optimize multiple criteria, all optimal trade offs between any of the selected criteria are "best" in some way.

I guess we only find out if some people order those chips and check if there is some data. From my understanding the idea is the same like maps showing air planes or ships (for ships it’s AIS). So without volunteers/pioneers who participate we won’t know. It seems like traffic lights and trams also can send data.

It's based on Car2X/Vehicle2X data that's sent unencrypted and can be received with chips you can order from China.

Have you tried MOTIS with only the geocoding enabled? This should be 1-2 orders of magnitude smaller.

Would you recommend this as a "thread pool" / coroutine scheduler replacement for an application web server?

Thanks! Maintainer of MOTIS here. We're planning to bring support for NeTEx, SIRI and OJP to MOTIS and with those formats a lot of features that are only available with those formats but not with GTFS(-RT) (yet). But having them implemented will also help us to quickly activate them for GTFS(-RT) once GTFS(-RT) gains support.

Just found this and couldn't find anything about it but it looks interesting. Does anyone have experience with it? Seems like a competitor to CUDA from AMD and Intel?

Regarding the size I would guess that if htmz would be extended to have the same features as htmx, it would also be similar in size? Would it make sense to modularize htmx in order to only pay for what you really use to support adding features without necessarily increasing the downloaded size?