Isn't circular funding how the entire economy works?
I can see how you could make an argument that this particular ouroboros has an insufficient loop area to sustain itself, or more significantly, lacks connection to the rest of the economy, but money has to flow in circles/cycles or it doesn't work at all.
Parties in an economy don't normally buy something that they sell at the same time. It's hazier than that here, but still looks like Nvidia is buying GPUs from itself via OpenAI and Oracle.
Btw there are examples involving sanctioned economies. Most US saffron comes from Spain, all of whose saffron comes from Iran. Azerbaijan exports way more gas than they produce, cause they also buy from Russia.
Only when using non aligned intwrests, like government funding roads.
When interests directly align and parties are largely owned by the same people, its wash trading.
The point of wash trading is to make activity increase the value of an asset via a netzero activity. Since nothing is generated from the activity its circular, eg, nothing physical changes hands.
Crypto trading is the golden child of wash trading as the primary mode of increasing the value of an asset.
Its unsurprising then that the company that got rich on crypto wash trading is doing its own attempts to drive artificial demand.
Author here, kinda sorta. I should've been a bit more specific than that.
You can have a profile showing a function taking up 99% of the time, but when you dive into it, there's no clear bottleneck. But just because there's no bottleneck, that doesn't mean it's optimized; vice versa-a well-optimized program can have a bottleneck that's already been cycle-squeezed to hell and back.
What I wanted to say was that a spiky profile provides a clear path to optimizing a piece of code, whereas a flat profile usually means there are more fundamental issues (inefficient memory management, pointer chasing all over the place, convoluted object system, etc.).
It sounds like a flat profile essentially is a local optimum, compared to cases where there's a path "upwards" along a hill to some place more optimal that doesn't require completely changing your strategy.
That's actually a good observation, yeah. It's often the case that you dig deeper and deeper and find some incomprehensible spaghetti and just say "fuck it, I'll just do what I can here, should be enough".
I've seen a few of these in my career, if I understand the author correctly. You have a big ball of mud that can theoretically be 10x or 100x faster, but the costs are diffuse and can't be solved by just finding a hotspot and optimizing it.
It often happens for good reasons. Features get added over time, there are some scars from a mocking framework, simpler (faster) solutions don't quite work because they're supporting X which supports Y which supports Z (dead code, but nobody noticed), people use full datetime handling when they mean to access performance counters, the complexity of the thing means that you blow your branch prediction cache size budget, etc....
The solution is to deeply understand the problem (lots of techniques, but this comment isn't a blog post) and come up with a solution, like a ground-up rewrite of some or all of the offending section.
It's ACPI - most laptops ship with half-broken ACPI tables, and provide support for tunables through windows drivers. It's convenient for laptop manufacturers, because Microsoft makes it very easy to update drivers via windows update, and small issues with sleep, performance, etc. can be mostly patched through a driver update.
Linux OTOH can only use the information it has from ACPI to accomplish things like CPU power states, etc. So you end up with issues like "the fans stop working after my laptop wakes from sleep" because of a broken ACPI implementation.
There are a couple of laptops with excellent battery life under linux though, and if you can find a lunar lake laptop with iGPU and IPS screen, you can idle around 3-4W and easily get 12+ hours of battery.
LG Gram user here with Debian as a daily driver. Can confirm, maybe not 15h, but I don't think about charging. Plus, it's super stable, not a single crash or hang-up over years. It just works. I hope LG will keep this up and not mess up next iterations of the hardware.
I had an LG gram before the battery in it gave out and now it won't boot with the battery plugged in. The battery life was amazing, it always slept properly, etc.
Now I have a Framework. It randomly reboots when I close the lid, the battery life is terrible, etc. I live with it since I like the idea of a repairable laptop.
What's standing in the way of doing something like NDISwrapper but for ACPI? Just that nobody with ghe required skills has spent the effort? Or something technical?
If the observable behavior is bad Linux performance, it's a Linux problem.
There's a saying in motorcycling: it's better to be alive than right. There's no upside in being correct if it leaves you worse off.
There are ways to make things better leveraging the Linux way. Make more usable tools for fixing ACPI deficiencies with hotloadable patches, ways of validating or verifying the patches for safety, ways of sharing and downloading them, and building a community around it.
Moaning that manufacturers only pay attention to where their profits come from is not a strategy at all.
Decompile your ACPI tables and then do a grep for "Linux". You are likely to find it, meaning the vendor took time to think about Linux on their hardware. Some vendors take the time to write good settings and code for the Linux ACPI paths, some dump you into no-man's land on purpose if your OSI vendor string is "Linux".
It's quite literally a vendor problem created by vendors leading anyone that doesn't run Windows astray in some cases.
If you run Linux, then dare to change your OSI vendor string to "Windows", you've entered into bespoke code land that follows different non-standard implementations for every SKU, where it's coded to work with a unique set of hardware and bespoke drivers/firmware on Windows. You also forgo any Linux forethought and optimizations that went into the "Linux" code paths.
My point is that from the Linux side, you're damned if you and damned if you don't no matter how you tackle the issue. If the layer above Linux is going to deliberately malfunction and lie on the Linux happy path, or speak some non-standard per-device driver protocol if you lie to use the Windows path, there's not much that can be done.
It's only a "Linux problem" if you're trying to run Linux on hardware that is actively hostile to it. There are plenty of vendors who supply good Linux happy paths in their firmware, using their hardware is the solution to that self-imposed problem.
I think the correct strategy in this case is to return your laptop to the store if it has linux compatibility issues, and keep trying until you find one that works.
i.e. don't support vendors whose laptops don't work in Linux.
I thought this article would first start with the most essential question: "How to decide what you need on your devboard".
Without that critical piece of design work, you may as well call this "How to build a Raspberry Pi Nano from scratch". Which, to be fair, is also a good article to write.
But step 1 for really building a dev board is answering the question, "What do I need from this that I can't get from a $5 Amazon purchase?"
"I built my house without any inspection or licensing and connected to the electric grid"
Where exactly do you live? I'm not saying you're lying, but this smells like a tall tale. You can easily buy solar panels and batteries, and if no government inspectors are coming by anyway, then it doesn't matter.
Maybe what you're saying is, "my power company wouldn't let me use grid-tied solar without it being permitted." ?
>"my power company wouldn't let me use grid-tied solar without it being permitted." ?
Nah they didn't give a shit what I connected it to. I literally stubbed a 200 amp service entrance on vacant land then just went wild connecting it to whatever I like. I shot the shit with their engineer when they ran secondary off the power pole and that was it, I've never seen them again.
> no government inspectors are coming by anyway, then it doesn't matter.
I don't know for certain but having an unpermitted solar panel visible via satellite would likely trigger a visit.
Great, so it sounds like installing unpermitted solar at your house is about as illegal as jaywalking, and you probably shouldn't worry about it so much.
What law governs this? I'm familiar with a lot of restrictions on grid-tie systems, but I've never heard of it being this strict for something that could (presumably) be done without a back feed.
I mean, are you saying that someone sticking up a few panels+batteries to run an electric fence, gate, and camera system has to have permits?
For example, here is the one that to install certain PV you need permit with roof and building plan, which is impossible on my house because I have none (literally built my roof off the cuff after thumbing IRC).
People have guns in all of the US. Sure, AZ ownership might be around double that of CA, but that's just going from 1 in 4 to 1 in 2. The odds are high either way.
> The I-team also found six sergeants in the Sheriff's Office who live out of state - in Idaho, Nevada, Texas and Tennessee. Two of them work on the bomb squad where they made almost $600,000 in pay and benefits last year.
>When I send an email that isn’t bounced back, or better yet, get an auto reply with a ticket number, I’m a lot more certain it’s going to get read.
An "auto reply with a ticket number" is not a feature of email, it is something that someone built that could just as easily be attached to a webform. Plenty of webforms work that way, I have personally built some in my career.
Is there any intrinsic value whatsoever in the DNA or SNPs themselves? Or is it just the link between your name and your DNA that is so concerning?
It seems like you could do lots of useful things without having a name attached to any particular sample. There must be some kind of differential privacy approach here that would work well.
> Imagine an AI engine like a block of swiss cheese. New, original content that fills one of the holes in the AI engine’s block of cheese is more valuable than repetitive, low-value content that unfortunately dominates much of the web today.
Great statement in theory - but in practice, the whole people-as-a-service industry for AI data generation is IMO more damaging to the knowledge ecosystem than open data. e.g. companies like pareto.ai
"Proprietary data for pennies on the dollar" is the late-stage capitalism equivalent of the postdoctoral research trap.
I can see how you could make an argument that this particular ouroboros has an insufficient loop area to sustain itself, or more significantly, lacks connection to the rest of the economy, but money has to flow in circles/cycles or it doesn't work at all.
reply