You found an important bug in your short code plugin. Removing the line from .gitkeep is not actually the solution; it was a symptom of a much bigger and more dangerous problem: you are inadvertently including and parsing a file that is not intended to be a short code.

You, or a crafty hacker, might one day create a file with code in it that should not be parsed as a short code, and not realize that it’s being done. You’re lucky that you’re the one who discovered this and not somebody else.

The solution is the only parse the files that you need to parse. This means ignoring hidden files that begin with a dot. You might also think about creating a default ignore list for any other non-shortcode file that could exist.

Birthed me. Then they had the audacity to celebrate it each year there after.

This post is still not Linux related.

…the Logitech AI mouse.

That should be false advertising; both to consumers and investors. There is nothing AI about a dedicated button preprogrammed to launch an application that does the AI for you.

But I guess that further demonstrates your point about companies cramming shit in consumer’s faces to appease investors. It’s still a huge WTF in my book though.

Where’s the flex in that statement? How is suggesting you’d have rolled over and let another country bully you better than the “underdog” country fighting back and giving the bully a hard time? I must’ve missed a memo somewhere along the way.

The way I look at it is this: I want credit for the work I do, I should also be able to fork a repo that I work on, and I sure as hell don’t like giving up my rights if I can help it.

But others may feel different.

They are nuts. Their license means that you give up all of your authorship rights to the code you contribute, and on top of that you’re not allowed to distribute modified source, nor can you fork the source for any purpose.

Edit: lol

Could you mean network radios?

Whatever it is, I’ll bet it’ll be 3 nanometers thinner than last year’s model!

I’ll admit I’m no c/c++ aficionado, but after a little research I see what you mean. Originally, C++ was a superset of C, but C has since diverged to include things that are not in C++. So we are both correct.

In before the pedants: clang is a c compiler, in that it compiles c code—but it also compiles other languages too. The distinction is that c, c++, rust, etc are compiled directly into byte code , whereas typescript is transpiled into another language (JavaScript) before it is executed. I’ll probably catch heat for this, but you can liken TypeScript to C++ because they both are supersets of another language.

I feel you’ve missed my entire point. My comment was not based on any technical merits of a language. It’s about a persons personal (religious) view of a tool they use to do their job.

I proudly use PHP, JavaScript, Java, Bash, and SQL. They have given me the means to make a long and fruitful 18+ year career. If my boss walked up to me tomorrow and said I needed to learn Python, or Rust, or even brainfuck, I’d learn it and be better for it.

Would it be as easy as my tried and true toolset? Not at first. I still remember the struggles I had when I was first learning my current toolset. It was frustrating. I remember cursing how stupid this or that was (especially PHP and JavaScript). But I learned, and now they’re not as frustrating — because I work with it, and not against it.

Look at JavaScript. Yeah it’s weird sometimes; if you don’t understand how it works. So people slap these transpiled languages or frameworks (like CoffeeScript or TypeScript or whatever) on top, trying to fix the things they think are wrong with JavaScript, and end up making a chaotic mess of the entire community. (And yes we could spend months arguing pros and cons of any merits of transpires and frameworks and why and what not, but then you’re still missing the point).

Anyway, the point is: if it works, then it’s good. Rust does not make Linux worse. If anything, it makes it better because it makes it more accessible to programmers who know Rust but not C. And that’s a good thing. It ensures the Linux kernel will be around longer than whomever ends up being the last C developer.

Those C developers bitching about how they don’t like the idea of rust in their kernel are akin to those old fogies yelling about those damned kids and their loud music or fashion sense.

This quote applies to so many situations and so many languages. It’s beautiful. 🧑‍🍳 💋

Typescript is always compiled down to JavaScript, so it’s kinda the same thing, but with “nicer” clothes.

People need to chill with the language fanaticism. It’s one thing to make jokes and rip on a language for its quirks, but at the end of the day it’s just a language. If you truly don’t like it, don’t use it. I’m going to take a stab and guess that there is enough Linux kernel source to go around to both the c devs and rust devs. Just be glad they’re not trying to rewrite it in JavaScript. 😉

Stupid move posting about it publicly while the case is still open.

The problem is that they both are contextual and can mean any position in a list/array. The starting index or starting offset is generally zero, but could be one, depending on the language used.

Blowing anybody up is NEVER funny. And it never will be.

There you. You can’t stop people from fighting, but we certainly can stop helping them kill each other.

And look, I get it’s a hot button issue for a lot of people. I’m not suggesting anyone is wrong for whatever side they choose. It’s too complex of an issue for my pea-brain to fully understand. What I do understand is that the US and other countries need to be working toward helping both sides find a reasonable and peaceful solution — whatever that may be (I’ll leave that to the smarter people to figure out).

Amen. Now, where’s that Wine?