We maintain a fork of LTP internally. Eventually we hope to contribute our changes back but unfortunately open sourcing isn't free and we have bigger fish to fry[1].
Out of curiosity, is progress on WSL bound by any blocking issues in particular, or could your team benefit from more resources being assigned to the project?
Maybe I'm naïve, but I tend to view WSL as a perfect way to win over a ton of developers who are becoming disillusioned with macOS, but are hesitant to run bare metal Linux due to the headaches involved (insofar that macOS and Windows "just work").
Not OP, but I'm genuinely interested in how this experience is. What do you think of it compared to using, say, iTerm2 on OSX? I've been thinking of switching back to a Windows PC since I haven't been very impressed by OSX in the last couple of years.
I've been using it since it's release to the fast insider ring and at work since it's release to the slow insider ring. It does everything I need to do. Build C++ with GCC or clang. ssh client works fine (have not tried ssh server, but supposedly supported). Python, Perl work fine. Have had some UI issues with the console, but those have been fixed on the fast ring.
The team behind WSL is also very responsive to issues reported at github.
A) VS code supports WSL in the newer versions of Windows Insider Builds.[1] Support for individual IDEs is now available [2] but will take time for individual IDEs to implement.
B) This is something that we are actively looking at but it is not an easy problem and will take time.[3]
Thanks for the work you're doing, it's pretty exciting! I hope MSFT remains committed to this project.
A) This is only a terminal, which isn't really more useful than opening a WSL window, I want to be able to debug python easily. I don't really know how the python debugging protocol works, so I'm not sure if stdin/out is enough, but even if it is enough there's some glue code missing to make this trivial, I need to have a binary that can take the same arguments as python and translate windows paths to WSL paths. And then the Python VS code tools also have some pretty cool Jupyter/IPython integration; I'm not sure that will just work with an executable that pretends to be python. Would be cool if the people working on VS code bits were thinking about WSL, rather than users having to come up with individual hacks.
2) Cool, I assumed backlog meant "not going to happen", will be great if it gets anywhere. Though I'm also interested in OpenGL for graphics; I wanted to run OpenAI's gym project, but that needed OpenGL for rendering. Not necessarily expecting you to write an X server, but would be cool if you could cooperate with or fund a project like Xming or https://github.com/kpocza/LoWe or something.
Corporate answer: big, hairy proprietary algorithms. Startup answer: straight magic, yo. Real answer: manual for this week. We're doing a couple things that don't scale to validate a concept.
Total occupancy but larger spaces can be segmented however they might want (order line, dining, bathrooms, bar area, etc.) Just need to separate two sections with a sensor.
1 sensor... ingress = movement into one area out of an adjacent area. Simultaneously, that counts as an egress (that person having moved out of that adjacent area into the next).
