That's just asinine. Just because any user would like fast navigation doesn't mean privacy only matters if you know what a violation it is to ping every server in sight on user's device, with absolutely no way to prevent it.
No, but the choice of name exudes a certain arrogance that aligns with the authors of MuJoCo. It's a very capable and robust engine, but the authors have been very condescending of other technologies and confusing the terms gaming with game.
It certainly won't replace PhysX as they are designed for comparatively small scale simulations, however with instancing. For instance, MuJoCo doesn't have real broadphase that scales with large environments, but sticks with the old tried-and-true SAP. Neither does it have separate friction coefficients for slip, tying it into robotics, except maybe for the VDB solver.
You should be aware that Microsoft's idea of open source is very much at odds with everything open source before Microsoft boldly slapped a "Microsft <3 open source" right and left.
They may have progressed beyond Ms-PL, but they have tried to coup and steal open source projects several times.
But, altho understandable, the simple fact that their primary products, Visual Studio, Office, Windows, and even worse: former versions of any of these, are simply not open source in any way precisely contradicts the expression of loving open source.
While I mostly agree, I will say they're leaps and bounds better than a couple decades ago. Windows now accounts for less than 10% of MS revenue, and definitely lacks in attention by all indications. Linux on Azure outweighs their Windows use by an increasingly wider margine, and a significant amount of the progress that has occurred on Windows has been to make Linux development easier.
.Net and a lot of other tooling and projects are on Github under BSD licensing, and that's pretty cool... almost everything they do outside Windows/Office works in Linux these days. I do think they should at LEAST get a version of office (offline) that works in Linux... even if it's a bastardized web version that runs in Electron.
Aside: I couldn't say how much I appreciate the work Valve has done to improve gaming on Linux, and have no expectations of ever moving back to Windows. MS seems to want to extract literally every cent of value out of every Windows user, and it sickens me.
I think you are right. Looking at the source code of the page there are the usual tell-tale signs of AI written code with overtly explaining comments, such as:
<!-- Favicons -->
<!-- Bootstrap CSS with Replit dark theme -->
<!-- Custom CSS -->
<!-- Bootstrap JavaScript Bundle -->
<!-- Custom JavaScript -->
I thought the point of a sliding window, especially a fixed one, is to add the next element and subtract the oldest one from a running sum, to achieve O(1) running time except the start cost. This is what an efficient constant-time median filter in image processing would do, such as Perreault and Hébert's Median Filtering in Constant Time, and Weiss' Fast Median and Bilateral Filtering do.
Edit: I can't see the visualizer explaining this part.
Thanks for the feedback. I can't speak to the image processing references, as I'm still learning, but I will check them out and see if they make sense in the app.
Regarding the purpose of the sliding window, you are correct for commutative operations in fixed windows, like maintaining a sum where each operation is O(1). When you're talking about min/max, median, and other operations where adding or removing would not be constant time, as with a priority queue or heap.
Can you elaborate on which aspects you felt are missing from the visualizer?
This reply looks like classic and corteous AI when contradicted, and proves it haven't read nor understood the references, which clearly indicate how to achieve O(1) for min, max and median, even with greater dynamic range than 8-bit, and also clearly show how lacking the visualization is.
Historically the .NET and XNA vector types have been seriously lacking for real graphics development, and they still don't even provide swizzling. It's likely that this project predates .NET numerics by many years, and anyone who has had a pet project for long enough will learn to avoid becoming too dependent on libraries and platforms that will die out.
reply