Like any other convention, it’s not really a big deal either way. Fortran gets along just fine with 1-indexing.

Removed by mod

Would a fork be technically viable if Americans and American businesses can’t participate (because the fork works with SDN entities)? Maybe.

The reality is that the Linux Foundation is in the United States, and Linus is a naturalized US citizen who lives in Oregon (at least on Wikipedia). So they both will have to pay attention to avoid transacting business with individuals and companies on the SDN list. That is the law in the United States.

Really I worked a project once that just had post-its stuck to the wall. It worked as well as Jira does.

Most places in the US will have nothing about severance written down anywhere, but it’s very common to actually pay severance in a mass layoff situation (unless the whole business is going under).

Current IT best practice is that passwords should never expire on a set schedule, but they should expire if there is evidence they’ve been breached.

If wasn’t full garbage collection in the spec. It was some infrastructure support in the spec that would make it easier to write garbage collectors in C++.

There’s also D. You could just upgrade to D.

When Fortran was created, each line was a separate punched card. The syntax made sense for that medium.

C was setup from the start for use on teletypes with fancy line editors like ed.

For example, synaptic is a long running front end for apt that has the buttons for update and upgrade.

When the gp’s book says that C is a third generation language: I would guess the first generation is Fortran and the second generation contains ALGOL and BCPL. C was heavily influenced by BCPL. (get it? C comes after B)

Especially talk to FSF if this “well known debugging tool” is a part of the GNU project, as FSF has the power and standing to enforce the copyrights on GNU software.

Or Fortran variables that collide with Fortran built-in functions.

Keep in mind that array subscript and function call are both () in Fortran.

And you can write more than six characters, but only the first six are recognized. So APFLWSAC and APFLWSAF are really the same variable.

And without namespaces, company policy reserves the first two characters for module prefix and Hungarian notation.

Ctrl+alt+delete was a separate interrupt line direct from the keyboard. That is, when you pressed the three keys, the interrupt signal was asserted, causing the CPU to jump to the interrupt service routine, which should be in the source code package.

Stellaris on Steam has a fully-native Linux executable.

Except even Gentoo does binaries now (more than they used to).

It’s not git that’s complicated. The work is complicated. git is just one of the tools that programmers use to manage the complexity.

I also think that some people get too hung up on having a “clean” history, and trying to “fix” the history after it has already occurred. I usually have enough problems to worry about in the present, without also trying to worry about the past.

Yeah, I think that guy only got a superficial understanding of what Uncle Bob was saying.

My policy as a tech lead is this: In an ideal world, you don’t need the comment because the names and the flow are good. But when you do need the comments, you usually really need those comments. Anything that’s surprising, unusual, or possibly difficult to understand gets comments. Because sometimes the world is not ideal, and we don’t have the time or energy to fully express our ideas clearly in code.

My policy on SCM logs is that they should be geared more towards why this commit is going in, not what is being done. And what other tickets, stories, bugs it relates to.