Kissaki @ Kissaki @programming.dev

[@GitHub](https://github.com/Kissaki), [website](https://kcode.de/)

---

Read more

Posts

27

Comments

452

Joined

2 yr. ago

Is it gatekeeping if they voice their disapproval? Is any form of disapproval gatekeeping? Where is the line?

They didn't ask them to stop posting or participating. Wouldn't that be the line where it crosses to gatekeeping?

They asked them not to attach the CC notice. It didn't address their content.

DuckDuckGo

I think it's convoluted way to describe it. Very technically-practical. I agree it's probably because of historical context.

The argument I read out of it is that using goto breaks you being able to read and follow the code logic/run-logic. Which I agree with.

Functions are similar jumps, but with the inclusion of a call stack, you can traverse and follow them.

I think we could add a goto stack / include goto jumps in the call stack though? It's not named though, so the stack is an index you only understand when you look at the code lines and match goto targets.

I disagree with unit tests replacing readability. Being able to read and follow code is central to maintainability, to readability and debug-ability. Those are still central to development and maintenance even if you make use of unit tests.

Their main argumentation (from page 1) summarized:

You know the state and progress of a program from the line you are on. A goto breaks that.

You can index the progress of a program through static line indexes and a dynamic loop index and function call stack. A goto breaks that. Including a "statements/lines since beginning of execution" is infeasible for understanding.

PDF magic… It has grainy text. But the selectable text and displayed text have a 1-character offset.

I assume they display the original scan so it definitely does not contain errors, while still providing the image-parsed text for searchability, indexability, and select-+copyability?

Unfortunately, the grainy text is hard[er] to read.

Go has goto too. They surely did not "mindlessly copy" it.

The standard library makes use of it. So they most definitely see a warranted use-case for it.

• math/gamma uses goto
• Stack Overflow: "Why does Go have a goto statement?"

OP argument against using it in high level languages may still hold though. Go may have introduced it as a systems language which allows control over alternative implementations.

To make it more accessible

1. create your own (small) projects
2. make small contributions where it's possible (skip compiling, or -> 3.)
3. try to work on a project, and quit early if it's not simple
4. pick technologies that are simple to set up or you are familiar with

Yes, you should, as you already do.

Is your question whether you should worry? Whether you should link the source when you're illegally ignoring license terms? Or when you're following license terms?

I hope the demo starts soon…

(What a bullshit correlation/equation to start with.)

Doesn't the "scaled trunk-based development" do that too, with feature branches and merge requests? Trunk is your production-ready branch there.

I guess we do scaled trunk development, if you want to call it that. We do allow direct commits, for trivial or safe stuff where reviews would be more noise and hindrance than value. (Code formatting etc.)

We only have one current release version though. (And at times a current test version that deviates from it.)

If there's a need to create a patch release for a tagged version when the trunk proceeded forward with something that shall not be included, I create only a temporary branch from the earlier tagged commit to tag (=create) that patch release.

What are the release branches supposed to be in your graphs? It says developers don't commit. Then who does?

Yes, the GPL allows you to make modifications. The GPL still applies.

The cloned repository still holds the history and deleted files. The files that are still there retain the GPL. If you make additions to the GPL sources, the GPL applies to those too. (Copyleft license.)

You can check the summary of GPL on ChooseALicense to understand your rights and conditions a bit better.

A patch from January and MFA prevents account takeover.

If you're not updating gitlab for over three months, across max severity security patches, you're negligent.

a random program

like

 js

    
alert(Math.random())

  

This description is so foreign to me. I guess you're talking about big [software] companies?

Nobody in my company, a software development company, measures by lines of code. We bring value through the software we develop and the collaborations we do.

When I miss them I create them. Then they're there.

You're asking about the backend only, separated from the fronted? The fronted will be HTML only, but independent of the backend anyway?

Doesn't that mean you're introducing another interface and a need for another backend for the HTML frontend generating?

If it's independent, why does the frontend intention matter?

My first choice/exploration would be C#/.NET.

The advocation for package manager platforms to include licensing and pay is interesting.

I had no idea experts exchange existed before stack overflow.

For me, it started showing up in web search results years after stack overflow became popular. And I was confused and annoyed why a copycat with pay walled features (even the answers IIRC) was given priority by search engines.