Simon

Great, thanks a lot @rohitvarkey. Here are some more thoughts: The old struggle how to layout your vertexarray will become a lot simpler. We can just use the format the...

That's exactly the idea here... The mesh examples are a bit confusing, since they don't actually use StructsOfArrays... They should actually look like this: ``` Julia SOA(Vertex, rand(Vec3f0, 10), rand(Vec3f0,...

Ah yeah, that's what I wanted to address as well. The example for why it would be convenient to have different units per vector was the one of plotting data...

> The animation problem troubles me too, but what you describe is already a problem, right? Yes, but now it's harder for me to cheat around this... Which is sort...

> using differently 'warped' time progressions can be informative That should map down to the ability to animate the parameters of time, which should be easily feasible. > Yes, I...

Yes! Would be great to have them here. Right now I'm pretty tight with time, but in the long term I want to do everything possible to create a unified,...

@ysimillides > and then individual packages can overload this function with their specific FEM structures? I created this issue specifically to discuss how to make this overloading easier ;) Because,...

I see, thanks for the clarification. Sounds like a bigger project though. CGAL seems to be interesting as well!

> VoronoiDelaunay.jl is faster than current alternatives, it will support distributed execution That's exciting and really proves the point, that a high-level language helps to make code fast, even though...

> I suggest we create a "Computational Geometry with Julia" organization in Github much like the Julia Webstack, Julia Optimization, or Julia Astro and develop all relevant projects there I...