3 ms·

You always have to start somewhere. Do you want to code all the OS from the ground up, or do you have minimal expectations about the environment your software w

You always have to start somewhere. Do you want to code all the OS from the ground up, or do you have minimal expectations about the environment your software will run on? Do you want to look at all the tiny details, or do you wish to focus on a specific aspect of the problem? The article author could also give an explanation of linear algebra, but I guess he expects the reader to be familiar with this part of the problem. I guess that there's always a software layer which may be considered "backbone". For people designing networks, all the tedious work of building the network is just plumbing, and they probably expect it to be automated from a formal description of the network.

FartyMcFarter 8y ago
> I guess that there's always a software layer which may be considered "backbone". The point is that you don't need any software layers at all to code up a basic neural network implementation. A programming language with basic floating-point operations is all you need. The algorithms are not complicated so even x86 Assembly is practical for this purpose if you're already experienced with it. So the "backbone" can simply be your favorite compiler. > Do you want to code all the OS from the ground up If it's a "make your OS" course then yes - a simple OS of course. If you want to become experienced in compilers, then writing a compiler from scratch for a simple language is mandatory for people who want to have solid fundamentals. It's not a coincidence that projects like these are common in Computer Science and Software Engineering courses.
- MrUnderBridje 8y ago
  > The point is that you don't need any software layers at all to code up a basic neural network implementation. I grafted my answer to the wrong post, I meant to respond to the guy talking about the project implicitely using Numpy. Offtopic remark: It would be nice to be able to move a post to a different thread, or make a single answer to several messages.
  - mos_basik 8y ago
    >single answer to several messages Always surprises me that out of all the different kinds of internet communities, it's only the oft-maligned imageboards that consistently provide that feature. I was kind of expecting Discourse to play with the idea, since they seem to be the modern-reboot-of-forums with the most traction + willingness to experiment, but they haven't so far, afaik.
    - spicytunacone 8y ago
      How would you represent that? On HN and similar every response is its own thread. This is true with email as well, but I don't have experience with any significant threads or mailing lists. The naïve solution would be to just limit nesting and order nested comments chronologically. Another solution may be to CC @postid in your messages and have posts display "responding to: id1, id4" at the top and "responses: id91" at the bottom with appropriate links. There's a question here about which post to write or display your response under. Finally, an extravagant solution would be to really represent discussion as a graph and I think a lot of time would need to be spent creating an interface with minimal frustration as I feel it can get really involved (i.e., a lot of clicking). Curious what you or anyone else thinks.

FartyMcFarter 8y ago

> I guess that there's always a software layer which may be considered "backbone". The point is that you don't need any software layers at all to code up a basic neural network implementation. A programming language with basic floating-point operations is all you need. The algorithms are not complicated so even x86 Assembly is practical for this purpose if you're already experienced with it. So the "backbone" can simply be your favorite compiler. > Do you want to code all the OS from the ground up If it's a "make your OS" course then yes - a simple OS of course. If you want to become experienced in compilers, then writing a compiler from scratch for a simple language is mandatory for people who want to have solid fundamentals. It's not a coincidence that projects like these are common in Computer Science and Software Engineering courses.

MrUnderBridje 8y ago
> The point is that you don't need any software layers at all to code up a basic neural network implementation. I grafted my answer to the wrong post, I meant to respond to the guy talking about the project implicitely using Numpy. Offtopic remark: It would be nice to be able to move a post to a different thread, or make a single answer to several messages.
- mos_basik 8y ago
  >single answer to several messages Always surprises me that out of all the different kinds of internet communities, it's only the oft-maligned imageboards that consistently provide that feature. I was kind of expecting Discourse to play with the idea, since they seem to be the modern-reboot-of-forums with the most traction + willingness to experiment, but they haven't so far, afaik.
  - spicytunacone 8y ago
    How would you represent that? On HN and similar every response is its own thread. This is true with email as well, but I don't have experience with any significant threads or mailing lists. The naïve solution would be to just limit nesting and order nested comments chronologically. Another solution may be to CC @postid in your messages and have posts display "responding to: id1, id4" at the top and "responses: id91" at the bottom with appropriate links. There's a question here about which post to write or display your response under. Finally, an extravagant solution would be to really represent discussion as a graph and I think a lot of time would need to be spent creating an interface with minimal frustration as I feel it can get really involved (i.e., a lot of clicking). Curious what you or anyone else thinks.