Getting pristine resampling is insanely expensive and not worth it.
If you have a mixer at 48KHz you'll get minor quantization noise but if it's compressed already it's not going to do any more damage than compression already has.
And we learned zero from the change after shutting down the Purdues. The electorate just wants to see drug users punished, not treated. Even though treating cheaper, more humane, and has way better outcomes.
Fuck him and people like him. There's no good reason to have a 70 hour work week other than insecure management needing it as a security blanket like some nine year old child. Researchers keep showing how human beings have a maximum productive time each week but instead he and his ilk want to go against this research for the sheer optics of it.
Errors work just like exceptions especially if you use the ? operator and let the error bubble up the chain. This is the Rust equivalent of an unhandled exception and the ripcord being pulled.
In C++, functions are error-colored by default. You write "noexcept" if you want your function to be infallible-colored instead.
(You usually want to make a function infallible if you're using your noexcept function as part of a cleanup path or part of a container interface that allows for more optimizations of it knows certain container operations are infallible.)
Rust makes infallibility the syntactic default and makes you write Result to indicate fallibility. People often don't want to color their functions this way. Guess what happens when a programmer is six levels deep in infallible-colored function calls and does something that can fail.
.unwrap()
Guess what, in Rust, is fallible?
Mutex acquire.
Guess what you need to do often on infallible cleanup paths?
Probably because our desire to help and not let down a person we care about gives us courage. That courage serves as motivation to go outside our comfort zone.
Yeah, it would be so much better if it was American-made, because as everyone knows there are no corrupt people in the US and every person of Russian descent is a spy for their motherland's government (:
Yes, it would be better if it was American made, because the US government has lesser capability to compell otherwise independent developers to do their bidding.
> US government has lesser capability to compell otherwise independent developers to do their bidding.
Are you sure about this? The US, like most countries with extensive intelligence capabilities, does not have a good track record of convincing their citizens of doing shady things [1].
You missed my point, which is that all governments exist to oppress by design, it's literally what governments are, they are businesses that monopolize violence. Some people, esp. people of the Western world are too arrogant to admit it. Personally, I would honestly rather trust someone who is aware of that fact over someone who isn't.
Look, I'm as much an enjoyer of Kropotkin and von Mises as the other guy and torched more then zero regional police HQs in my life.
You are right in principle, but there is a varying degree to which different governments actually oppress people and there are certain patterns of what to expect from which.
I would not trust american company, like msft to not snitch to me to US government either, but the likehood of random shmuk being coopted is much more likely in one case as opposed to another.
> the likehood of random shmuk being coopted is much more likely in one case as opposed to another.
I don't think Russians actually live in fear of the big brother, I wouldn't be friends with so many Russian femboys if that really was the case. But what do I know, it could all be a conspiracy.
Edit: I also don't understand how torching police hqs makes the world a better, more peaceful place. At best, you'll just end up creating another monopoly on violence… @.@
Why such a simple UI utility app needed a VSCodium/Electron UI? The author seems to be well versed in Win32 API, so why not just learn the GUI part as well? It's not that hard.
The reason the Windhawk UI is based on VSCodium is mainly for the mod editing functionality. VSCodium with clangd are used for C++ intellisense out of the box.
You might say that many users don't care about mod development and don't need it. I agree, and I have it on my list to create a lite Windhawk version which doesn't depend on VSCodium.
Note that VSCodium is only used for the UI. When Windhawk is running in the background, its memory consumption is a couple of MB.
as opposed to any other updater on your system...?
> Tech Enthusiasts: Everything in my house is wired to the Internet of Things! I control it all from my smartphone! My smart-house is bluetooth enabled and I can give it voice commands via alexa! I love the future!
> Programmers / Engineers: The most recent piece of technology I own is a printer from 2004 and I keep a loaded gun ready to shoot it if it ever makes an unexpected noise.
Absolutely. Sufficiently capable LLMs can mass produce exploits against whole ecosystems; recent Anthropic post moves the risk needle from ‘theoretical’ to ‘realized’. Any auto-updating software is running a risk of its cdn and/or build forge being compromised. Scary times.
This is not an updater. Due to the sensitive nature of Windhawk, it has no auto-updating mechanism, only update notifications (this file is part of that).
This technique is surprisingly powerful. Yesterday I built an experimental cellular automata classifier system based on some research papers I found and was curious about. Aside from the sheer magic of the entire build process with Cursor + GPT5-Codex, one big breakthrough was simply cloning the original repo's source code and copy/pasting the paper into a .txt file.
Now when I ask questions about design decisions, the LLM refers to the original paper and cites the decisions without googling or hallucinating.
With just these two things in my local repo, the LLM created test scripts to compare our results versus the paper and fixed bugs automatically, helped me make decisions based on the paper's findings, helped me tune parameters based on the empirical outcomes, and even discovered a critical bug in our code that was caused by our training data being random generated versus the paper's training data being a permutation over the whole solution space.
All of this work was done in one evening and I'm still blown away by it. We even ported our code to golang, parallelized it, and saw a 10x speedup in the processing. Right before heading to bed, I had the LLM spin up a novel simulator using a quirky set of tests that I invented using hypothetical sensors and data that have not yet been implemented, and it nailed it first try - using smart abstractions and not touching the original engine implementation at all. This tech is getting freaky.
The mainstream coding agents have been doing this for a long time.
It helps to give it a little context and suggest where to look in the repo. The tools also have mechanisms where you can leave directions and notes in the context for the project. Updating that over time as you discover where the LLM stumbles helps a lot.
Apparently it's also shit. There was a discussion about it a few days ago that contains multiple project maintainers pointing out deepwiki didn't get their repos at all https://news.ycombinator.com/item?id=45884169
Normally this would be handled by a wider synchronized network. The EU has a continent wide synchronized network and the UK isn’t part of it.
There are also other ways to store energy. For polar regions sand batteries are capable of storing heat for months. High grade heat to the point they can siphon off that heat for power generation.
The interconnectors between UK and the continent are HVDC.
As such they are essentially massive switching-mode PSUs, and there is no possibility of having a synchronised connection, as the AC has to be synthesised, following the local spinning iron.
But also europe isn't that large. When there is no wind in the UK, there is no wind in France or Italy. Which means not only do they not provide diversification, they will import at the same time.
If you have a mixer at 48KHz you'll get minor quantization noise but if it's compressed already it's not going to do any more damage than compression already has.