Ths is a massive misunderstanding of the technology. First of all, the amount of hydrogen in the reactor is tiny. The magnetic confinement severely limits the density of the plasma. The inner containment vessel is a ultra high vacuum chamber. The chemical energy that would be released by a reaction between the hydrogen in the reactor amd oxygen from the air would be less than what is released by popping a hydrogen filled balloon with a lighter.
The truly concerning failure modes would be related to release of radiation or activated materials. But that would require damaging the reactor in ways that the reactor is incapable of imparting on itself.
> chemical energy that would be released by a reaction between the hydrogen in the reactor amd oxygen from the air would be less than what is released by popping a hydrogen filled balloon with a lighter
Thanks for the correction. If you're breeding lithium in the walls, might that be an incendiary concern?
The breeding blanket is entirely contained inside a vacuum vessel, so there isn't any oxygen to react with. Also, the are many blanket designs, but the lithium is never present in its elemental form (precisely because it would be very reactive), but in a stable chemical bond with some neutron multiplier (like lithium-lead alloys or beryllium ceramics). In some design the lithium is even immersed in the coolant itself, which is high pressure helium, so it's not going to ignite in any reasonable way.
> breeding blanket is entirely contained inside a vacuum vessel, so there isn't any oxygen to react with
When the vessel works. If the vessel breaches, that lithium could ignite. Note a showstopper. But I suppose a risk to be thought about by the engineers (probably not by policymakers).
Commonwealth Fusion Systems plan to use lithium in salt form FLiBe, a molten salt made from a mixture of lithium fluoride (LiF) and beryllium fluoride (BeF2). It does not violently react with air or water.
There seems to be a number of different prototypes of blankets, but the average operating temperature seems to be 300-700C. Adding oxygen to some of these designs while that hot may cause metal burning. This said, many of them are ceramic designs and would likely resist combustion.
With all that said, it seems to be way less 'dangerous' material than would be in your average nuclear reactor, making it more of an industrial accident versus a planet contaminating mess.
You are ignoring that the plasma would ignite the O2 in the air. You are also ignoring what happens when several hundred MW of energy (at about 1,000,000C) under pressure is released instantly. Anytime you have a powerplant with enough energy to be economically viable, releasing that energy at once will be a problem. Even FF PPs can explode quite violently.
1. All that AI really does is a (partially) randomized exploration of the space that has been spanned by existing music. AI creativity, as far as it can be said to exist, is limited by this. You, on the other hand, are human and not bound by any of these limitations. You are free to explore wild things that no AI can do. Just as a completely random example, you could go out, record noises your environment (even if it's just with the smartphone), grab interesting parts, chop them up, process them and turn them into unique new instruments. Bang on random stuff that has a nice ring to it. Record background hums, apply filters and envelopes to them etc. And there are so many other ways to produce unique creations.
2. Most importantly, music is a form of human expression. It is able to capture the human condition in a unique way. As a human, you can express these things genuinely through your own emotions, experiences, memories etc. AI systems can only produce hollow facsimiles of this. Regardless of whether you are conscious about it, every piece of music that you create is a reflection of you: your thoughts, your emotions, your process. And that imparts the true value on your creations.
> Just as a completely random example, you could go out, record noises your environment (even if it's just with the smartphone), grab interesting parts, chop them up, process them and turn them into unique new instruments.
I'm not sure if you already knew this, but this is actually a thing already - it's been called "Botanica" and there are a bunch of cool tracks floating around.
20% to 30% slower would be amazing for all the extra runtime work that is required in my limited understanding. This would be good enough for a whole lot of serious applications.
Yes! Even closing the windows of programs that users no longer need is hard.
It's easy to develop a disconnect with the level that average users operate at when understanding computers deeply is part of the job. I've definitely developed it myself to some extent, but I have occasional moments where my perspective is getting grounded again.
I don't think that's representative of most non-CS professionals. Most people in the fields I know (mostly professors, medical doctors, and businesspeople) can use google chrome, word, powerpoint, and a little of excel decently. There are the occasional few who confuse spreadsheets and databases, but no one who thinks shutting down computers or closing windows is hard. Heck, my ageing dad managed to troubleshoot his printer without any help, and he has no formal computer experience whatsoever.
HN has a long history of patronising the "average user" in the guise of paternal figures who don't realise that what they are doing is belittling the vast majority of tech users. I'm guilty of it myself. But they're capable of a lot more than we think they are.
Ultimately, it comes down to the willingness people have to learn new things. If they're curious enough to think about how things work, they'll be fine.
I'm not doing this to be patronising, more like telling people or myself that assumptions i make, are just not necessarily true for everyone.
And weirdly enough, a Task like sorting a file with data in it, if you are not a professional, windows offers very if not non single way of doing this. You would need to understand file types, understand that csv can be imported for excel, you need excel, than you need to understand excel how to sort stuff in it.
The ffirst thing I do in Excel is select the pseudo table and click on table -> insert to make it a sortable / real table. I showed this to every one in my Team full of studied CS people because non of them knew this.
Well, I didn't mean for this to be patronizing, but rather as a warning that not everybody is at the same level and the spread is huge. I see it often enough.
Racing like in Formula 1 is extremely different from normal product design: each Formula 1 car has a user base of exactly 1: the driver that is going to use it. Not even the cars from the same team are identical for that reason. The driver can basically dictate the UX design because there is never any friction with other users.
Also, turnaround times from idea to final product can be insane at that level. These teams often have to accomplish in days what normally takes months. But they can pull it off by having every step of the design and manufacturing process in house.
The same line of reasoning leads to constitutions and laws being jokes, too.
The simple fact is that rules matter if and only if they are enforced effectively by a community. And power is the ability to direct and control that enforcement.
The international order has declined in the past one or two decades because the UN security council was hamstrung by the enormously powerful veto rights held by Russia, China and the U.S. This has slowly emboldened those countries to de-value the UN and pursue their own interests.
It is not that laws are being jokes or not because are not in place, but ends being that way when they are in place and they are blatantly ignored, specially for some power groups or communities. Then they can break those laws with impunity, and then others follow example with varied success, but still, those laws are already a joke.
When you look at the DM's guide guide to the game, one of the very first rules it teaches is that the fun trumps being a stickler for the rules and the DM is free to bend and break rules for a better plot, and even encouraged to do so.
D&D has a strong narrative aspect when you look at the published adventure modules. There are usually plenty of characters to interact with in some way or another and some quests can be solved entirely by following the breadcrumbs offered up through them. But the DM needs to role-play all of these characters and do a lot of improv to make this work. This isn't so easy.
Also, combat in D&D is a slog. Whereas turn taking outside combat is rather fast and loose, the game turns into this enormous ceremony once the words "roll initiative" are spoken. The effect is that combat can take up a lot of playtime relative to the non-combat role playing, while often also leading to less overall quest progress per time.
Unless I'm overlooking something, the demo only requires DOSBox to have a machine with predefined execution speed. There are no DOS interrupt calls that I can see. Other than that, the program could probably even be trivially modified to fit in a floppy disk MBR and could potentially run without underlying OS.
To be more exact (in an excessive way), it uses the BIOS's code to set the video mode (INT 10h) which is probably a few dozen bytes (at least?) although I have been remiss at not ever reading them. And it depends on DOS configuring the memory space to leave an INT 20h call (to terminate the program) at a place that's easy to RET to. But, yeah, very little extra. But I'm not being negative at all and this is pretty nice code and on the impressive side of 256 byte demos from the 80s and 90s (and onward).
Yes, this is very minimal; if it were self-booting the INT 20h call wouldn't be needed, but there's no getting around the INT 10h, unless you specialize for very specific hardware.
The entire 5150 BIOS fit in 8k, so even if it were laden with BIOS calls (which it's not) then that would be an upper-bound.
Also, MIDI - I'm not very familiar with demo programming, but I guess using MIDI saves a lot of bytes compared to trying to do something similar with only the PC speaker?
Sure, it saves a lot of bytes compared to PCM encoded wave-form data, but it's not really cheating anything unless we also consider the red, blue and green parts of the computer monitor to be cheating because we're not outputting colours as raw wavelengths, but instead the monitor is decoding compressed signals into actual colours.
What is this "cheating" you speak of? I wasn't expressing any judgement, just saying that using MIDI helps save bytes. But now that you mention it, the bitmapped graphics that we take for granted nowadays also help (it gives you a whole memory space to work with that doesn't count towards the length of your program, rather than having to "race the beam" -https://en.wikipedia.org/wiki/Racing_the_Beam). Not sure if there's a demoscene for the Atari 2600, but that would probably be the most "bare-metal" you could get...
You have the totally wrong expectations here. Some service that requires citizens to buy and bring their own devices in order to use a service will by definition always be exclusive. Whining about lacking compatibility with some niche sbowflake devices is just inappropriate in this context. The only solutiin is to require an actually convenient fallback for those otherwise excluded from that service.
The limited selection of attestation providers can be criticized for many other reasons, though.
Your disdain isn't helpinh you here either as you're just as wrong as parent.
Such public utilities ought to always prioritize privacy, platform-independence, and empowering market competion long- and short-term. And to achieve that you need to start at the design level.
In this case, clearly, you either have to avoid relying on app attestation or lay the foundation for an unrestricted number of independent chain of trust frameworks.
The latter, of course, is a policy-level issue, but the ones responsible for the design and development are the ones who need to pass such concerns up the chain.
You have the right starting point, but the wrong conclusion. Government services need to be inclusive of everybody. But you simply cannot build technical solutions that put technical requirements on devices owned by the users in a way that the service is sufficiently inclusive. That is just a fact.
If you want to be critical of the outcome on compatibility grounds, forcing a grind to increase technical compatibility is the wrong thing to ask for. That must necessarily always leave some people behind. The only honest alternative positions on that front are (a) the government issues the tech to everybody itself or (b) the government doesn't build advanced systems at all.
The German government offices rely on a lot of quaint-looking paper based processes, but they have one thing going for them: working through them can be done with pen and paper - tools that are available for cheap and broadly compatible. It's probably not such a bad thing after all?
Inclusivity is secondary here. Moreover, it's just fallacious to argue the nation has to give up on its own rights and principles and be content with whatever the market provides.
The truly concerning failure modes would be related to release of radiation or activated materials. But that would require damaging the reactor in ways that the reactor is incapable of imparting on itself.
Overall, the technology is remarkably safe.
reply