Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)BI
Posts
1
Comments
425
Joined
1 yr. ago

  • I think translation is where LLM could truly shine the most. Some simpler models are literally searching for the closest meaning in the higher dimensional feature space. Translation isn't that far off from what those models do.

  • The PCB doesn't do anything other than a compacted connector between components. Especially the surface mount component. Also, some devices can be more sensitive than others making it more prone to breaking during mishandling. If something on the pcb breaks (highly unlikely), then you can just solder using jumper wire (to some degree, high speed signals cannot be treated this way). However, if the component on the PCB is the one that breaks, then you can just replace that component with some careful solder works. But yes, sometimes replacing it will be easier than repairing

  • Yeah, that's the thing with electronics. Sometimes the damage is not visible but the component doesn't behave as expected anymore. Timing can be off, more bit flip happens, all sorts of crazy stuff, including a resistor that is not up to spec or damaged ADC. Haunted it is.

  • Have you tried changing the pi as I suggested before? If the problem still persists, then there could be something wrong with the power supply or your house electricity. Because other than that, the only possibility is its haunted.

  • Yeah, that's fair. But I will still recommend anyone trying out linux AND having a problem to consult Arch Wiki when they can. It is amazing what they have there. It will also increase your technical understanding of how your system works overtime. But if you don't have any problems when driving linux, that is good too. It just means linux for the masses is coming closer.

    For some distro recommendations, if you love to tinker, I'd say go arch. You will learn a lot about your computer too, and it is also how I learn about mine and get the know how for a lot of things now. But also, if you don't have the time to tinker, I'd recommend bazzite. I've read their documentation and came to the conclusion that if anything goes wrong, it would be easy to recover from it, has great community, and is based on a solid distro.

  • I am merely rebutting your point about how more stuff can make things perform faster. Multi-tasking comes to mind. In a simple program, a task may be run in a procedural manner without interruption. Say for example, network access. The network stack must wait for the reply to arrive, but since the program is simple, it really is waiting for it doing nothing, wasting time that can be used to perform other computations. So the code will get bigger, but the performance is increased by reducing time wasted waiting for resources. By size alone, it is more bloated, but it is increasing performance. And as I said, I haven't looked at AOSP source code so my comment is not directed towards that point as I have no knowledge about low level android stuff.

  • This is for the general case, size doesn't always translate to performance. I haven't read the AOSP source so I wouldn't know for sure, but the general case for any algorithm is that. Sometimes having more code can result in faster performance due to how the algorithm works.

  • Yes, first you need to resize the partition to accommodate the new OS. Usually 40-60 GB is good enough for minimal linux installation if you didn't do any gaming or other massive applications. The resizing can be done in windows using disk management utility baked into windows, or some other partition manager (easeus, magic tools, etc). After that, linux can be safely installed in the free space as a single partition.

    Now, sometimes the bootloader is fucked, but it is quite easy to fix. In fact, if you use grub, it usually runs os-probe for you to check for any other OS. So sometimes, fixing it is as simple as rerunning grubmkconfig. But there are other times where it is not as simple. It will vary depending on what happened and too long to list here. Arch Wiki usually covers a lot of the topic so you could try searching there, especially on the topic of boot sequence.

    Lastly, if you need to move the partition, the data already inside will need to be moved too. This can take time depending on the size. But it is doable and safe.

    If, later down the road you want to remove either OS, you can simply remove the partition after moving the data first. Linux can mount ntfs natively so no problem there. On windows, there is a program called ext4 explorer or something along the line to browse and copy from linux filesystem (which is usually ext4). Don't forget to remove the boot information too after you're done removing the partition.

    Now there is also the other suggestion to use a live environment but I didn't suggest it since the experience can be lacking and more hassle in and of itself.

  • I am well aware, but it is bullet proof as in they couldn't restrict the OS from outputting audio somewhere else. For lossless DRM breaking, I'll leave that to the more technically skilled person. I am more of a developer than a "hacker"

  • Holy shit you got me thinking using ESP as a bluetooth audio receiver, but instead of playing the audio, it records it. Tedious sure, but I think it is quite bullet proof. Headphone jack also works if you have a soundcard with line level input.