1,059 karma · joined August 31, 2014
But standard combustion processes output air with a single-digit percent of CO2, and there seems to be no cheap way to change that or separate it from air.
It was not too bad, but my memory of Riven is so much stronger. Maybe I should replay it instead, just to walk through this beautiful world again, even without solving all the puzzles (the puzzles are IMO not why you play it). Riven evoked this constant feeling of wonder with the sounds and short cut-scenes adding a lot to the atmosphere.
There was this place where you walk down towards the water with a beast sitting there in the sun, and that scene almost has a smell to it. Or maybe my memory is colouring it all rosy now.
That said, the game mechanics are really well done and give you options for creative problem solving. For example your pilot increases the chance to evade missiles. Unless he is busy extinguishing a fire in another room. So instead you can open a door to space and power down your own oxygen supply. And use that power to charge a second weapon.
This is the kind of optimization I might have done in C 10 years ago. But coming back from Rust, I wouldn't consider it any more. Rust, despite its focus on performance, will simply not allow it (without major acrobatics). And you can usually find a way to make the compiler optimize it out of the critical path.
(Okay probably those are not ready to be used as NN weights if the activations are not binary too, but... the gap to what CPUs already can do is getting smaller.)
I think micro taxation on all transactions (including at ATMs) would work better. Easier to explain, harder to avoid since you tax both sides of each transaction.
There is no evil master plan. The processes that lead to self-exploitation will sound reasonable and well-intended. (If this wasn't the case, people would refuse to adapt it. Most people don't like exploitation when they see it.)
For example, in most of Europe there is a law that requires employees to record their working hours. This law was created to prevent (unpaid) overtime, and it does that. Now company X implements this by making you write down how many hours each day you worked towards which task. Doing this every day makes you think where you put this one-hour chat you had with a co-worker. It was nice, but which task did it contribute to? (It didn't...?) If you bother to ask, everybody will actually encourage you to have those talks, that it is even in the interest of healthy company culture, and remind you that maybe it's part of the paid break (you didn't forget you have that, did you? it was never anyone's intention that you skip your break). Nobody will be responsible for nudging people towards efficiency. It's all the fault of the individual who feels pressured into efficiency. It was never anyone's intention to prevent you from having those occasional nice chats, and nobody will stop you if you keep doing it.
Still, every day you get to think about how long it took and which task it belongs to, and it feels a bit like lying to just add the time to a random task. This kind of habit can shape your thinking.
Posts are not just going got flood over, though. Each Mastodon instance has its own local view into the fediverse, and discoverability depends on what other users on your instance have subscribed to. Some instance admins will decide to not host anything Meta, or limit discoverability, as they do with other servers.
After we hit the third "Linux"-bug that turned out to only happen in WSL, I suggested to maybe just install Linux in a normal VM. Clunky, yes. But at least it has a clear boundary. Unless you move something across it, everything will just work.
Not sanity, maybe. But security? How much more would it take to declare a nuclear meltdown: https://alexgaynor.net/2020/may/27/science-on-memory-unsafet...
I'm not into TDD, but I'm absolutely into "never skip the red phase".
After fixing a bug or writing a test, I always revert and repeat the test. Same when testing manually (except for the absolutely trivial). You wouldn't believe how often the test then just passes. It's the hygienic thing to do. It's so easy to fool yourself.
About half of the time I realize my test (or my dev setup) was wrong. The other times I learn something important, either that I didn't fully understand the original problem, or my bugfix.
Not very technical, not about Go tactics either, but it's just a very well-done movie about the people involved.
Then try staying in control with an unbalanced ship, or after you inevitably smashed one of the thrusters into a rock. It's a pretty space-nerd game too, they simulate details like reaction wheel saturation.
If that's true, then I'm surprised they only see a 10x speed-up. I would expect more from only compiling that loop for the CPU. (Comparing to interpreted Python without numpy.) Given they already have a numba version, why not compile it for the CPU and compare?
Also, they say consumer CPUs have 2-16 cores. (Who has 2 cores these days?) They go on suggest to rent an AWS GPU for $3 per hour. You're more likely to get 128 cores for that price, still on a single VM.
Not saying it will be easy to write multi-threaded code for the CPU. But if you're lucky, the Python library you're using already does it.
Ha! I wish CPUs were still that simple.
Granted, it is legitimate for the article to focus on the programming model. But "CPUs execute instructions sequentially" is basically wrong if you talk about performance. (There are pipelines executing instructions in parallel, there is SIMD, and multiple cores can work on the same problem.)
We happen to know how LLMs are trained, and from the loss function it's pretty clear that blood sugar will not magically enter the equation, nor even motor neurons, except as abstract knowledge that the model can reason about.
A LLM trained on western texts will, best-case, simulate a western abstract reasoning process, which usually puts more focus on independent/isolated explanations compared to other cultures. From that training data it will not spontaneously start simulating a generic human brain that was separated from both its cultural knowledge and its spinal cord.
At least in the same sense that the Mandelbrot fractal does not contain a picture of the maxwell equations. You may actually find that picture, but by looking hard enough in a complex enough system, you can find just about anything else you want.
The human brain doesn't even have the concept of written language, that's all culturally learned knowledge.
I once got an bigger "upgrade" for my small wacom tablet, but it only collected dust. It used too much space on the desk to always keep it ready, and the larger active area meant too much travel distance when using the pen as a mouse.
And concerning Wacom, they were the first to have someone working on Linux drivers, and the only one for a long time, back when tablets were new. Not sure how it is today.
When I try to imagine that, I can't help it. I see leaves mounted on top of a tree. Using solar power to bind carbon into a dense trunk package below. Ready to be carted off and hidden below grounds.
Also, given that we can't find anyone willing to pay for carbon capturing right where it is most dense, at the source, how are we going to find the will to pay for capturing it from thin air at much higher cost...