nickwitha_k (he/him)

  • 8 Posts
  • 1.35K Comments
Joined 3 years ago
cake
Cake day: July 16th, 2023

help-circle

  • Open question to all: what is your level of profiency?

    I’d say that I’m pretty proficient. I haven’t done LFS yet but haven’t really spent more than a few mins with windows except for a handful of times for about 15 years. The one time that I did so recently was to try to get a PSVR2 to work. That experience was so awful (driver disks for OS install, ADS FUCKING EVERYWHERE THAT CANNOT BE DISABLED, etc) that I quickly gave up and ended up killing the VM. I’d dinner become a hermit in a cave than abide by OS-level ads that can only be partially disabled by mucking around in the registry.

    Sorry. A bit off-topic. I just really hate ads. Erm… I’ve done some basic tutorials on writing drivers for the kernel and have been working on reverse engineering a driver for some AR glasses, though I’ve not made it too far.

    How do you learn about linux?

    My initial learning was because I lost my XP serial in college and decided to give Linux a try. From there, a lot of my learning has been through work, which I got due to my teaching myself how to use Linux.

    Do you think there is a problem or is it a loud minority of users?

    It’s both. I’d say that it really is going to vary based upon the sub-community. Unfortunately, there’s a lot of toxicity in the gaming community at large, which, in my experience, is reflected in segments of Linux gaming communities. On the other hand, I just last night saw a bunch of people on Lemmy trying to help someone figure out how to get their new GPU to work, which was very much the opposite of toxic.




  • First, I would like to give you some major props. Installing Arch, in itself, is a big deal. It is not a beginner-friendly distro. It is a very power-user friendly distro and has an incredible wiki that is helpful, at least to some degree, for many distros.

    For a beginner distro, I would recommend Linux Mint for its easy transition and great focus on user experiences or Bazzite if you really want to install and get gaming.

    When taking drivers in Linux, most are provided as either kernel modules (integrated into the kernel, so you don’t have to worry about installing anything) or packaged for the distro, in which case, once installed via package manager, they’ll auto-update whenever you update system packages. They are so much easier to deal with than Windows drivers (for the end user). For example, to use a Wacom drawing tablet, all one has to do is plug it in.



  • It’s really not just that it is/was cheaper. There are cases where, all costs considered, it was actually measurably more expensive. The main reason for off-shoring is purely ideological. Amercan capital has nothing but disdain for workers and hatred for organized labor. Off-shoring was intended to crush unions, while giving a temporarily lower price to goods to prevent the populace from understanding how much they were getting screwed.

    Chip production is a highly specialized field, where workers could readily demand concessions from capital, were they on anything resembling stable ground. That was not too be allowed.





  • Another (mostly joking) suggestion: Create propaganda supporting use of free, [libre,] open-source software and esoteric operating systems (like Plan9). While this is not directly related to conventional nation-state-vs-nation-state or political-ideology-vs-political-ideology topics generally central to propaganda, it may encourage people to make the digital and physical world a stranger place.







  • In your statement, you provided much more self-awareness and abstract thought than an LLM, by its nature, is capable of. They are not intelligent.

    I don’t disagree that what’s going on in our meat computers (simplification) isn’t terribly special, in the grand scheme of things. And, there’s little reason that similar processes and results can’t be realized in other media. But, LLMs, by themselves, will never be capable of it because of their innate characteristics. Brains have numerous specialized structures that are networked together, so, probably the best bet would be building systems that can fullfill similar functions, and connect them.



  • Been a while since I was in a lab (I was mainly concerned with squishy, squidgy things like microbes, so not quite OChem either) but, this looks accurate to me with a minor bit of pedantry that I had to validate before mentioning. BPA is not actually a plasticizer but a monomer/co-monomer (it does frequently get incorrectly labeled as a plasticizer in retail products). Notably in polycarbonate, which is something like 90% BPA by mass.

    A big issue with is the incomplete reaction of monomers, leading to things like room-temp leeching of unreacted BPA in polycarbonate (so glad that I took a Nalgene with me everywhere for years when I was younger /s).


  • In that case, my suggestion would be to target implementing a REST API with OpenAPI (formerly Swagger). There are server code generators for both Rust and JS (multiple flavors, I think).

    Basically, the workflow is something like this:

    1. Create your API spec skeleton (YAML or JSON, pick your poison). This will have all of the required sections like info
    2. Pick your first endpoint and define it in the paths section. Probably start with during simple like a GET. This will mean that you mainly have to worry about defining your responses (at minimum HTTP2XX and HTTP4XX, preferably with a catchall error response for HTTP5XX responses) and their schemas.
    3. Run the code generator. This should generate files with stubbed-out definitions for interfaces (or the equivalent for your language of choice) for your response methods. Generally, you do NOT want to add any code to these files as they will be overwritten anytime you update your API spec.
    4. Implement the methods to handle the stubbed out interfaces. Ex. A hello-world interface would likely need to be implemented with a method or function that returns the string “hello world”.

    The reason that I recommend OpenAPI in writing REST APIs is that it helps to layout the API contracts before you even start coding. This helps with keeping typing consistent, give you a clear milestone for implement, and makes creating clients really easy.

    Extra benefit is that OpenAPI is (mostly) language agnostic, so, as long as you have a codegen or some good boilerplate, you can use it for any language, which can give you a safe place to start when learning a new language.