tliltocatl

Screw average user.

It is server-rendered cgit pages, there are potentially quadrillions of unique. They are not cacheable.

Nei. Please don't. Enough money wasted already.

If you want to jump on the bandwagon just build a semi fab. Lots of clean water, lots of electricity, lots of geologically stable ground, lots of money that can't be invested locally - can't see why that haven't been done already. And it will still be useful after the fad is over.

I get:

Visualization failed:

createProgram@https://magik.net/llmcity/:1098:115

MatrixRenderer@https://magik.net/llmcity/:1107:20

main@https://magik.net/llmcity/:1895:20

(IceCat)

> Patents are designed to protect costly research

I'd argue that how they should have been, but the reality is quite the opposite. The patent framework is all about novel ideas rather than costly research, even though ideas aren't any valuable anymore - the easy stuff that is cheap to reproduce once the idea is known is already discovered.

Multimedia codecs and similar stuff are pretty patent-worthy (costly research) but their value is an exponential function of their adoption, and hence the unencumbered one always wins. Same with basically everything else.

I think they already do that, except it's not 1980 so you don't fix the upper mask, you fix the lowest metal layer (the upper layer is very coarse and is only useful for power). But even a single mask is still quite expensive.

Using LLMs for information retrieval is the most stupid thing one can do. Especially when old methods work much better.

Nice idea, but the interface needs some polishing:

- In general, you are exposing too much of the internal object model to the user. E. g. nodes added by the user and nodes added during reconciliation might be same class internally, but the user don't care much about the latter.

- "Reconciliation" looks like a sure way to confuse everyone (e. g. made an equilateral triangle, why are my joints not exactly the same? Forgot to reconcile one).

- A button for automatically merging all attachments at a node into a joint would be nice (but that might require keeping a track on what got reconciled where).

- Would be nice to automatically adjust length ratio and reconciled offset for shallow connection angles.

- You have to tweak visibility settings to be able to select nodes, virtual links and attachments, that's a bit ugly. Would be nice e. g. to be able to select a virtual link behind currently selected physical link, or a node out of a list of nodes on the current link. Especially when adding a connection in the middle of a link - you have to select the link, then hide physical links. Perhaps only allow selecting valid/semantically meaningful elements in this modes, and highlight them so that they aren't occluded?

- Any way to exploit symmetry? That's a bit advanced, but if we are making a regular tetrahedron it's quite a chore to repeat every operation four times every time you have to readjust it. That's particularly desirable because when you one physically manufacturing the design, one'd like to know which parts are interchangeable.

- Make automatically assigned names shorter (i. e. J1 instead of "Joint 1") so that you could put them as labels on prints.

> Why would a developer using LLMs be hammering their own codeberg site?

Because a significant percentage of "developers using LLM" have no clue what they are doing?

Hosting your code on a free server is not a universal right. It is a privilege.

Neurodivergency, or whatever you might call it, sucks, at least during childhood. Ten times so in a family-centered society. I had a mild enough case to grow up functional and independent, but if not for that… I totally see how one might chose a risky treatment even when fully informed. The problem here, it looks like the consent was nowhere informed enough, and the research team chose not to publish the case after it turned out a failure.

TL;DR:

- The girl had a really rare genetic disorder, traceable to a single-base mutation, that result in intellectual disability. Her case was quite mild, she was verbal and only had a learning disability, other cases are often far more severe.

- They went for using adeno-associated virus as vector to deliver a CRISPR payload. It caused kidney and liver damage (AFAIUK due to immune response, not the virus itself? So hard to predict from an animal model.) which turned out fatal.

- The family paid a significant share of the research funding and some off-record financial favors to the research team.

- The research team's recent publication in Nature didn't mention the case at all (they basically chose keep silent about failures).

The whole story has quite some Flowers for Algernon vibes except real life is way more cynical and sad. And I disliked the book back when I read it because it felt like a weepie just for the sake of weeping.

> with the caveat that there is NO private pay option

I don't think there is a society in the world that ever had that successfully executed in practice. I live in Norway, and even if the public heath system is probably as good as it gets here, I often use private providers for non-urgent things simply because waiting time can be up to six month otherwise.

And even if you somehow manage this on paper, you'll be very surprised on how markets work. They don't need legal recognition. They don't even need money. See: USSR. Health care was public and medics weren't even a particularly attractive profession because there were too much of them already. Still if you wanted to survive an appointment you'd better have a package of some deficit wares ready.

What denies public healthcare money isn't "wealthy trying to cut public spending down". It's bureaucrats wanting their share of the pork barrel.

> Corolary: submarine datacenters are much better than orbital datacenters

Yea, except datacenters also need connectivity. And submarine connectivity, while not particularly expensive, is quite vulnerable - even more so than on land.

This sounds pretty similar to Java's array-of-templates problem. Is it really more of a problem than parent pointers?

At that point they might skip the bonfire part (or the locals would without asking their permission), which is kinda the whole point.

> the densest 64bit ISA

Because all other 64-bits were designed with no regard to density too. On 32-bit (and thats where density matters) it's sill worse then Thumb even with compression extension.

> I'm starting to get the feeling that there is something fundamentally broken in the RISC-V specification that fundamentally limits performance.

RISC-V is an objectively bad ISA design (a resell of MIPS dropping some of the most ominous features, then trying fix the code density issue with billions of extensions), but x86 is way worse and it didn't prevent Intel from making performant implementations. And RISC-V is certainly not bad in the way that would limit performance (well, maybe code density, but it's not the major issue).

The reality is, ISA matters very little for CPU performance. What really matters a lot is the memory subsystem and interconnect. I. e. good DRAM controllers IP are pricey - way more pricey than ARM cores AFAIK. Not a problem unique to RISC-V - i. e. Altera memory controllers used to be shit as well, not sure if Intel changed anything.

And another issue - there doesn't seem to be all that much money in CPUs any more. Look at ARM's history with high-performance sector.

By starving off access to cheap DRAM for everything that isn't AI?

MDY, seriously? Please don't.

> If market followed rational logic, you could pre-calculate which stocks will be what price and never lose money.

The fundamentals are unpredictable, so even a perfectly rational planning (suppose such thing could exist) would lose money sometimes. Not in the long run, but long run doesn't matter if a single wrecked ship can wreck you.

I don't think it's any good for that. It's relatively narrowband and not the frequency you usually have issues with EMC on (5 to 6GHz - unless you are specially transmitting on this frequency you are unlikely to emit anything there).

"Moore's law" is a marketing gimmick. The real physical law that held for decades is Dennard scaling, which stopped to apply already in 2006 once transistors got too small so short channel effects and gate leakage kicked in.

Yea, but governance structure can be changed on a political whim. .io is efficiently governed as a gTLD now, even if it is a ccTLD. While .com/.net/.org are generic and governed by ICANN, the registry is VeriSign, a USA-based company, and ICE made it explicit already in 2010 they can seizure these any time they see fit. Back in 2010 it was mostly for genuine law-enforcement ends (whatever these ends justified the means is another story), but with what became of ICE recently, I would not bet on anything.

Same applies for .com/.net, except it's USA's politics. Which you may or may not consider more reliable. But yea, ccTLD domain hacks are pretty damn stupid.

That's to be expected, in this test setup wall density is the only thing that matters (and Blender physics friction model is probably not quite realistic either). But heavy rolling ball impact isn't the kind load these walls are normally subject to.

Except NK isn't a hereditary monarchy. One might say "so what, they still have a dictatorial rule by a single family", but it is an important difference: the leader post inheritance isn't governed by a clear set of rules so familial illegitimacy is just irrelevant for politics.

A friendly reminder that a 0-day is a vulnerability that wasn't known until after a malicious actor exploited it. If someone publishes a PoC, it is not a 0-day, just a vulnerability.

Depends on the application, of course. For "google replacement" they are trying to sell it as - it's absolutely essential, but even then it works like crap. For coding… Maybe it's not so essential? Yea, it would not know about latest libraries, but maybe that's not much of a problem? Then, of course, it is a big question if LLM code generation is worth it at all.

Based on what I could find:

They generate the RF on the surface and transmit it down the borehole thru a waveguide, so it's only limited by arching in the waveguide. Since we only need power transfer and don't care about multimode propagation, the waveguide diameter isn't limited, and probably on the larger side to reduce copper losses. And the heat management is provided by blowing argon which also carries abalated rock particulate to the surface.

See the schematics here: the schematic here: https://www.thinkgeoenergy.com/wp-content/uploads/2021/03/mi...