I feel you. I've been using en-dash in my writing for decades, but finding myself removing them now for fear of being mistaken for an LLM. (They tend to use em-dash, but I don't think people are going to distinguish between – and —.)
Do you think pre-AI writing is going to become really valuable because it is free of any AI assistance? If we all start using AI to assist in writing, then pre-AI writing may become important, similar to pre-atomic steel (i.e., https://en.wikipedia.org/wiki/Low-background_steel)
>Do you think pre-AI writing is going to become really valuable because it is free of any AI assistance?
Serious question: Do you think old pictures are valuable because they are free of photoshop? Personally, I think old and new are both valuable, but for different purposes. Technology gave us new capabilities with new hope
Not the user you asked, but: Yes, it seems obvious that old pictures are valuable because they are free of photoshop. Not that this means that they are free of manipulation though, c.f. the famous picture of stalin at the river with/out his fellows.
I predict in the future a humans.txt for each site that indicates the level of human authorship and for fully human authored content to be highly valuable
It's already important, for various reasons. E.g. I love older electronics books where they explain things in a very thorough manner (maybe because they had more time?). But of course reading older books is full of traps, in some subjects you need to be more careful than when analyzing the output of an LLM.
That is what I mourn the most. They were my punctuation get-out-of-jail free card.
I didn’t love them enough to figure out how to type them without doing two dash’s in Word and then backspacing out of one and hitting space again — but damnit, I miss it.
Before the LLM craze I didn't even know — was specifically different than just -, and I used it in the same way. But now I notice specifically when people use either, and when people use -- instead.
I would think to most people, (myself included!), it's just a 'dash'. A sentence was written with a dash - you could just ingest and read past it, like a comma.
Not saying this is accurate usage, maybe just real world usage.
I would hope most people can distinguish between the really short dash and the longer forms, even if they don't know any of the rules around them. But n versus m I don't expect people to notice.
I’m not sure I’m representative of “most people” in this respect (I have always used both n and m dashes), but I personally find the difference between n and m dashes bigger and more noticeable than the difference between regular and n dashes.
Because most people are ESL and really don't care.
I didn't even know there are multiple types of dashes.
I did know about multiple types of quotes because they kept breaking code on blogs. Still didn't care, but at least I learned how to spot and fix them.
Really looking forward to having the wrong kind of dash in code, but at least with current tech that seems like it won't happen.
Why wouldn't they. Never studied them. Never even thought twice about the dashes in a sentence. Didn't realize they were different till like a few months ago when everybody suddenly started focusing on how "AI" it makes everything look
Ton of fun! Was interesting to see how my strategy evolved as well. I started out trying to make a large pen, but quickly realized that wouldn't work, so I made a small pen and then started moving it out. This allowed me to see individual optimizations and try alternatives. Even at the end, about to hit submit, I wasn't sure my solution was optimal, but ended up with the optimal sizse-86 solution for today's challenge. Will try again tomorrow!
I'm not so sure. Both Go and Rust seem like examples of very popular ecosystems with a set of common, "blessed" tooling. (They didn't have everything from the get-go, e.g. rust-analyzer was very popular before it became part of the Rust project, but it still demonstrates that a large ecosystem can rally around a set of common tooling.)
That's a fair point, but I don't think it's really fair to say Gleam has everything necessary included when it's brand new. Because it currently doesn't suffer from the problems of the JS ecosystem doesn't mean it won't in the future.
(As another example besides rust-analyzer, there's also all the Go dependency management tools that existed before native Go modules, e.g. Dep, Glide, Go Package Manager, etc.)
As someone who has contributed to a language server, I've wanted a language/editor agnostic way to interact with it, primarily for the purposes of black-box testing. I wonder if this could be useful for that?
What's the process for adding support for a new language?
I can see now how that line can give the wrong impression. My unit is very dear to me, to the point where I call it by name like any other housemate. It's always "honey, I'll give Bob a go at these dishes". I guess I was expecting constructive discourse on HN without having to dodge knee-jerk comments at every step.
I think someone demonstrated in the announcement thread that, adjusting for inflation, the Pi5 is going to be cheaper at release than the Pi4.
Ultimately though, at least IMO, the Pi isn't about being cheap, it's about being capable while staying a great value. I bet there's a lot of hidden complexity in the pricing, and it's very possible that they'd have to compromise significantly more than 12.5% of the functionality/performance to get a 12.5% price reduction (to $35).
A naive approach that may still work well is to simply break up the image into fixed, predetermined regions. I don't believe this would be significantly more work for the server if it's already comparing pixel-by-pixel, and the average frame will probably contain updates only in one region. Even breaking it into 4 or 6 would, I think, be a significant payload reduction.
Ehhh, a lot of high level languages support low-level interop. Python, Ruby, etc. It's not something you usually reach for as a user, but rather as a library author.
Of course everyone wants their language to be faster, but the interop story for Elixir/Erlang is very good, all things considered.
Similar issues for me. I can load github.com and my profile, but visiting a repository (or trying to git pull a repo with the https origin) returns a 500.
