10 ms·

Take a look at the code if you haven't: https://github.com/fogleman/nes/tree/master/nes https://github.com/fogleman/nes/tree/master/nes I don't know if it's a

by sfeng 12y ago

Take a look at the code if you haven't: https://github.com/fogleman/nes/tree/master/nes https://github.com/fogleman/nes/tree/master/nes I don't know if it's a statement about fogleman or Go, but it seems so much more clean than other emulators I've looked at.

jmgrosen 12y ago
See also sprocketnes, an NES emulator written in Rust: https://github.com/pcwalton/sprocketnes https://github.com/pcwalton/sprocketnes It was written by pcwalton, one of the main driving forces behind Rust. (Unfortunately, it hasn't been updated for a couple months, so it won't build with latest rust).
- kibwen 12y ago
  NES emulators are a common and fun challenge for testing out languages. Here's one in Clojure that intends to be fully immutable, such that you can rewind and fast-forward through history at will: https://github.com/samfoo/clones https://github.com/samfoo/clones In the case of Sprocketnes, one of its goals is to serve as a demonstration of Rust's ability to run entirely without a runtime (see the long-outdated quote in the readme: "The Rust garbage collector is not used in this project"... we really need to get this updated for 1.0).
  - MetaCosm 12y ago
    Woah, that is a really cool idea. The idea of walkable state is neat... even if 1 FPS.
- MetaCosm 12y ago
  > It was written by pcwalton, one of the main driving forces behind Rust. (Unfortunately, it hasn't been updated for a couple months, so it won't build with latest rust). Possibly the most telling sentence I have ever read about Rust. I am (well more honestly, was) excited by the language but until there is some sort of stability guarantee, it is a fun toy, a distraction. The Rust community appears desperate to have continuous improvement at the core language level, and despite some hand-waving, it feels like they simply won't be pinned down. I will watch it with interested post the May 15th 1.0 deadline -- but since they shipped entirely new Path and IO in Feb -- added new language constructs and removed others (Alpha2)... I am worried...
  - pcwalton 12y ago
    > Possibly the most telling sentence I have ever read about Rust. I am (well more honestly, was) excited by the language but until there is some sort of stability guarantee, it is a fun toy, a distraction. > The Rust community appears desperate to have continuous improvement at the core language level, and despite some hand-waving, it feels like they simply won't be pinned down. What is the impending 1.0 release if not that? We've been very clear all along that 1.0 means language stability. I see no "hand-waving". > I will watch it with interested post the May 15th 1.0 deadline -- but since they shipped entirely new Path and IO in Feb -- added new language constructs and removed others (Alpha2)... I am worried... Why would you be worried that we're following precisely the schedule that we said we would?
    - MetaCosm 12y ago
      I was vague and unclear, entirely my fault. I really want Rust to be successful, I just think some of the decisions being made are shortsighted, so I will watch after release to see if I am correct, hope I am not. > What is the impending 1.0 release if not that? We've been very clear all along that 1.0 means language stability. I see no "hand-waving". I guess I don't consider "stability" and "backwards compatibility" the same thing -- in the "stability as a deliverable" post, it was specifically referenced that rust will "continue to evolve at a rapid pace and even accelerate!" (quoted from memory, sure it is somewhat off). I think a constantly growing language (no longer changing cause old code has to work, but growing... which seems worse) and the fact that libraries will opt into new features and bundle use of those features with bug fixes will mean that the entire userbase is on a 6 week upgrade cycle -- 8 or 9 upgrades a year. I consider that a mistake. Furthermore, I consider the idea that the channels will not fracture the community to be very naive. I expect a lot of libraries will just live on unstable and tell users to "come with them". > Why would you be worried that we're following precisely the schedule that we said we would? You are correct and that was unfair. I can't fault the team for doing what they said -- even if to an outsider it seems like an insanely late time to be doing these types of refactoring.
      - kibwen 12y ago
- 4ydx 12y ago
  The last time I checked this is a link about go? Or no?
shurcooL 12y ago
If I may be so bolt to plug my tool, but would http://gotools.org/github.com/fogleman/nes/nes http://gotools.org/github.com/fogleman/nes/nes be a nicer way to look at the source of the entire Go package?
- shurcooL 12y ago
  *bold, sorry about the typo.
- hahainternet 12y ago
  Line numbers should be linkable in the same way as a filename is. Perhaps they should be foldable.
  - shurcooL 12y ago
    Thanks for the suggestion. That's an opened issue [1] and the highest priority for the project. [1] https://github.com/shurcooL/gtdo/issues/11 https://github.com/shurcooL/gtdo/issues/11
- oneeyedpigeon 12y ago
  If you must force a target on links to other packages, can you at least use a static name (rather than _blank) so the same package doesn't keep opening in different tabs? E.g. <a href="/errors" target="errors">"errors"</a>
  - shurcooL 12y ago
    Thanks for the suggestion. I've opened https://github.com/shurcooL/gtdo/issues/33 https://github.com/shurcooL/gtdo/issues/33.
- fogleman 12y ago
  Looks pretty good.
  - gillianseed 12y ago

by sfeng 12y ago

jmgrosen 12y ago

See also sprocketnes, an NES emulator written in Rust: https://github.com/pcwalton/sprocketnes https://github.com/pcwalton/sprocketnes It was written by pcwalton, one of the main driving forces behind Rust. (Unfortunately, it hasn't been updated for a couple months, so it won't build with latest rust).

kibwen 12y ago
NES emulators are a common and fun challenge for testing out languages. Here's one in Clojure that intends to be fully immutable, such that you can rewind and fast-forward through history at will: https://github.com/samfoo/clones https://github.com/samfoo/clones In the case of Sprocketnes, one of its goals is to serve as a demonstration of Rust's ability to run entirely without a runtime (see the long-outdated quote in the readme: "The Rust garbage collector is not used in this project"... we really need to get this updated for 1.0).
- MetaCosm 12y ago
  Woah, that is a really cool idea. The idea of walkable state is neat... even if 1 FPS.
MetaCosm 12y ago
> It was written by pcwalton, one of the main driving forces behind Rust. (Unfortunately, it hasn't been updated for a couple months, so it won't build with latest rust). Possibly the most telling sentence I have ever read about Rust. I am (well more honestly, was) excited by the language but until there is some sort of stability guarantee, it is a fun toy, a distraction. The Rust community appears desperate to have continuous improvement at the core language level, and despite some hand-waving, it feels like they simply won't be pinned down. I will watch it with interested post the May 15th 1.0 deadline -- but since they shipped entirely new Path and IO in Feb -- added new language constructs and removed others (Alpha2)... I am worried...
- pcwalton 12y ago
  > Possibly the most telling sentence I have ever read about Rust. I am (well more honestly, was) excited by the language but until there is some sort of stability guarantee, it is a fun toy, a distraction. > The Rust community appears desperate to have continuous improvement at the core language level, and despite some hand-waving, it feels like they simply won't be pinned down. What is the impending 1.0 release if not that? We've been very clear all along that 1.0 means language stability. I see no "hand-waving". > I will watch it with interested post the May 15th 1.0 deadline -- but since they shipped entirely new Path and IO in Feb -- added new language constructs and removed others (Alpha2)... I am worried... Why would you be worried that we're following precisely the schedule that we said we would?
  - MetaCosm 12y ago
    I was vague and unclear, entirely my fault. I really want Rust to be successful, I just think some of the decisions being made are shortsighted, so I will watch after release to see if I am correct, hope I am not. > What is the impending 1.0 release if not that? We've been very clear all along that 1.0 means language stability. I see no "hand-waving". I guess I don't consider "stability" and "backwards compatibility" the same thing -- in the "stability as a deliverable" post, it was specifically referenced that rust will "continue to evolve at a rapid pace and even accelerate!" (quoted from memory, sure it is somewhat off). I think a constantly growing language (no longer changing cause old code has to work, but growing... which seems worse) and the fact that libraries will opt into new features and bundle use of those features with bug fixes will mean that the entire userbase is on a 6 week upgrade cycle -- 8 or 9 upgrades a year. I consider that a mistake. Furthermore, I consider the idea that the channels will not fracture the community to be very naive. I expect a lot of libraries will just live on unstable and tell users to "come with them". > Why would you be worried that we're following precisely the schedule that we said we would? You are correct and that was unfair. I can't fault the team for doing what they said -- even if to an outsider it seems like an insanely late time to be doing these types of refactoring.
    - kibwen 12y ago
4ydx 12y ago
The last time I checked this is a link about go? Or no?

shurcooL 12y ago

If I may be so bolt to plug my tool, but would http://gotools.org/github.com/fogleman/nes/nes http://gotools.org/github.com/fogleman/nes/nes be a nicer way to look at the source of the entire Go package?

shurcooL 12y ago
*bold, sorry about the typo.
hahainternet 12y ago
Line numbers should be linkable in the same way as a filename is. Perhaps they should be foldable.
- shurcooL 12y ago
  Thanks for the suggestion. That's an opened issue [1] and the highest priority for the project. [1] https://github.com/shurcooL/gtdo/issues/11 https://github.com/shurcooL/gtdo/issues/11
oneeyedpigeon 12y ago
If you must force a target on links to other packages, can you at least use a static name (rather than _blank) so the same package doesn't keep opening in different tabs? E.g. <a href="/errors" target="errors">"errors"</a>
- shurcooL 12y ago
  Thanks for the suggestion. I've opened https://github.com/shurcooL/gtdo/issues/33 https://github.com/shurcooL/gtdo/issues/33.
fogleman 12y ago
Looks pretty good.
- gillianseed 12y ago