nickwitha_k (he/him)

  • 6 Posts
  • 683 Comments
Joined 2 years ago
cake
Cake day: July 16th, 2023

help-circle


  • I’ll continue to say this every time that I see it. Feudalism. It’s just feudalism (or maybe neo-feudalism, with “neo” in relation to time period). Nothing about it is new. Nothing about it is really predicated on technology. Feudalism and similar mono/oligargic systems have always used available technology to oppress.

    The only thing that they’re doing different is not bothering with “divine right” and being slightly more honest in that they believe having money makes the better. But that’s also been done before. No need to slap “techno” on the front of it to make it seem like it’s a unique situation that’s never been attempted before. They’re just another group of egotistical shitheads who have convinced themselves that they are special, unique, and superior, when they are none of these things. Just like all of the rest of the would-be kings in history.










  • 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.







  • In a world not dominated by unfettered capitalism, sure. That’s not the one that we live in however and this tool has both been built on stolen and unlicensed intellectual property as well as being used explicitly to harm people’s livelihoods while replacing their work with objectively inferior plagiaristic amalgams.

    AI companies also refuse to obey the rules of the Internet and continually DDOS sites that request crawlers and scrapers not do so, necessitating creation of whole new types of software to defend against their malicious behavior.

    And on top of all that, they have substantially increased greenhouse gas emissions and are actively consuming potable water in a manner that makes Nestlé execs hard. Putting the planet’s biosphere at greater risk and unnecessarily increasing water scarcity.

    Nah. Simping for AI companies is the irrational take. The value that they provide to humanity is, outside of some niche use cases, marginal at best and will likely never come close to making up for the harms that they are causing to humanity for a quick buck and to increase worker oppression.