I thought about some about 360 videos and oh boy it looks hard. First of all it uses obnoxious amount of data. Oculus go for example has resolution of 2560 x 1440 (1280x1440 per eye) and horizontal fov in region of 90…
As hard as rust is in itself, it tries to lower most of the other barriers to entry for new programmers. I think that central package repository coupled with sane package manager and consistent documentation is must…
I feel the same. From my own experience, I've done both 9h-10h of productive work for few weeks in challenging projects and 8h ass-in-seat in crappy and bad managed ones.
And in emacs you can use org mode with export to pdf though latex
I follow @HNTweets on Twitter (pretty much only thing I follow) and I scroll through it every time I have a free moment that would be wasted otherwise (bus rides or long queues come to mind). I find it easier to follow…
> You can write user code in Pony that will cause a kernel panic or hardware error? You can always (as in OS with lazy allocation) allocate enough memory to get OOM no matter how safe your language is.
Don't forget dialog requesting for notifications permission because otherwise you would miss important news.
I thought about some about 360 videos and oh boy it looks hard. First of all it uses obnoxious amount of data. Oculus go for example has resolution of 2560 x 1440 (1280x1440 per eye) and horizontal fov in region of 90…
As hard as rust is in itself, it tries to lower most of the other barriers to entry for new programmers. I think that central package repository coupled with sane package manager and consistent documentation is must…
I feel the same. From my own experience, I've done both 9h-10h of productive work for few weeks in challenging projects and 8h ass-in-seat in crappy and bad managed ones.
And in emacs you can use org mode with export to pdf though latex
I follow @HNTweets on Twitter (pretty much only thing I follow) and I scroll through it every time I have a free moment that would be wasted otherwise (bus rides or long queues come to mind). I find it easier to follow…
> You can write user code in Pony that will cause a kernel panic or hardware error? You can always (as in OS with lazy allocation) allocate enough memory to get OOM no matter how safe your language is.
Don't forget dialog requesting for notifications permission because otherwise you would miss important news.