Threads for teymour


    LaTeX is a wonderful piece of software, but it’s often quite temperamental and the error messages are very cryptic (to me at least).

    It gets worse when trying to convert LaTeX documents to HTML:

    1. 2

      Spaced repetition is really interesting, and there’s probably room for innovation in this space. What about using ML to generate “distractor” answers for multiple choice questions? Or social features so you can see how hard a question is for other users? Or VR so you can assign facts to physical locations in a “room” to make them easier to remember? There are only a few pieces of software in this space, and they’re all pretty old at this point so they don’t have these kinds of features.

      1. 3

        Or VR so you can assign facts to physical locations in a “room”

        A VR Memory Palace! Yes! Although apparently that technique is more specifically for recalling things in sequence, like the points of a speech or the plot of a story.

        A voice interface to this software could be great too. Being able to say “Hey Cicero, I want to remember that the German word for ‘apple’ is ‘apfel’” or having Cicero randomly wake up and ask you questions during the day.

        1. 1

          There’s definitely room for innovation in all these spaces, but (and maybe this is just a personal preference) I find that I like the the simplicity of current approaches. e.g. with Anki I’ve found that it can be used on old and/or resource constrained devices (which VR question generation might not be able to).

          About multiple choice questions, I can’t remember exactly where the paper is, but I did see one suggesting that in order of effectiveness free recall was better than multiple choice which was better than close deletions which in term were better than merely being shown the answer periodically.

        1. 14

          This reads like a puff piece. It’s an interesting project but I wouldn’t say there was a real takeaway except that you have YC funding now.

          1. 11

            Ouch; this is very unconstructive criticism.

            1. 4

              I liked the article as an experience report - you can build something Erlang-ish in Rust on wasm and end up at least convincing yourself (and YC?) that it works. I agree that the article doesn’t have a strong central thesis, but I found it interesting.

            2. 11

              Sadly I believe you’re correct, especially given the post history here.

              For folks that quibble with this dismissal as a “puff piece”: for me at least if this post had any code at all showing how the APIs changed, how this mirrored GenServers or other BEAM idioms, how various approaches like the mentioned channels approach changed the shape of could, or anything like that I wouldn’t be so dismissive. Alas, it seems like a growth-hacking attempt with lots of buzzwords (I mean christ, look at the tags here).

              Marketing spam and bad actors still exist folks.

              1. 2

                Hi friendlysock, I do mention in the post “Check out the release notes for code examples”. Here is a direct link to them:

                1. 6

                  From (successful) personal experience: you can get away with promoting your stuff if you offer people something of real value in exchange for taking their time & attention. Nobody cares what’s in your GitHub: make content that is on the page you are posting that is worth reading.

                  1. 5

                    Friend, your only contributions to this site have been entirely self-promotion for your Lunatic project. It’s a neat project, but you are breaking decorum and exhibiting poor manners by using us in a fashion indistinguishable from a growth hacker. Please stop.

                    1. 1

                      I don’t think it’s fair to call a blog that has 3 posts in 2 years “marketing spam”. This submission is currently #1, so it’s obviously of interest to the community. But with this backlash in the comments I’m definitely going to refrain from posting in the future.

                      1. 19

                        I don’t think it’s fair to call a blog that has 3 posts in 2 years “marketing spam”.

                        In one year, as I write this comment, you have:

                        • Submitted 3 stories, all self promotion.
                        • Made 5 comments, all on stories that you submitted, promoting your own project.

                        That is not engaging with this community, that is using the community for self promotion, which is actively contrary to the community norms, and has been the reason for a ban from the site in the past.

                        This submission is currently #1, so it’s obviously of interest to the community.

                        The rankings are based on the number of votes, comments, and clicks. At the moment, all of the comments in this article are either by you, or are complaining about the submission. This will elevate the post but not in a good way.

                        But with this backlash in the comments I’m definitely going to refrain from posting in the future.

                        I would say that you have two choices:

                        1. Stop posting altogether.
                        2. Engage with the community, comment on other stories, submit things that are not just your own work.

                        The general rule of thumb that I’ve seen advocated here is that posts of your own things should make up no more than 10% of your total contributions to the site. At the moment, for you, they are 100%. If they were under 50%, you’d probably see a lot fewer claims that you were abusing for self promotion.

                        1. 4

                          I don’t know how to resolve the problem that this is both an interesting project but only being posted by you, and that there’s a business wrapped around it, where you’re the ‘CEO’ - which just makes it a bit awkward when people are interested in the tech but opposed to ‘spam’.

                          I’m certainly interested in following the project, so I’d prefer that you keep posting!

                1. 3

                  The title greatly undersells it. :)

                  1. 2


                  1. 28

                    This article convinced me that Rust is overhyped.

                    But I also don’t owe it to you to cater to your delicate sensitivities and apologize for every other excited person who also writes about Rust.

                    And we don’t owe it to you to cater to your delicate sensitives and not say “wow you’re kinda creepy and arrogant about this Rust thing.”

                    Most of all, I’m not going to stop advocating for something I believe will materially improve the industry (and my job satisfaction).

                    I strongly advocate for something I believe will materially improve the industry (formal methods), but I work hard to do it in a way that’s not obnoxious. You can be enthusiastic without being a jerk!

                    1. 18

                      The aggressive, everyone-else-is-an-idiot tone of a lot of Rust advocacy is a big turnoff to me, personally. Obviously there are jerks in every community, but this communication style seems much more common among Rust advocates than among advocates of most other popular languages.

                      The language itself has interesting ideas. I still might choose Rust if I were working on a project involving a lot of concurrent access to mutable state. But I sure wouldn’t do it for the joy of becoming part of that community.

                      1. 7

                        It’s unfortunate, really, and one of the reasons it’s pretty far down my “would be cool to learn” list.

                        1. 7

                          As someone very interested in learning Rust, the community is actually one of the positives for me. I’ve never seen the attitudes you’re talking about, in fact the impression I have had is that the Rust community is very welcoming, friendly, and motivated. Far more commonly I see the opposite, where people somehow manage to be offended by someone’s genuine enthusiasm about the language and go out of their way to take them down a peg. It’s quite petty. That’s what I read from the article/rant and I agree with it, it’s something that has been bothering me even as someone outside the Rust community. If someone wants to make a point that their project is ‘written in Rust’, then what is it to you? Often it’s just one remark within a larger article but half the comments just zero in on it. If I get tired of anything, it’s that. It’s become more of a meme to point that out every time than the statement itself.

                          1. 6

                            This is the motte-and-bailey of Rust evangelism. Once you’re part of the community, it is all puppies and sunshine…but there is silence or outright denial about how the annoying the missionaries are if you have not seen the light.

                            (We had some similar things with Node back in the day, and Java–though the author of the article didn’t mention it–was heavily shiller by Sun marketing and what these days we would call developer evangelists.)

                            The Rust evangelion strike force has given the community a bad rep, and if you want to draw a historical analog look at the minority of obnoxious Ruby and Rails devs back in the day that made everybody think it was a community solely of brogrammers.

                          2. 4

                            but this communication style seems much more common among Rust advocates

                            It saddens me to see that you believe that. My experience with the people working on rust is that they’re very open about other languages and the shortcomings that exist in rust.

                            I would like to believe that the loud minority you can read here would do that with any language they can use to make such bold claims. (We’ve had this previously with people here ranting on “everything that’s not C”.) So based on my experience with people writing rust code in production I would ask you to ignore posts like this and make your own picture of it. And then come back and tell us what annoyed you about it, we can’t enforce the CoC on some persons blog post, but we can do so in the community channels and on github.

                            Another problem that I’ve seen is that for every post pro rust there is one contra, some in the dismissive style we can read here (you don’t have a spec?, where is my GUI framework ?, do you know about django?, this will never mage it big, you’re just too bad to write good c). If you want some arguments against rust I’d invite you to r/rustjerk, where we can ironically make fun of the duality of rust coders, libraries and other related languages ;)

                            1. 1

                              The more I think about it, the more I can see how similar this is to people arguing against & for vaccination and how I’ve lately seen very aggressive attitudes on each side.

                            2. 2

                              I think the “everyone-else-is-an-idiot” is actually a group of people (many of whom have worked on the codebases they are talking about – e.g. Firefox and their attempts to build concurrent browsers) stating empirical evidence on previous software projects and their shortcomings and then talk about how they feel Rust reduces these failings.

                          1. 2

                            Erlang really is a fantastic piece of engineering.