You mean like the comment fields we’re using right here on lemmy?

As others have pointed out, it’s usually some markdown that’s embedded within the text. Lemmy is using a format that’s actually called “markdown” if I’m not mistaken, or a slight variation/subset thereof.

I’ve gotten used to the double-star for bold and what not to the point that it annoys me when some message client or whatever doesn’t support it. I share code snippets with people fairly often, and the code markdown is particularly useful to maintain its legibility.

I started in C and switch to C++. It’s easy to think that the latter sort of picked up where the former left off, and that since the advent of C++11, it’s unfathomably further ahead. But C continues to develop and occasionally gets some new feature of its own. One example I can think of is the restrict key word that allows for certain optimizations. Afaik it’s not included in the C++ standard to date, though most compilers support it some non-standard way because of its usefulness. (With Rust, the language design itself obviates the need for such a key word, which is pretty cool.)

Another feature added to C was the ability to initialize a struct with something like FooBar fb = {.foo=1, .bar=2};. I’ve seen modern C code that gives you something close to key word args like in Python using structs. As of C++20, they sort of added this but with the restriction that the named fields have to come in the same order as they were originally defined in the struct, which is a bit annoying.

Over all though, C++ is way ahead of C in almost every respect.

If you want to see something really trippy, though, have a look at all the crazy stuff that’s happened to FORTRAN. Yes, it’s still around and had a major revision in 2018.

I guess the MAC address guy is up next. 48 bits may not go so far if every light bulb is going to want its own.

Imagine if you were the guy who made the call on IPv4 addresses…

Falsehoods About Time

Having a background in astronomy, I knew going into programming that time would be an absolute bitch.

Most recently, I thought I could code a script that could project when Easter would land every year to mark it on office timesheets. After spending an embarrassing amount of…er…time on it, I gave up and downloaded a table of pre-calculated dates. I suppose at some point, assuming the code survives that long, it will have a Y2K-style moment, but I didn’t trust my own algorithm over the table. I do think it is healthy, if not essential, to not trust your own code.

Falsehoods About Text

I’d like to add “Splitting at code-point boundary is safe” to your list. Man, was I ever naive!

Fair, though I guess my interpretation was that void* is kind of like a black hole in that anything can fall into it in an unsettling way that loses information about what it was?

We need to watermark insert something into our watermark posts that watermark can be traced back to its origin watermark if the AI starts training watermark on it.

One thing most text editors can do is print. I was shocked the other day when I couldn’t print a readme from vscode when someone asked for hard copy.

This is why I fear activating any AI features in the IDE.

Compiler/interpreter: Can’t find variable farfignewton.

Earlier:

Me: Declare variables near, far

IDE: Oh! You mean farfignewton right? I found that in some completely unrelated library you didn’t write. Allow me complete that for you while you’re not paying attention.

This was a struggle for me going from hobbyist programmer to working at a company. I tried to tone it down. Really. But eventually I got “promoted” to having my own office with a suspiciously thick door. Hmm…

True story. I was looking for an answer to an obscure problem and found it in a 10-year-old stackoverflow post. Then I looked more closely at the author…

Hey! Me from 10 years ago, stop being such a smart ass! It’s obnoxious.

1st reaction: lmao

2nd reaction: hey wait, this is pure genius!

There is an issue with templated code where the implementation does have to be in the header as well, though that is not the case here. C++20 introduced modules which I guess were meant to sort out this mess, but it has been a rocky road getting them to be supported by compilers.

Looks like we’ve got a Java programmer here taking C++ for a spin.

There is bounds checking, but it’s opt-in. I often enable it on debug builds.

Ah I think I found it. I need to go:

{
    "format_on_save": "off"
}

deleted by creator

It was more than just tab conversion. For example, it decided on its own that:

if(...) {
    ...
}
else {
    ...
}

would look better like:

if(...) {
    ...
} else {
    ...
}

I mean I guess I could live with that, but really? I imagine there’s some config where you can disable all this, but it just doesn’t seem worth some giant git commit every time I touch a file with the editor.

I tried it briefly. It certainly is a lot snappier than Atom ever was, I’ll give it that. Seemed to be pretty good with Python, but when I opened some C++ source, it went around reformatting my indentation and replaces tabs with spaces. I will have to see if there is a way to disable all that, as I found it obnoxious.