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

Highest priority is moving the toolbar???

Fortunately the LLM will always see that your gut instinct was right all along.

Others are pointing out that many also lost money, but I think we can say something even stronger, which is that the people that got rich only did so by taking the money of the people who lost money on it. If it's the future of money, you'll be able to buy in at a stable valuation, neither winning nor losing in the transition -- that's kind of a key property of money.

And yet, at some point most web developers will have picked it up after the "raw html" era -- that point has probably come, even.

Others mention Apple news+ but there are actually a bunch of services that do this. Zinio is one that I've encountered, but a quick search shows that there are also Magzter, Readly, Flipboard, etc etc. I can't speak to their relative merits/range of content/user hostility. In the early 2010s I used to use one where you bought credits and paid per article (usually on the order of $1-$2 iirc, but depended on the source/length). Can't remember what it was called and I don't see it on any of these lists, so maybe it no longer exists or was bought up.

Anyway, this is something you can have if you actually want it.


I think part of why we're much more likely to learn about the iid, finite-variance CLT is that it's a lot easier to prove than the more general ones.

Yes that's a big part. The proofs get hairier otherwise.

But I think there is more to it, the convergence to Gaussian also gets slower.

In practice, we deal with finite averaging, so speed of convergence matters. For some non-iid case, the convergence may be so slow that the distribution cannot be approximated well by a Gaussian.


It sounds like you already know how to improve your comments, how about just doing those things.

Well, I keep missing the "serve"/"server" thing because spell checkers think "server" is a real word so don't flag it. :-)

I'm happy to forgive that kind of small typo in a hacker news comment, but generally it's easy to catch these things by just reading over the thing one time. If you're putting any amount of thought into your contribution it should be much faster to read it over one time than it was to write in the first place.

Getting that wrong is a small price to pay. Plus, people know what you mean.

Too much effort, bruh.

Capitalization is apparently too much effort for some now. Who would have thought the Ai would make us so lazy so quickly?

Who cares about people with reading disabilities, let's shift burden onto the reader. My time is better spent managing my Ais.


This started years before LLMs, as a way of signaling unconventional thinking. Maybe influenced by the UX of instant messaging.

That's my general understanding too. More recently people have adopted it as a way to not look like Ai, I've had several cite that as their rationale. There has been a notable uptick since the Ai step function change at the end of last year, along with all the other patterns we see, such as the one that underlies this new HN rule.

>onto the reader

Or the reader's AI who is able to format or translate the text to make it easier to read for the reader.


I shouldn't have to burn tokens to read. Most input boxes and editors will handle the capitalization for you during auto-correct. It seems like people go out of their way to drop the caps.

On mobile, maybe? I haven't had anything like that on any PC I've worked on.

IMO, if it's too much effort to improve one's comments, then it's too much effort to write them in the first place.

There's something viscerally distasteful about a one-liner comment berating the author of a long thoughful comment for exerting too little effort.

You can already do this in vim. Pretty easy to shell out to whatever command you want and use the result for various purposes.

That's still built on top of the hardcoded vim design choices though.

For example, I really like the "select then edit" approach of Helix, but Vim doesn't really play nice with that (there may be better plugins since I last looked to be fair). File handling, buffer rendering, and frames have very little to do with that, and yet I have to switch editors, lose all my plugins and configurations, and switch all those subsystems at once.

There's missed opportunities for modularization.

Edit: looks like Neovim is already split from its UI.


You're right that changing the whole editing model will involve rewriting a lot of keybindings. You could do that in vim if you really wanted to -- start by remapping motions to enter visual mode first. I don't really know why you'd want that when visual mode is already a keystroke away, but that's ok.

FWIW though if that's what's important to you, I get the sense that kakoune is much more vim-like in making it easy to compose with other tools, while being set up for your preferred editing model.


The post is not about preventing the rise of fascism, it's about not preemptively building tools for them to use in implementing fascism.

Yeah sorry I'm not a fan of rearranging deck chairs on the titanic.

By "ad-tech" it's referring to the surveillance that underlies modern targeting of ads on the internet. YC's job ads don't do that.

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

Search: