the RIIR fallacy, again
> Nobody forces beginners to write macros. Beginners are only macros _users_. With time and experience, the need for macros emerges by itself, then learning them is a natural part of the process. But even then, nobody…
Is it by any chance that it will work with docker-nividia? I.e. support accessing the host's GPU insider the nested containers?
first of all, I don't think "most inappropriate languages for frontend development" is a thing, it is just a new way to do web dev that is different to what you used to be doing with. If you don't think it is an…
it is a very useful project and just done at the right balanced - simplicity and self-contained. But, I use an android phone :(
Stavros thanks for the explanation, how does TileDB avoid downloading the entire matrix and do the slicing (locally)? Are we achieving this by breaking down a big matrix to a set of smaller ones? so that you only down…
the RIIR fallacy, again
> Nobody forces beginners to write macros. Beginners are only macros _users_. With time and experience, the need for macros emerges by itself, then learning them is a natural part of the process. But even then, nobody…
Is it by any chance that it will work with docker-nividia? I.e. support accessing the host's GPU insider the nested containers?
first of all, I don't think "most inappropriate languages for frontend development" is a thing, it is just a new way to do web dev that is different to what you used to be doing with. If you don't think it is an…
it is a very useful project and just done at the right balanced - simplicity and self-contained. But, I use an android phone :(
Stavros thanks for the explanation, how does TileDB avoid downloading the entire matrix and do the slicing (locally)? Are we achieving this by breaking down a big matrix to a set of smaller ones? so that you only down…