These days I go to https://news.ycombinator.com/active And search for [flagged] items first.

That’s what I do too.

Does this explain Atlantic reporter invitation?

> Does this explain Atlantic reporter invitation?

If it does they should both be hung because it means their phones were broadly breached.

That explanation seems less plausible than the people involved just doing something dumb.

I did not expect RISC-V to be ahead of ARM for framework. Is this is because of freedoms RISC-V brings for manufacturers?

Or because it's basically a way for a board maker to have a laptop form factor available for their device.

It's a way for other companies to piggyback off of Framework rather than the other way around, while strengthening the Framework ecosystem.

That's my perception as well. TFA is clear this is a partner-driven thing, so I suspect DeepComputing drove most of this (obviously with some collaboration from FW though). Win/win for all involved!

It's great to see partner ecosystem developing! Framework is such an exciting company.

An end goal of targeting RISC-V is better for everyone than targeting ARM or x86. No licensing fees, manufacturers could design their own silicon and be completely royalty free, etc...

Right now we are nowhere near that. RISC-V software and hardware is not very mature at all. But much of this can change very quickly once products launch.

Maybe just the availability and maturity of that particular SoC, the PineTab-V tablet uses the same one. An obvious ARM SoC to use in a laptop is the RK3588.

> An obvious ARM SoC to use in a laptop is the RK3588.

Yup, I've got the RK3588 module preordered for my Reform and I'm looking forward to it. Would be neat to see an RK3588 board for the Framework too.

Nothing wrong with a little hype-chasing.

Wait, isn't it the old way of thinking? That browser is a medium rather than a compute node. (I like both old and new ways)

Good point Marius.

It is a new way to think compared to the "modern js framework" craze over the last 10 years.

But, you're right, it is the "old" way of using the browser/html with sprinkles of new interactivity.

Didn't even think about that.

Sometimes I wonder what would be the smallest program to generate humans DNA. How many operations would it take and how would it compare to real world iterations of total evolution.

Interestingly, dna programs are quite compressible

https://en.m.wikipedia.org/wiki/Compression_of_genomic_seque...

Not sure what kinds of selection pressures there has been for shorter DNA strings, but presumably you could compress it a great deal putting it in a .zip file. Now imagine the havoc caused by random mutations on that format though.

If we ever find a perfect theory of physics, then that might be the smallest program to generate human DNA.

I failed at first try but I found a hint by looking at the example character by character.

Using xss one might target login form and steal username/password instead of a token. So I do not see argument here against jwt. Sure the xss will have to be more sofisticated(?)

I’m not arguing for / against any specific technology. I’m saying that relying on a lack of security flaws in one layer isn’t a great idea.

I don't find these figures regarding casualties in the article.

Could it find some equilibrium environment to be able to suck as much matter as it radiates. So it could last longer (?)

It only has the gravity of a 1 kg object and is extremely small, so it's not likely you'd be able to find an environment where mass is going to be getting jammed into it at quadrillions of tons per second even ignoring the fact that it's sort of a continuous nuclear explosion — it's radiating all its mass energy at a rate a few million times higher than the output of the sun in the ballpark of a star actively going nova.