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

Same here. I quickly learned that if you merely ask questions about it's understanding or plans, it starts looking for alternatives because my questioning is interpreted as rejection or criticism, rather than just taking the question at face value. So I often (not always) have to caveat questions like that too. It's really been like that since before Claude Code or Codex even rolled around.

It's just strange because that's a very human behavior and although this learns from humans, it isn't, so it would be nice if it just acted more robotic in this sense.


Yeah, numerous times I've replied to a comment online, to add supporting context, and it's been interpreted as a retort. So now I prefix them with 'Yeah, '.

Very interesting observation. Wondering if anyone ever analyzed the underlying "culture" of LLMs and what this would mean for international users.

Obviously you want AI to do your job, so you should accept the result and not coauthor it.

The reason is the system prompt they provided. They probably added a clause like “plan user’s requirements… and implement the required code”

We're training neutral networks on human content to be human like. We don't have "robotic content"

Do what you would do with a person, which is to allocate time for them to produce documentation, and be specific about it.

I've only written a handful of production projects in Go so my experience isn't very deep, but I find the syntax to be the ugliest of any PL. The mixed capitalizing based on function privacy, to me, is awful (among other things, i.e. personally I loathe curly brace initialization/definition). I'm sure you get used to it? It doesn't help that it just feels very hacked together, from the wonky generics, the lack of useful types like tuples and enums, the bolted on module system, to the annoying error handling, to say the least.

That said, compile times are great, the concurrency is dead simple, it's performant, and it's still easy to be really productive in it so it's not like I'd never consider it. Many other languages have many of the same issues, anyway.


> The mixed capitalizing based on function privacy, to me, is awful

Awful compared to ... what? `private` and `public` keywords? Ugly hacks like pythons `_` and `__`?

> it just feels very hacked together

> the wonky generics

What exactly about the generics is "wonky"? "Wonky" is not a term defined in any programming textbook I ever read. And languages are not designed on feelings, especially when the design goal is to be as pragmatic as possible, as is the case in Go.

> the lack of useful types like tuples and enums,

Need a tuple? Use an array and don't change it.

  - [2]string: string 2-tuple
  - [5]int: int 5-tuple
  - [1]any: empty-interface 1-tuple
And btw. 99% of the time tuples are used, it's as a stand-in for multiple-returns. E.g. Python does that. Go simply has...multiple returns.

> and enums,

Outside of language-enthusiasm with matching and whatnot (which more often than not is used because it looks cool rather than being useful), the most common (and again, 99%) use of enums, is to give names to magic values. Go has that covered:

    type Color string
    const (
      RED Color = iota
      GREEN
      BLUE
    )
> the bolted on module system

Pray tell what exactly is "bolted on" about modules? They are simply an extension of the import system, nothing more, nothing less.

> the annoying error handling

The "annoying" thing about it is that it's explicit and forced. Both of which are positives as far as I'm concerned, because I AM FREKKIN DONE with shitty 10-mile stacktraces because some joksters library threw an "exception" 400 layers down in some sub-sub-sub-sub transient dependency lib.


I definitely prefer public private over case defined visibility.

You can't use an array for different types.

Matching _is_ useful, no one uses matching just because it looks "cool".

You can have explicit forced AND exhaustive error handling without exceptions. Go actually lacks this.


> I definitely prefer public private over case defined visibility.

And I think `public` and `private` keywords are a verbose mess that adds nothing to a language.

> You can't use an array for different types.

Yes I can. I even provided an example for exactly that: `[4]any` can hold references to any type.

> Matching _is_ useful

A lot of things are useful, doesn't mean they are used for that useful case most of the time.

> You can have explicit forced AND exhaustive error handling without exceptions

Go has wrapped and typed errors, covering exactly that.


> Yes I can. I even provided an example for exactly that: `[4]any` can hold references to any type.

And now you've lost type checking. `(&'static str, bool, u64, f64)` is not the same as `[4]any`.

> A lot of things are useful, doesn't mean they are used for that useful case most of the time.

I'm sure you have vast insights into what most people do most of the time.

> Go has wrapped and typed errors, covering exactly that.

Sure, "Go has X because it gives you the tools to reimplement it yourself another way" is true of most anything you can think of.


Zed is the only editor I've been using for maybe two months or so. But I find the extensions still sorely lacking and the API not extensive enough yet either. Still, I really love the design as well as how AI was builtin, and some more of the niche differences.


Anecdotally, my cats meow at me a lot. But they're my cats (others live in the house and help care for them). I also meow back more than anyone else. In fact, I might be the only one to do so. :)


I used to meow back to my cat when he was younger for vocal modulation and pitch practice (lots of minor seconds and perfect fourths). This might have been a mistake as he's now very talkative, particularly when I'm on the phone.


Anything to avoid stricter gun legislation. This type of incident will be considered an unfortunate but necessary sacrifice despite how dystopian it really is.


How do you pay with PayPal if not putting in your credit card or bank details? link is a pretty well-known online wallet and much simpler to use than PayPal.


I've never heard of link, so it's the difference between a random website and a well established brand. Not that hard to understand why someone might be hesitant to put in their cc details.



It's $16k for a 1-person household. Here's the rest:

$21,150 (2), $26,650 (3), $32,150 (4), $37,650 (5), $43,150 (6), $48,650 (7), $54,150 (8)

Also the median household income in NM is ~$62,000 according to the Census, which is already under the 400% threshold for just a one person household.

https://www.healthcare.gov/glossary/federal-poverty-level-fp... https://data.census.gov/profile/New_Mexico?g=040XX00US35


Working with one of those right now, on my two-person team, ironically.


I am on a team of 2 people with a dedicated manager. That is, the manager does not write code and is not even really technical.

It is awful, send help.


I had no idea what Arrow is: https://arrow.apache.org or arrow-rs: https://github.com/apache/arrow-rs


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

Search: