Hacker Newsnew | past | comments | ask | show | jobs | submit | brson's commentslogin

The TigerBeetle database docs have a page on financial accounting that is just a really good overview of double-entry accounting.


Rust was specifically designed to be refactorable and in my experience it is. It was part of the dogfooding process of building Rust in Rust - lots of changes to the language, lots of changes to the compiler, lots of churn. Rust's strong type system means you can refactor and be confident that programs continue to work.


To the students and mentors: congrats. GSoC is a great program and a great way to get involved in the industry. I hope you had an amazing experience.

Not to take away from them, but the first sentence of this official Rust post kinda stunned me: "the Rust Project participated in Google Summer of Code (GSoC) for the first time this year". There may be an interpretation of this sentence that is true, but multiple students have worked on Rust GSoC projects under Mozilla (which at the time ran the Rust Project), and quite a few worked on Rust GSoC projects under other organizations.

At the least, Michael Woerister worked on debuginfo in 2013, and Igor Matuszewski on the RLS in 2017. [1] [2]

Please Rust Project do better at remembering your history.

[1]: https://blog.gerv.net/2013/06/gsoc-2013-project-list/

[2]: https://summerofcode.withgoogle.com/archive/2017/projects/52...


it’s impressive how high-impact these projects were!


I use this daily instead of python3 as a simple calculator via the repl, and for that purpose it is indistinguishable from python.


Having so many students involved in Rust was huge. Definitely the most rewarding thing about working on Rust was seeing students get involved, grow, then turn that experience into a career, while seeding the industry with Rust talent.


Yes, but it goes both ways. As a student, I was always thrilled to see bits of future technology today.

I am still sad that some of the things I've seen or have taken part in didn't materialize and haven't taken a hold in the present.

The students you had were certainly as happy as being with you as you were having them. :-)


Rust was explicitly designed from the beginning for creating maintainable large-scale software.

Here's the original elevator pitch from 2010:

https://github.com/rust-lang/rust/blob/d6b7c96c3eb29b9244ece...

Note the text about "programming in the large".


There are. Here is a copy of my notes on the subject:

https://gist.github.com/brson/9422a92791062ac52d9e08f0ba7d48...

Sorry it's not more organized and detailed.


Another recent big user is 1password, both on the Windows desktop and in the browser with wasm. Great notes!


Reddit also uses commonmark, plus some GitHub flavored markdown extensions, via the comrak library, plus some custom extensions. So Reddit markdown should mostly look like GitHub.


Reddit seems to use two different Markdown engines. I use old.reddit.com, and I've noticed that some users that use new Reddit post code in ``` blocks. That doesn't work on old Reddit where you need to put four spaces in front of every line for it to render as code, so it just looks messy. I'm guessing their WYSIWYG editor uses the ``` version.


I only use old reddit and can post/view ```code blocks``` without issue.


I went looking for some examples and found these two. The first [0] is someone that tried to post a ``` block, but it's not rendering properly on old Reddit. It does render ok as a code block on new Reddit in a private window.

The second [1] is somebody that posted a ``` block but also indented all lines with four spaces. That renders as a code block with ``` lines before and after it on old Reddit, and as extra indented code on new Reddit.

If you use RES you can look at the raw Markdown code for each comment using the source link.

Maybe you´re thinking of inline code which use a single ` before and after the code content?

Screenshots: https://imgur.com/a/TKSKoEB

[0] https://www.reddit.com/r/cpp/comments/e16s1m/what_is_wrong_w...

[1] https://www.reddit.com/r/cpp/comments/e0fdp3/simple_timer_fo...


You're correct, I was thinking of `inline code`.

The old Reddit formatting wiki page doesn't mention ``` now I look, there's a note on new Reddit about sticking to spaces for compatability: https://www.reddit.com/wiki/markdown Would be nice if they fixed it indeed.


That version of Rust also did async I/O in the runtime. Async I/O has always been part of Rust. The model changed because there was too much overhead doing it the more ergonomic way and it got booted out of the runtime.


Yep, this is a great point.

Someday, we should get a book about the history of Rust together...


I didn’t know about this.. I’d love to read that book :)


Just remembering this deck and thought it might be interesting to this audience. This is the very first public documentation about Rust (Servo is not actually defined in this deck...), Graydon's slides from the Mozilla Summit 2010, dated 2010/07/07.

As far as I can tell, beyond this talk, there wasn't a formal "announcement" about Rust's initial open-sourcing (if somebody knows otherwise please link). It was mentioned the next day on LtU: http://lambda-the-ultimate.org/node/4009


Can you add (2010) to the title please?


I don't think so. I don't see anything to click that would let me do that, but I'm happy to do so if someone tells me how.


If you are the user that posted the story, you can see an edit link in the listing of stories. (For a limited time after posting.)


Users can't edit titles; mods can. If this had hit the front page, they probably would have done it for you.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: