It is not about memory safety or anything like that. It is about simplicity.
If you say "you can't do x with y in C++" you will get an "yes you can, you just use asd::dsadasd::asdadqwreqsdwerig_hfdoigbhiohrf() with weaorgoiawr flag". From what I have seen from Rust, it is similar.
I don't want to fill my brain with vim bindings.. cough.. Rust ways of doing something. I just want to code my hobby game engine v7.
That said, I am happy to use software written in it. Even though the evangelists can be really annoying.
In my experience the hardware requirements are whatever the file size is + a bit more. Cpu works, gpu is a lot faster but needs VRAM.
Was playing with them some more yesterday.
Found that the 4bit ("q4") is much worse then q8 or fp16. Llama3.1 8B is ok, internlm2 7B is more precise. And they all hallucinate a lot.
In my opinion they are not really useful.
Good for translations, to summaries some texts, and.. to ask in case you forgot some things about something.
But they lie, so for anything serious you have to do your own research.
And absolutely no good for precise or obscure topics.
If someone wants to play there's GPT4All, Msty, LM Studio.
You can give them some of your documents to process and use as "knowledge stacks".
Msty has web search, GPT4All will get it in some time.
Got more opinions, but this is long enough already.
When i think of "desktop integration", i think about drag and drop not working between `ark` (a QT program) and `thunar` (a GTK program), and i think of folk writing blog posts about window theming. (there's also notifications, icons, etc, blablabla, that keeps getting worse (freedesktop is, that is))
To be honest, i don't care much about how programs look. But i do know many people do care.
I never said it doesn't work. And yes, i do have "anything substantive" against it. The fact that, as i mentioned, it is just a package manager. And a bad one.
> From what I have seen, most of the opposition to Flatpak comes from the same place that the one to systemd: fear of change.
This is what pisses me off. You, nor anyone else, can tell everyone else what >I< think or feel. It's not fear, nor fear of change, nor any other dumb ass reason people who think like you think it is. I hate it because it's just a package manager. I hate it because, when all the reasons against it are brought up, something nebulous like "security" or something quazi-psychological like "fear of change" are brought up in defense of it.
The real problem with flatpacks is that they don't solve the real problem, and they do it poorly.
Want to solve the problem of your program not running on multiple distros, or not running in 5 years ? Then look at why that is. For example; it's not that the zip file format will change, so why must i recompile my program every time libzip changes ? Or X11 to wayland transition; why does my program have to even care about that when all i want is a window and an opengl context ? (bdw the solution to the latter is SDL2)
Let's look back when flatpack started. Why did it start ? Maybe because GTK3 changed it's API ever so often ?
Linux doesn't have a good GUI toolkit. THAT is the biggest problem here.
I just fucking hate the "ohh, you just don't like change" people. That dismisses all further discussion. That is the real "hate" that people like you blame others of.
It says 72% efficiency, so over 400W of heat at full load.
Inverter to a normal PSU would be about the same, if not worse. It could be that it raises the voltage then drops it back down to 12V, but i'd sooner think it's just cheaper mosfets.
Anyway, these kinds of converters can usually regulate themselves.
Thief the dark project supports HRTF through OpenAL Soft[0].
Head related transfer function is the.. modeling of how sound waves bounce of your body (shoulders, ears, breast). And it's a part of how we determine where a sound is coming from. Other part is the timing, as in the difference of phase of sound coming in one and in the other ear. Amplitude(volume) is also a part, probably, but we are much more sensitive to difference in phase then amplitude.
If you want to start researching in these things; the start is probably "impulse response" as well as.. a lot really (systems and signals is a heavy book that i should read one day). Just remember that everything is a spring.
As for practical modeling in 3D games and such. The problem is almost the same as global illumination. You would need to model the whole environment and how it responds to sound (absorption, reflection, idk probably even the speed of sound in various materials to be accurate). A great youtube person has a couple videos on whitepapers about this [1-2](the 2 is more practical). Valve bought a company that played with these things, but idk if anything came out of it (iirc it is part of the steam framework now).
Well, it seems to work fine (xorg.conf tearfree option, that is). AFAIK wayland compositing also has the problem that clients don't know when they should be done with rendering, as in when the flip is going to happen. I don't know much about how it (wayland, DRI) actually works (as in, can the "client" just render where the compositor told DRI it should without involving the compositor, or does it have to tell the compositor when it rendered).
Screen tearing under X11 is more or less not a problem anymore. HIDPI, yes, but only for multiple monitors (maybe even just programs that don't support it properly ?). Security... eh, yes and no (Xorg can be ran as a normal user).
The actual good thing about Wayland is that it simplifies things. While the bad thing is that it needs some kind of extensions for even the basic things a desktop needs, and that (AFAIK) freeGNOMEdesktop is in charge now.
Electrons are.. we don't really know what they are. What we do know is that they have a "charge" around them, an "electric potential", and that they repel each other.
"Electricity" is one of those terms that doesn't really have a specific meaning. From what i see, we use it to group all the electromagnetic things that.. i guess deal with "loose" electrons.
As for the actual question, first i'd have to explain "electric current". Current (in Amperes) is just the flow of electrons. As in how many electrons flow through some plane over time. In practical terms; how many electrons flow through a wire, where the "plane" is the diameter of wire.
Voltage is a force. Imagine that the electrons weren't points that repealed each other, but were instead balls. You fill up a pipe with balls and push on one side of it. The force you are pushing with is the "voltage". You can also imagine this with water, where the pressure is.. well it's all the same really when we get "low" enough. Note that electrons, unlike balls and water, don't really have mass.
Wattage is power. It is how much energy is.. transmitted over time. You pay your bills in Watt * Hours, but you might as well pay it in Joules. It shows you how much power you can expect from a machine. Wattage is calculated by multiplying Voltage and current, as in how hard you push and how many electrons you push per time. In water terms, it is the speed of the water multiplied by how big the river is (or pipe).
So they are useful units of measurement, just as any other metric unit of measurement. In fact Ampere is one of the seven basic units of measurement in the Systeme international d'unites (SI, often called "metric").
The one that actually hurts you is the current. The thing is that Voltage "pushes" the current, so one might rightfully think that "high" Voltage is the dangerus one. But again you can touch a 100000 Volt sphere on top of a Van de Graaff generator, because it doesn't have enough electrons in it to make a current "big" enough to kill you. The current across the heart, that is enough to stop your heart, is about 50mA (as far as i remember), and that is very little current. Your heart is in between your hands, so you would need to hold "+" in one hand and "-" in another for current to go through it. You can also die from poisoning if a large current burns your flesh, and other similar bad things. If you think there's a danger from electricity, use just one hand so that the current goes through your legs, missing the heart (also watch for the top of your head, because brain). If the voltage is really high, like a transmission line cable falls right beside you, put your feet together and hop away. Like 10 meters away should be fine, idk. To be clear, you can touch the leads on your 12 Volt car battery and nothing will happen to you, in spite of the car battery being easily capable of delivering a big(ish) current of a 100 Amperes (but if you connect the leads with a wire, it will melt and burn you).
For fun i measured my palm to palm resistance just now. It's ~2 mega Ohms currently. So saying i need 50 mili Amps through my heart to stop it, i'd need (V = 0.05 * 2000000) 100000 Volts minimum. But that is for "direct" current (DC, not AC), and it doesn't take a lot of other things in to account. In reality 220 Volts AC could be enough. On the other hand, i know many people survived grabbing the "hot" wire and ground with their other hand, and the only one i vaguely remember died has fallen of a ladder because of the shock.
So in short; Wattage is power, Voltage is.. force, they are used to calculate things involving a lot of stuff (and safety), and the current hurts you because Voltage told it to.
PS Feel free to ask if something is not clear, i misinterpreted your question, something else you want to know or expand upon, etc, etc