Posting Etiquette

I will frame the question in terms of a specific C# objective that I am working on right now but I imagine the question is a pretty general one related to the Dunning-Kruger effect, in a way - how do you know how to build an application when you don't know all the issues you are supposed to prevent?

There is a message hub and I am developing a consumer for it. The original plan was to just create a few background services that get initialized alongside the application, that have a loop to load new messages/events and then process them.

Some time has passed and it feels like I am knees deep in Wolverine, Quartz, Hangfire, MassTransit, transactional outbox and all manner of different related things now. The potential issues are dealing with downtime, preventing loss of messages by storing them in a separate table before processing them, and everyone on the planet has a different idea on how to prevent and solve them and none of them sound simple and straightforward.

Honestly at this p

I’m versed enough in SQL and RDBMS that I can put things in the third normal form with relative ease. But the meta seems to be NoSQL. Backends often don’t even provide a SQL interface.

So, as far as I know, NoSQL is essentially a collection of files, usually JSON, paired with some querying capacity.

1. What problem is it trying to solve?
2. What advantages over traditional RDBMS?
3. Where are its weaknesses?
4. Can I make queries with complex WHERE clauses?

Learning by doing is hard to beat when it comes to building software.

I am starting a home lab to have a safe environment to try things out. Any ideas on what I could run that is completely useless but fun to set up?

@learnprogramming
@homelabs

im trying to understand 'dynamic tables' [snowflake] and they kiiinda just sound like materialized views + automation on cache results?

How can I define lines so when I click on the screen, my program knows whether I clicked on A B or C?

Hi, I have this function that is supposed to upload a file stream to another page:

 undefined

    
async function getData() {
    const vocadata = await fetch('http://localhost:3000/upload/',
        {
            method: "POST",
            headers: {
                "Content-Type": "multipart/form-data",
            },
            body: data,
        });
    console.log(vocadata);
};

  

The problem is though, no matter what URL I enter in the first argument, it always posts the request to /. How can I fix this?

I've been stuck in this mindset where I can't think of any good website ideas, or game ideas, or anything really. I want to get out of this mindset by thinking, "What should I make?", or "What do I need to make?".

I still follow peoples advice on "go take a walk and think about it for a bit" and "you'll get one soon" and things like that. Those don't seem to work.

All I need is advice on how I can make myself come up with ideas for projects that would let me do something with my free time. Any help would be appreciated!

I know stuff like SDL and RayLib exists, but I already have my own X11 and Windows API stuff working, and otherwise those libraries like to obscure things from the user in the name of "ease of use", sometimes even missing features (force feedback and proper XInput are the ones that are often skimped out on for whatever reasons, and only SDL has them to my knowledge). While I'll implement libevdev eventually, it has the issue of needing access to the devices.

While I found some reference to game inputs in X11's input extensions, I cannot find any user guide on them, since they're instead pointing me to SDL and co.

I not only have hard time finding tutorials, but even if I do, I have a hard time getting them to not crash, let alone working. I don't know what's the reason, but I have a suspicion that some of these are now AI generated, hence the issues of them not working or outright crashing.

I know newer APIs exist. They're way too complicated for my usecase.

I've heard about WebGPU, but I don't want to touch it with a 10 meter long pole, due to its name. I'll have a lot of time convincing people that WASM isn't a web-only thing, and me using it for scripting won't mean my game engine is either Web-based, nor that it has any Web-capability, and I only stayed with it due to my inability of finding a well-supported scripting VM without "Web" in its name.

If you ask: My game engine is currently using CPU rendering, and used to use SDL2 for displaying the output. I decided to move away from them. Managed to find some basic OpenGL tutorials when I first write my replacement for the SDL2 window han

Vertex:

 glsl

    
#version 120

void main() {
    gl_TexCoord[0] = gl_MultiTexCoord0;
    gl_Position = ftransform();
}

  

Fragment:

 glsl

    
#version 120

uniform sampler2D tex;

void main(){
    vec4 texSlmp = texture2D(tex, gl_TexCoord[0].st);
    gl_FragColor = vec4(texSlmp.r, texSlmp.g, texSlmp.b, 1.0);
}

  

All I get with this is a black screen.

I cannot seem to get tutorials for anything older than OpenGL 3.3, and for my usecase, I could go lower, except everyone tells me "OpenGL is obsolete, try Vulkan instead".

gl_TexCoord[0] seem to be all zeros if I modify the fragment shader to try to output gl_TexCoord[0].st, so its content would be displayed as color information, which I did for a different test. Also I can't find anything on how do I "pass" textures (or other values) to the shaders in the official docs, nor any of the tutorials I could find explains how that actually works.

EDIT: Target version is OpenGL 2.1/GLSL 1.20

EDIT2: I updated the shaders to GLSL 3.30, but t

For context, I am trying to do a save system for a game.