aout

8 ms·

31.
by aout 12y ago
Most of the big avenues in Paris already have separated bike lanes on either the sidewalk or the bus lane but the road (for regular cars) still takes 80% of the space. The goal here is to leave more space to pedestrians (like on the river f
32.
by aout 12y ago
Well, if you hide Karma but still use it in the ordering of the thread then Karma could be derivated. In a day you could extract the data from the posts and build a kind of karma-book with top users etc etc...
33.
by aout 12y ago
Since it's a really big, technical book here are some quick quotes I thought were useful in general: "This book is a handbook of widely applicable and heavily used design techniques, rather than a collection of optimal algorithms
34.
by aout 12y ago
True, but picking is only one pass of rendering (and a pretty fast one as you can see here: https://github.com/aout/SAGE/tree/Multipass/Sage3D/Resources... ).
35.
by aout 12y ago
Your browser is slow when applying transform to DOM elements because it has to translate everything 3D in terms of JavaScript and DOM. If you want to manipulate images and elements effectively in 3D then you have to learn matrix computation
36.
by aout 12y ago
Because you could do something easier to understand in terms of 3D for a very simple use case and find a generic use for it.
37.
by aout 12y ago
Just updated the repo with multipass rendering including picking and lights. Might interest you.
38.
by aout 12y ago
I tried the demo of course and I thought you did a great job. I'm not saying you should abandon the project because of performance issues you'll encounter but rather focus on simplicity with clear boundaries. Again, go for it! (bu
39.
by aout 12y ago
Well, your browser is already GPU-accelerated. What makes it slow is the process of making GPU-memory accessible to your JavaScript. An example of that is drawing a DIV and applying a CSS 3D Transform to it. By doing so you'll modify i
40.
by aout 12y ago
Wait wait wait... Handling textures via CG Buffers is quite fast you are right and you can basically do whatever you want in terms of image manipulation using the shaders but you'll lose efficiency as soon as you introduce complex pick
41.
by aout 12y ago
Completely true. But is it so hard to imagine a fallback instead of a rewrite / refactor? I mean, aren't you tired to develop for X renderers? Couldn't Microsoft adopt something like the Khronos group for once and stop fuckin
42.
by aout 12y ago
It is a fairly common practice in companies that do not have technical managers ( http://en.wikipedia.org/wiki/Code_coverage ). Basically it is useful to measure the coverage of existing conditions (and insure stability)
43.
by aout 12y ago
I'm not sure I fully understood the moral of the article but it seems to me that all of these findings are basically what "people knew for a long time". Okay it's good to put data on "beliefs" but is it really
44.
by aout 12y ago
Based on your speculations I'd say that the QRCode is the IP adress of the WebApp + some kind of token. Scanning it allows the phone to connect to the browser and act as a proxy to transfer messages?
45.
by aout 12y ago
I would add that Acompli isn't on the AppStore anymore so it's probably a pure rebranding of the app.
46.
by aout 13y ago
What's your opinions about a mobile first mail client that helps you connect through mail instead of What'App or Skype? What about persistant folder move if you have a clear indicator that there's something new in a folder? W
47.
Mobile Mail Client for collaboration?(theairmailproject.com)
1 points by aout 13y ago|1 comments