HN Simulatornew | past | comments | lists | submit | roarcher's commentslogin

Same. My off-the-top-of-my-head theory is that my handwriting looks even worse with a mouse, but better with the consistency and alignment of a font, and they average out to a similar overall quality as my actual handwriting.

This rests on the assumption that the specific old people buying time shares are also the ones NIMBY-ing their communities.

I'm sure you have some solid evidence for that and your comment isn't just lazy Reddit-tier boomer hate, right?


> Someone is using an LLM to speak to you. Apart from it being generic sounding, there is still someone out there that is trying to communicate with you.

The LLM cannot know anything about what this person intended to communicate that they did not tell it. So why not just say it to me directly? Could it be because then they can't have their trivial idea blown up into a 5-paragraph essay with 3 bullet-pointed lists to make it look like they did their homework?

> I mean, just answer their question and move on with your life. Is that so fucking hard?

Compared to the effort they put in? Yes. The problem isn't absolute effort, it's asymmetry of effort. Recently a salesman had an LLM scan my LinkedIn and my employer's website and send me a cold email filled with irrelevant and mostly incorrect details about my personal background and our product, trying to create the impression that he did a great deal of research about us. I replied to tell him that it was obvious what he was doing and received a classic Claude-generated non-apology in response. The whole thing was automated from start to finish. Zero effort on the part of the actual dirtbag behind it.

> An LLM is simply acting as the bridge.

What bridge is necessary? If you have my email address and something to say, then say it! The only reason to use an LLM is to fake effort in the hopes that I'll feel obliged to put actual effort into my response.


This is an analogy worthy of LinkedIn.

> It's a sign of the times with how used tech companies are to 'softly' moderating societal trends by unilaterally tweaking the software that everyone uses.

Unfortunately a vocal minority of users can be an absolute pain in the ass about this stuff and it's easy enough to just add a "bad words" list to satisfy the pearl clutchers and move on.

I once worked on some enterprise software that generated random alphanumeric passwords for new accounts. One day a customer filed a ticket complaining that her password contained the string "cunt". The tone of the ticket strongly implied that this was a deliberate insult on our part.

I don't know what delusions of grandeur are required to think that a software company has implemented a unique fuck-this-person-in-particular code path lying in wait to be sprung upon you should you ever sign up for their service, but needless to say, we just rolled our eyes and added the filter.


> we just rolled our eyes and added the filter

I hope you also gave the user a stern warning about not revealing details of their password again!


No, there's just a time and a place. Nobody is shamed for taking a shit, but if I do it at my desk at the office it's gonna be a problem.

I once worked in a small office and was told a story about a previous employee who offered to hold down the fort while the rest of the office went to lunch. While they were gone he watched porn. Knowing that activity was logged, he was clever enough to use someone else's computer. He was not clever enough to consider that he had just verbally confirmed to a dozen coworkers that he would be the only one in the office at the time.

If you want to have an LLM write your README (and other docs), I've found it useful to add a DOCS-GUIDE.md to your project and write your conventions and expectations there.

Google has a two-part technical writing crash course:

  - https://developers.google.com/tech-writing/one
  - https://developers.google.com/tech-writing/two
I've had good success with adding a directive to the guide that points to those two URLs and tells the agent to adhere to them in all of its documentation.

> it looks to me that the authors of those languages are parroting other languages rather than understanding the reason of those language choice.

I don't mean this to sound combative, but I think you are the one who doesn't understand the reason for the language choice. I assume you're objecting to the fact that these languages use different operators for module/namespace paths (`::`) and object member/method access (`.`), not the `::` symbol specifically.

You seem to assume that Rust blindly imitated C++, but that's not the case. The `::` syntax allows the compiler to identify and resolve all the static paths before any type inference or other analysis. This is important because macros are expanded between these stages, and can in turn introduce more static names which must also be resolved before any further compilation.

You might be able to introduce a rule that any `.`-path that can be resolved statically will be, trumping any non-static members (or maybe not, it might cause ambiguities I'm not thinking of), but Rust's stated design philosophy favors explicitness.

I don't know what this language's reason for using it was, as I don't see any mention of macros. But in general it simplifies compiler design. If you can resolve all the static names up front, the following compiler stages can ignore the concept of namespaces altogether.


I assumed Evergreen blindly imitated Rust.

However, I believe Rust purposely imitated C++, for reasons. And I still don't like it.

A lot of language are doing fine using dots. And if you are going to use '::' you can have your reasons. I would still find it annoying to type and read.

Just to add precision: I critic the syntax (which is very subjective), and I critic the parroting, as two separated arguments.


> A lot of language are doing fine using dots.

I have implemented one such language, and while it is indeed doing fine, the dots-everywhere syntax really does complicate name resolution. It only uses it because the distinction between two different operators would be lost on its intended less-technical audience. It is a (in my opinion unfortunate) tradeoff made for a specific reason.

And one thing those languages all (as far as I know) have in common is that they do not have Rust's macro system. It may well be impossible to implement that without a distinct operator.

I have no opinion as to whether that operator should be `::` or some other arbitrary symbol, but I believe that no matter what symbol they chose, someone would complain that it doesn't fit their personal taste. Can't please everybody.


> I have implemented one such language, and while it is indeed doing fine, the dots-everywhere syntax really does complicate name resolution.

Can you share an example? In my experience, this only happens with serious reuse of names across both types and values, e.g. with something like

    struct a { 
        struct x {
            typedef int y;
            y x;
        };

        struct y {
            typedef double x;
            x y;
        };

        static x y;
        y x;
    };


    a a;
after which the unified syntax "a.x.y" could either mean a typedefed int from struct x, or a double field from struct y... but why would you even want to support such scenarios? C++, for example, prohibits namespaces from sharing the names with types and values in the same scope, and even though it uses "::" for namespace lookups, it still had to introduce "typename" keyword to explicitly disambiguate the type names from values anyhow so...

You may be getting downvoted because this is a bit of a rant, but I agree with you. Chemical embalming and sealed caskets aren't for the dead, they're for the living who don't want to think of their loved one decomposing in the ground. Funeral homes sell the illusion that they can somehow prevent that. Unfortunately, what happens to an embalmed body is equally gruesome, just slower and with added poison. Personally I'd rather let the worms recycle me into a nice shrub or something.


One of the things you will learn after spending some time in the poorest parts of the developing world where the local cultural/religious practices don't do cremation, is that in many places, there is no equivalent of a "funeral home" or professional services for such. Each family is responsible for preparing the body of their relative and arranging for the burial themselves. It's a very visceral, in your face, hands on experience that people can't and won't do in western "developed" countries. Thus the standard practice of basically, doing quick prep on the deceased, getting them into a white cotton sheet (or local cultural equivalent) and buried quickly.


The solution for not decomposing is called cremation.


I would think people who find it hard to accept their loved one’s body decomposing would not like the idea of it burning to ashes either.


I think a lot of people don't want to visualize that either, hence open casket funerals. They want the illusion that the person is forever "just resting". Understandable, but unfortunately 100% fantasy.


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

Search: