HN user

jezzamon

658 karma
Posts1
Comments187
View on HN
Dav2d 2 months ago

You are underestimating HN's reach, this happens all the time. As someone who has been on the front page of HN it's a pretty big rush in traffic!

FYI, those 8% of males / 0.5% females stats are not about complete colorblindness, so almost all of those people use color in their life

I have been in a locust plague once. It does feel very weird. Yes they are grasshoppers but you might be underestimating just how many there are. Plus they don't look normal, they actually change appearance when they're in a plague.

One small detail I remember was when the sun was just behind a building, you could see this glow around the building which was the sun reflecting off all the locusts that were flying around it

It's possible he had multiple accounts but seems unlikely, one reason he was caught was because he made a whole bunch of trades on markets related to "year in search", all on one account, and all the trades were perfect. If he was thinking about creating new accounts to obscure himself then he should have at least made each bet he placed on a seperate account.

People (particularly those committing crimes) do frequently overlook things in inconsistent ways, so it's possible. But seems unlikely to me.

You can definitely get stuck in a weird place with git that I haven't run into in the same extent with jj. The ability to undo anything with the one 'jj undo' command is awesome in the agent coding world when it makes a mistake.

If you do want to solve this, here's two thoughts on how you can deal with it. First: don't try to edit jj changes. Always work on a new change and then squash that in to the parent. You think of that top level change as your working space.

From there, the simplest way is to just always use 'jj commit -i' and 'jj squash -i' to create change ids with your work. Then if you want to have your changes move around with you, just rebase your working copy which contains your "uncommitted files" to the new branch.

A different idea is to put those changes in a separate change, and then when you do work, always create your working space change as a merge change like 'jj new <uncommitted file change id> <main change id>. Then you should be able to do 'jj absorb' instead of 'jj squash' to put changes into the right change. Switching to a different branch is 'jj new <uncommitted file change id> <other change id>.

As in typing this, I'm thinking for myself and what I actually do in practice... I find moving / rebasing jj commits very easy (I have a UI tool that literally lets you drag and drop them) so I usually just commit these changes and then drag the commits around so it's not in the chain of when I want to send it out for review

Wow. As someone who just went through this process myself (leaving the US to get a green card via consular processing), I can only hope they hire more people to handle the increased case load. You need a medical exam and there were only 2 people available in my country to do that, which added 2 months to my application time (where I could not return to the US)

I have the originals of both, the screen is much better on the switch 2. Don't have any other similar devices or the OLED version.

In the Switch 2 Welcome Tour app they even have demos to highlight the improvement in the screen quality compared to the switch

For me personally this is one of my all time favourite games. It has a lot of charm and humour.

It looks like it's a zelda-like game, but because combat is deterministic rather than skill-based, it's really more of a puzzle game

I mean. If the cost per use of use is only slightly worse with these cheaper goods, you could just view that as a slight premium for the ability to switch styles every few years. It's also a smaller upfront investment, so taking account inflation it might not really be a big difference even considering that?

Clearly most people choose to buy cheaper stuff and producing higher quality, more expensive things makes you a niche company