swaits

You did make a good call on skills.

Anything that lets us compose smaller tasks into larger ones effectively is helpful. That’s because self-attention (ie context) is still a huge limiting factor.

As someone who uses these tools a lot, and who sits on the bleeding edge everyday, I agree with you.

Keeping things in perspective, no, there is no reasonable concern of this happening in the US in the near term.

The places where this happens, like Iran now, are in extremely different situations than anything in the US, or any other Western country.

That shouldn’t discourage people running meshes though.

This unlocks some really nice stuff in the future!

Unfortunately seems to be too old to include coverage of FSRS and the associated optimization algorithms. Would love to see Gwern’s updated thoughts on this.

`jj` isn't new. It's definitely not *very* new.

Definitely let your keybinding keep you from trying out and using a fantastic tool.

Frankly, this is a rather poor, uninformed excuse. Most people who try it grok the concepts in days. And they feel right at home in weeks. That's when you start hearing, "I'll never go back."

Google is definitely your friend here. Plenty of tutorials online.

This is one I'm okay with. Git submodules are absolutely awful.

I recognize that some folks are stuck with it, and yeah, in your case jj probably just doesn't make sense. Stay tuned though.

Pragmatic is using the best tool for the job. Certainly subjectively, and arguably objectively, jj is the better tool in many ways.

My advice is to try it. You should like it, if you're in the majority of folks to give it a sincere shot. If you don't like it, cool. But then my advice changes. jj is probably the future. Adapt or become one of those old-timers who froze their learning in time.

This isn't going to be a very HN-like comment. But it's rooted in fact: That is complete nonsense.

Every time I see one of these nifty git tricks or workarounds I find myself wondering, “why not just use jj?”

You get a nicer, significantly simpler interface. You don’t need any tricks. You don’t have to google how to work yourself out of a bad state, ever. And you get near-perfect git compatibility (ie you can use jj on a shared git repo, doing all the same things, and your teammates won’t know the difference).

I’ve wondered if there is a psychological thing here: someone who spent time memorizing all the git nonsense may have some pride in that (which is earned, certainly), that introduces some mental friction in walking away???

I know what you’re trying to say. That Proton IS Windows at some level. And so MS gets some credit for that. But they don’t.

A lot of actual work went into Proton and into making games work therein.

MS is a slow, lumbering, monoculture that has lacked innovation and creativity for a very long time. I don’t see how freezing APIs or keeping old APIs around (mostly through versioned DLL hell) as some grand accomplishment.

Mmmmkay then.

And the entire Quake series runs very well on Linux+Proton as well. In other words, I’m not sure why this is impressive on Microsoft’s part.

The online games have depressingly (to me) small communities. But they’re still kicking.

It’s not luck. To assume so, let alone say so, is uninformed and quite rude.

Getting into these roles requires a ton of hard work. Yes, it’s a grind.

If you feel it’s only achievable with luck, I suggest you’re selling yourself short.

You’re understating it. Meshtastic is horribly designed. If you designed a wireless mesh network making all the worst possible choices, with the most shortsighted design decisions imaginable, you’d get something a little better than Meshtastic.

It’s some mixture of luddites, denial, ignorance, and I don’t know what else.

I’m not sure what these people are NOT seeing. Maybe I’m somehow fortunate with visibility into what AI can do today, and what it will do tomorrow. But I’m not doing anything special. Just paying attention and keeping an open mind.

I’ve been at this for 40 years, working professionally for more than 30. I’ve seen lots.

One pattern I’ve seen repeating is folks who seem to stop leaning at some point. I don’t understand this, because for me learning everyday is what fuels me. And those folks eventually die on the vine, or they become the last few greybeards working on COBOL.

We are alive at a very interesting time in tech. I am excited about that. I am here for it.

Nobody is saying it out loud. But as always, it’s probably about money.

Go definitely popularized concurrency for the modern era, but coroutines themselves are ancient tech. Melvin Conway coined the term in 1963 and Simula had them by '67.

It’s also worth noting that the specific 'coroutine' model most languages are adding today (JS, Rust, Python) is based on C#'s async/await.

Go actually rejected that approach in favor of Green Threads (Goroutines, not coroutines), so technically it popularized the alternative to what everyone else is doing.

PHP is fine. If the site sucks it’s not because of the language.

It’s pretty common sentiment with senior level Amazonians that Uncle Jeff was a great leader. Many lament his departure and loathe his replacement.

Lifestyle distractions aside, Bezos playing any kind of CEO role is probably a good thing.

Oh that sounds quite nice, thanks for sharing!

MeshCore is a huge step in the right direction. Especially over Meshtastic which is very poorly designed.

However MeshCore makes one fundamental choice which is severely limiting. It uses a single LoRa discriminator and channel for all nodes. That said, LoRa limitations pretty much force this choice.

This, limits a typical network (3 repeaters) to about 500 messages/hour. The throughput scales inversely by how many repeaters you can hear.

The code does try to adjust down the TX power of a repeater in repeater-dense networks, which probably helps keep throughput consistent for a while.

For these things to work at scale they either need something other than LoRa (which is quite novel, but limited) or they need to figure out how to use LoRa in a way which allows for more channelization.

Until then, the “one transmission at a time on the air” in these very low baud networks is severely limiting.

Probably referring to the mailing list from https://hackernewsbooks.com

It is almost certainly deterring many more than the 66 who were aggressively deterred.

Bring it up with the author then. To the rest of us, what you're saying is senseless.

Don’t just back away slowly. Run for your life!

Prediction: this is the part of the AI boom that goes bust.

This is 100% how it works at Amazon. It is said you have to do the job (of Principal Engineer) to get promoted. But most Principal Engineers are doing a different job than the job you have to do to become one yourself. Signed, PE@Amazon for 9 years.

Slackware’s last release was 2.5 years ago.

Look at Fedora (if you like RPM distros) if you’re after something pretty nicely put together that stays reasonably well up to date. Very well maintained. Influenced by Red Hat (or “led by” or even “owned by”), which works for some, not for others.

CachyOS is trendy these days. EndeavourOS is basically Arch with an installer.

There are a few distros targeted at Windows refugees. ZorinOS is well regarded. AnduinOS is a newer entry. But if you’re willing to walk away from a Windows-like UI, skip these.