when the official docs are telling you to use it, then it’s used. You can have no expectation of people to think the tooling isn’t shit when it’s literally the official recommendation.

Anything but the last one. Don’t duplicate the http code in the body, else you’re now maintaining something you don’t need to maintain.

I’m not a fan of codes that repeat information in the body either, but I think if you had used a different example like “INVALID_BLAH” or something then the message covered what was invalid, then it would be fine. Like someone else said, the error data should be in an object as well, so that you don’t have to use polymorphism to figure out whether it’s an error or not. That also allows partially complete responses, e.g. data returns, along with an error.

I completely agree.

I do not. I’m sorry.

https://github.com/nektos/act

it does if the other ones have edible seeds, seeds without arsenic, or fewer seeds… your analogy makes no sense.

Also, writing memory safe code honestly isn’t that hard. It just requires a different approach to problem solving, that just like any other design pattern, once you learn and get used to it, is easy.

the CVE list would disagree with you.

https://en.wikipedia.org/wiki/The_Power_of_10%3A_Rules_for_Developing_Safety-Critical_Code

and their 40 page coding standard document. https://ntrs.nasa.gov/api/citations/20080039927/downloads/20080039927.pdf https://ntrs.nasa.gov/citations/20080039927

and their software safety handbook. https://standards.nasa.gov/standard/nasa/nasa-gb-871913

all 389 pages of it https://standards.nasa.gov/sites/default/files/standards/NASA/Baseline/0/nasa-gb-871913.pdf

It’s also just a huge fallacy. He’s saying that people just choose to not write memory safe code, not that writing memory safe code in C/C++ is almost impossible. Just look at NASA’s manual for writing safe C++ code. It’s insanity. No one except them can write code that’s safe and they’ve stripped out half the language to do so. No matter how hard you try, you’re going to let memory bugs through with C/C++, while Rust and other memory safe languages have all but nullified a lot of that.

You ask them to add a license, you don’t suggest a license.

You can write cross platform mobile (and desktop and even browser) apps with Kotlin.

that’s so weird because I got an email inviting me to participate and I haven’t ever been considered a ‘prolific poster’. I’m only at 60k and 12 years. I had no clue I was invited until I looked in my spam folder.

still, people are clearly confused by the button. I’m just gonna make it an animation and prefers-color-scheme since that’s so widely supported now.

I’ve wondered what this problem was for years but never cared to figure it out, because it always resolved after the first button press (just refresh the page and it all works properly). turns out it is something wrong with my use of local storage to save your theme state. if you don’t have the key in local storage then it does what you mentioned. I just need to switch this to prefers-color-scheme anyway.

that post is about toggle buttons, not switches. e.g. a play pause button, when pressed, does it show play, or does it show pause?

It shouldn’t be like that. on my computer it shows the sun when it’s in light mode, moon in dark mode.

Hm. what browser are you on? It is showing sun for me on light mode.

I’ve been saying this for years. My site only has a few lines of javascript. the rest is pure html and css, and it’s very simple. https://tylerthrailkill.com

Because no one ever uses those. Literally > and | are the only ones I’ve ever seen in over a decade and you will never need to worry about the differences between the two.

XML as a configuration language is terrible. Yaml gets the point across in an easily readable way, which is exactly the point. Same for JSON except JSON you can’t even use comments (you need json5 or one of the numerous other alternatives to get those).

Manually patched by pulling the commit and building your own source?