4,781 karma · joined August 19, 2007
But - what stops banks from creating infinite money? There is a byzantine system of rules laid out by the Basel Accords and national regulators within that. That system limits the activities a bank can conduct, lays out rules for the way it must go about business it can conduct, and sets capital requirements.
There is nothing close to a full reserve and the system is not defined in those terms. Rather, there are ratios. If you have so many AAA rated treasuries posted with your central bank, then you can grow your balance sheet by X. But for B rated investments, you can only grow your balance sheet by Y. When a commercial bank issues a loan, it literally creates money.
It is rarely clear what the hard problems will be when new to a domain. Only as scale kicks in.
We are constantly pitched frameworks that sell themselves as a good approach to a domain, but then obstruct engagement with the hardest problems when it matters. The developer becomes captive of the system that claimed it would steer them right.
This is particularly true of fields where the hard problems are integration problems which, by their nature, cannot be outsourced to frameworks.
Net booting. Distros vary in how awkward it is to get stripped setups set up for net booting. My experience is that the redhat world distros are easier for this than the debian world.
It exists to deal with the dynamics of scarce goods. If person a is using your wheelbarrow, then person b cannot use it as well. You can't raise cows on a piece of land, but also plant a crop of wheat there. This definition goes back thousands of years and is respected across cultures.
There is another practice that was respected across cultures for thousands of years: the free sharing and open remixing of songs, stories and ideas.
IP is a weaselly project to carry the advantages of property rights to non-scarce goods, and to things which were previously fiercely regarded as public domain. It creates a set of rights which did not previously exist and which created new benefits for people who were already elites.
"For IP, others selling copies would restrict your ability to sell copies as they undercut you." This does not follow from the argument you are making. Selling something is not a use of it. Carting things around in a wheelbarrow or playing a compact disk - these are examples of use.
Perhaps you bring some cultural bias to this conversation. Having grown up in a setting with IP, and having a career in a field where some people gain great advantage from IP, you have come to believe that it is reasonable to regard ideas as property.
But IP is an aberration, even in our time. It is not law in all places, it is not enforced well in the places where it is, and in those places people who are morally conscious and otherwise law-abiding routinely violate it.
IP is impractical to enforce equally, is inconsistent with the principle of live-and-let-live, it raises the barrier-of-entry to a range of industries, it grants extra privileges to existing elites, it is easily gamed by bad-faith actors, it is disrespected by the general population, it has at best a hand-wavey economic justification that is backed by no real evidence. IP is complicated when good laws are simple, and IP muddies the water for a concept that is a genuine foundation of our civilisation - property. IP fails all tests for what is reasonable law.
If the government were to say that black were white, this would not make it so. So it is with property.
> minus its free catastrophe insurance
Many more people have died from dam collapses in the last fifty years than nuclear accidents.
> Every kwh of solar and wind produced electricity right now > is a kwh not produced by gas and will be for some time > almost everywhere.
We don't have a general-purpose solution to storage. As a result there is waste overproduction of solar and wind at some times, and under-production at other times. Those under-production windows need to be covered by base-load forms of energy production such as gas and nuclear.
We do not currently have a general-purpose battery for solar and wind that could power the grid when they stop producing. (Some regions can through pumped storage hydro.)
Nuclear compares against base-load power sources: coal, gas, oil, hydro, geothermal.
When I was watching the video, that argument reminded me of the Peak Oil campaign from about twenty years ago. This claimed that the world had reached a point where the amount of oil available would be in decline going forward, and claiming that this justified major changes. At the time, this Peak Oil claim got a lot of sympathetic coverage in mainstream media. Oil production has been healthy in the years since, and technology changes have opened up new reserves.
1. It is common to use USD because it is convenient, but it is not a standard. There is no structure that forces it.
2. The world does have dozens of liquid currencies already. Banks do offer rates on them. And banks do trade in them without the USD being in play.
3. It is simply not true that the current system of floating exchange rates would fail to function without the USD.
The author moves on to talking about it being a privilege to be a reserve currency. It is not a privilege to be the reserve currency - countries generally go out of their way to avoid it happening - the Swiss central bank headed it off within the last ten years. Patrick Boyle's recent video /The Weaponization Of The Dollar/ touches on this in the last few minutes.
I stopped reading here.
The concept of Eurodollars (US-denominated debt outside the reach of US foreign policy) has been effectively obsolete in the developed world for decades.
Any bank who has a balance sheet large enough to be involved in significant trading operations (e.g. operating as a top-level general clearing member at a clearing house, or acting as a prime broker for foreign exchange transfers) is also able to qualify for an account with the US central bank. This gives them access to cheap lending (free money).
When you take on this membership, you sign up to align with aspects of US foreign policy. And not just for stuff you do that is denominated in USD - it applies to all your business globally.
A recent example of this - Deutsche Bank got fined for money laundering done by Danske's Estonian Branch. Danske were operating on DB's balance sheet, which means that DB had failed to ensure that their balance sheet use aligned with US standards on money laundering, so DB got fined in the US even though they had no direct hand in the wrong-doing.
It is these arrangements that allow the US to be so effective in launching sanctions against other countries. Consider how Trump decided to go after Iran even though European countries wanted to stick by the Obama-era deal, and how thorough those sanctions have been.
Is it possible to have a top-tier western bank who choses not to have a relationship with the US central bank? Hypothetically, yes, but who would do such a thing? Such a bank would lose access to cheap lending in the world's largest economy and would lose economies of scale.
It is not the USD that is powerful, it is the US. The US is a vast economy with a strong rule of law tradition. Common use of USD is a side-effect of that.
Thanks for this correction.
One of the challenges of management after feudalism is making the best of the variety of individual contribution. When you are moving rocks around or ploughing, each individual is roughly equivalent. This was obsolete by the industrial era. A factor in Japan’s rise in auto was giving workers direct and individual (ie not union-filtered) feedback into the manufacturing process.
Now, the multipliers are higher still. There are regular situations where an aggressively small team has executed where several well funded teams of thousands failed.
My view is that capital is nearly irrelevant in mainstream technology now beyond achieving bootstrap and avoiding dumb renumeration errors that alienate talent. Rather, the key tensors are 1. how high you can get the ceiling on your core talent and 2. how small you can get that team, in order that this talent can be engaged with the big picture, in order that they can be identifying and focusing on the most important problems. They are related. The more capable your talent, the more it can participate in the big picture.
These dynamics do not resolve easily with the orgchart-centric, bigger-is-better assumptions of traditional worldviews.
Possible limit to the view - I have not had exposure to fields with vast ongoing capital cost, or complex cross-discipline stuff like silicon manufacture
You could offer something like shell scripting on that, but my system did not and there are better options. For example: have the resource manager expose a command that offers a DSL for making system-wide changes.
It is useful to have both the fitted arrangements and operator interaction.
In addition to giving operators power to make changes in production, the command line is useful for development. Devs can develop in a one-host grid and interact with it in a repl-like way. Contrast this to traditional workflow where the deployment environment is quite different to the development environment. This encourages devs to work with the grain of the platform and discourages the "it works on my machine" dynamic.
There is a name for this: Single System Image. There is no need to write the operating system layer - Linux works well.
I built a SSI. Each grid can host several apps, 'gridapps'. As priorities change during the day, an operator can rebalance resources using a bash-like shell. Each gridapp has (1) core nodes, which need to keep running, and (2) scale nodes which can be started and stopped. Nodes can be configured so they are taskset-bound to an individual processor, or sharing a processor between several nodes. There are equivalent primitives for memory and persistent storage. Commercial, 1000 cores.
The author contrasts this with K8s by saying that K8s is declarative. This is not the important distinction. My system had declarative configuration, and did a fitting at startup.
The key difference is motive. The design above is the natural choice when you build a grid computer from first-principles.
K8s is designed to solve a different problem: scaling up the traditional model of programming. Here, a developer writes an algorithm on their workstation. The deployment circumstances and interactions with other systems are an afterthought. Often this developer does not deploy the code themselves, this is done by another team who don't understand the internals of the code.
1. Play through the first page of levels of TIS-100. This is a game you can buy on Steam. After spending a few hours working on problems in this, I felt a hard-to-describe mental shift that removed the intimidation of assembly.
2. Work through the first half of /Programming Boot Sector Games/ by Toledo.
3. Designing and building a simple instruction architecture, implementing it as a VM, writing an assembler for it.
The ChibiAkamus tutorials on youtube may be worth a look, also.
If you try for TIS-100, give yourself a decent chance to get into it. Print out the manual, calmly read through it with a biro, don't let yourself give up easily on the first few problems.
> Every deadline can be met if employees are "eager to
> please" and will work unlimited overtime hours for free.
No amount of pressure or willpower can get software done if the team is badly aligned, working on the wrong problem or simply flailing. The message I take from the parent post is not about estimation theory, it's that the project manager created a delivery culture across a large team.I don't think the open and close calls respect non-blocking on linux when operating on files (specifically files, not sockets - for sockets the return is always quick as far as I know). From man open(2), "I/O operations will (briefly) block when device activity is required, regardless of whether O_NONBLOCK is set". And my recollection is that they will non-briefly block if the problem is a hanging NFS mount.
"What are you going to do when they don't return? Accumulate dead threads and inconsistent shared application state?"
Good point. My practice is to use child processes. These can be killed, and so I do not run into this. But subprocesses ratchets up the amount of work to be done, because you then need to do async IPC. So it's now a lot of extra work. It's even worse for multiplatform stuff because now you are exposed to platform differences (e.g. select is suboptimal on Linux, but poll is not available on Windows).
As you say, using threads within same proc would lead to stale threads. In some contexts this would be tolerable but it is not nearly as simple+clean as I presented.
Thinking hard about addressing this on Linux brings me down, every time. I hope io_uring will make pure async practical within a single process. Even if it does, the multiplatform story will remain complex. I am not fond of your disregard for user data in the (tangential) discussion about disappearing filesystems, but you have won me over to embracing the main thread in this context.
That criteria is established here - the OP is about an issue affecting paying end-users! Premature optimisation is not relevant - the software is failing.
It is unsafe to make fair-weather assumptions about customer systems.
Consider a common software failure: where the user is saving data to a SMB or NFS partition, and then there is a loss of connectivity to that file-server, and the developer has done whatever I/O they need on the main thread. This causes data loss.
You /should/ be able to assume (1) reliably fast return from core async-coordination syscalls (e.g. select, poll), and (2) that you will not suffer process or thread starvation caused by someone else. Respecting those constraints, it is good practice to isolate sync calls to a non-main thread in order to catch when they are not returning. This robustly covers both common scenarios (like the missing-filesystem) and obscure scenarios like the one in blog post.
The concepts raise the standard of policy development. Consider how much easier it is to discuss a proposal thanks to 'The Tragedy of the Commons'. Those few words serve as a shorthand for a dynamic. Without it you might need to spend half an hour stepping people through the dynamic each time you wanted to refer to it, and you would lose people along the way.