aeblyve

As long as it is in the normal range for your sex and age, you're fine even if your ferritin remains at 0.

This is simply wrong when one considers that iron has many bodily functions outside of hemoglobin, such as acting as a cofactor in tyrosine hydroxylase for dopamine synthesis.

I've read some of your stuff over the years and was appreciative of its accessibility.

https://pages.cs.wisc.edu/~remzi/OSTEP/

The above is another example I appreciate: the authors charge for physical copies and complete documents but generally make the work content available for free. I've bought a physical copy in that case because I really valued the work.

I agree with the cognitive premise unfortunately. But even so, I start to speculate about solving this by DIY book printing, or advances in digital reading technology (mostly I'm interested in the latter, for example, means of "spatializing" the flat screen experience, and reducing latency to a minimum)

In most cases that is also true, although in rare cases I will buy physical copies of certain books for that reason.

I have a hard time cognitively justifying most physical book purchasing anyways when internet shadow libraries have most of what I want to read.

Reminds me of how startups now will change their social proof marquee on the landing page from actual testimonials, to "trusted by XYZ", to just one composed of company logos (with the level of corporate engagement to be imagined up by the viewer)

‘At a certain stage of development, the material productive forces of society come into conflict with the existing relations of production, or this may express the same thing in legal terms - with the property relations within the framework of which they have operated hitherto. From forms of development of the productive forces these relations turn into their fetter. Then begins an era of social revolution. The changes in the economic foundation leads sooner or later to the transformation of the whole immense superstructure.’

Marx

People salivate so hard at the thought of the high level of automation promised that they're willing to do away with privacy altogether and live in Data Communism.

My thinking is, this will increase the demand for backup and other resilience solutions.

Not really, personally... time waits for no one.

This is awesome! In the past I would use the promise of starlink or other LEO internet as a tiebreaker for booking flights and was disappointed a few times (as clearly not all of the airframes for an airline have the capability)

I found it absurdly slow yesterday.

I don't know much about UL but I can say that FCC certification (also technically required) for electronics can range from about $3k to something like $30k depending on what you're doing.

($3k would be for "unintentional radiator" device, i.e., not supposed to be a radio, $30k would be for "intentional radiator" device, i.e., supposed to be a radio)

That's all fair. It is a cool piece of work nonetheless.

For example I am thinking, what if I wanted to hook up my micasa instance to some other arbitrary self-hosted service? If it's an App that means bespoke code, with a spreadsheet stack it is trivial.

I feel like a lot of these types of apps could just be spreadsheets. Maybe a "smart" spreadsheet like Grist[0] executing Python code. Am I off-base there?

[0] https://github.com/gristlabs/grist-core

This is a more honest comment than the many around it making overly intellectualized arguments.

But I would sooner compare this engineer class to something of a small bourgeoisie swallowed by a yet larger one, especially in the United States.

Familiar relationships always come out of a sense of shared responsibility and utility, not out of a "secular" desire to "make friends", the way I see it.

So, live vigorously in a way that benefits from social relationships and they will necessarily come.

Be useful to others and they often return the favor.

ZeroFS is a single-writer architecture and therefore has overall bandwidth limited by the box it's running on.

JuiceFS scales out horizontally as each individual client writes/reads directly to/from S3, as long as the metadata engine keeps up it has essentially unlimited bandwidth across many compute nodes.

But as the benchmark shows, it is fiddly especially for workloads with many small files and is pretty wasteful in terms of S3 operations, which for the largest workloads has meaningful cost.

I think both have their place at the moment. But the space of "advanced S3-backed filesystems" is... advancing these days.

It has some functionality of this type (you can see in the overall map a small number of "sensor" nodes), but it's not super well fleshed out or documented ATM.

What I think you can do for sure today is poll a sensor over the mesh, unlike the meshtastic way where you generally automatically broadcast telemetry.

Nth for MeshCore, which the Boston Mesh has found to be a much more scalable solution for building an emplaced mesh network with hundreds of clients: https://analyzer.letsmesh.net/map?lat=42.00963&long=-70.9639...

Separately: while it's cool to chat human-style over these networks, lately I've been thinking that the real value add is last-mile automations. Stuff that won't clog the network like remote-starting your car once or twice a day, and is normally built on top of LTE.

I think that would be too reductive. The objective productive factors of software are what give it actual value. The author could have chosen to write "produce useful software", but did not.

I find that the software that evinces a feeling of admiration in me is itself as devoid of feeling as possible, RE the observation that aesthetics are created out of pure functionality.

The more "sentimental" or "egotistical" a piece of software is in itself, the less I like it. Taken to the limit, the title of the article commands us to generate Skinner boxes to maximize user engagement etc.

Meshtastic is reasonably good for unplanned and mobile use cases such as hiking, but for building an emplaced network, Meshcore has much better performance.

This has been our experience in the Greater Boston Mesh.

It's worth commenting to me that MeshCore performs much better than Meshtastic at scale and as an emplaced deployment. We have a very active network of about 60 nodes in the Boston area which feels similar to iMessage in deliverability and speed.

But yes, it can't realistically be compared to something like a "real" MANET system with $10k radios that can do something like 100mbps data rates. It is dramatically more accessible and deployable though.

I've seen a few times people using the weather-guarded 120 VAC outlets (provisioned for power tools) on lamp posts at institutions to steal a bit of charge.

Host is erroring out, so webpage is down, per cloudflare.

I'm quite sympathetic to on-prem but there's a possible argument against.

The reason is oftentimes fairly simple, certain people have their material wealth and income threatened by such automation, and therefore it's bad (an intellectualized reason is created post-hoc)

I predict there will actually be a lot of work to be done on the "software engineering" side w.r.t. improving reliability and safety as you allude to, for handing off to less than sentient bots. Improved snapshot, commit, undo, quorum, functionalities, this sort of thing.

The idea that the AI should step into our programs without changing the programs whatsoever around the AI is a horseless carriage.

Hand coding can be the knitting to the loom, or it can be industrialized plastic injection molding to 3D printing. How do you know? That distinction is not a detail--it's the whole point.

One could have made a reasonable remark in the past about how injection molding is dramatically faster than 3D printing (it applies material everywhere, all at once), scales better for large parts, et cetera. This isn't really true for what I'm calling hand-coding.

Obviously nothing about the future can be known for certain... but there are obvious trends that need not stop at software engineering.

Agree, and well said. There are no points for hard work, only results -- this is an extremely liberating principle when taken to the limit and we should be happy to say goodbye to an era of manual software-writing being the norm, even if it costs the ego of some guy who spent the last 20 years being told SWE made him a demi-god.

This process has been affecting most of the world's workers for the past several centuries. Programming has received a special treatment for the last few decades, and it's understandable that HN users would jump to protect their life investment, but it need not.

Hand-coding can continue, just like knitting co-exists with machine looms, but it need not ultimately maintain a grip on the software productive process.

It is better to come to terms with this reality sooner rather than later in my opinion.

I use "artisanal software" to refer to software written by small groups of individuals as opposed to larger organized groups.