I reinforce the suggestion of insulating Bootstrap on a layer.

And also, don’t be afraid to delete code that is demanding too much maintenance. Don’t get attached to it.

Outside of that, have fun!

If you add Bootstrap to your site, you write bootstrap-configuration for it, not normal CSS. You can’t use any of the usual code people pass around.

Also, it seems you are doing it for learning, so it wouldn’t apply, but a lot of the tricks for eliminating aren’t really practical and are best not deployed on real things.

That said, insulating Bootstrap into a layer deeper than your code may help (look at CSS layers). And yeah, like the sibling said, writing it on the browser dev tools is much better than reloading.

TBF, I don’t even remember why I stopped using the daemon. But it’s currently 3 seconds, so I dislike it… but not so much that I’d prioritize solving the problem versus complaining about it on the internet…

Anyway, I’m adding the server into my DE’s startup. Thanks for the reminder.

The problem is not encoding the result.

The problem is that you need some support from the language to make it easy to deal with. Otherwise you’ll get into go-style infinite if (err != null) handlers that will make your code unreadable.

It has Evil if that’s your thing :)

I dislike that it takes way too long to boot, but IMO the defaults are just fine.

In C++, ignoring anything that any other language provides…

I mean, yeah, if your language does not support error values, do not use them.

That’s a valid point.

There are two kinds of good serialization languages, the ones where values are black boxes and only serialize the data structure, and the ones where everything is completely determined and can be turned directly into an API.

JSON is neither, but it’s closer to the first than YAML. XML is the first, while the SOAP standard almost turns it into the second. TOML is about as close to the first as JSON.

TFB, the numbers are not defined as 64 bits floats.

They are just not defined. At all.

The end of line also has semantic meaning. Both indentation and eol are whitespace.

Haskell supports both semantic whitespace and explicit delimiters, and somehow almost everybody that uses the language disagrees with you.

But anyway, for all the problems of YAML, this one isn’t even relevant enough to point out. Even if you agree it’s a problem. (And I agree that the YAML semantic whitespace is horrible.) If YAML was a much better language, it would be worth arguing whether semantic whitespace breaks it or not.

Anything that didn’t need that kind of security from the beginning also wouldn’t break if it’s built.

The stuff that would break are all vulnerable because it doesn’t exist.

Have a code, where you can really describe the error; try to use the correct HTTP status (your example doesn’t); don’t ever use status 200 for errors; and finally, have an “error” key set to something somewhere (I’d write the error code to it).

The message is optional.

So, the simplest version would be:

HTTP/1.1 401 POST /endpoint
{
     "error": "UNAUTHORIZED"
}

Yes. Actually implementing Scrum can go either way, but going out of your way to learn and apply it is certainly going to end in tragedy.

The OP wants the paginated table data and the count. With a single query execution.

Just those hundred ones here. But I have to press them repeatedly and on a set pattern.

And bribing governments…

Everybody would use Mercurial, since Fossil completely lost the race, and both Subversion and CVS are unfit for today’s needs.

What is too bad, because Fossil would be much more productive than Git or Mercurial if the software just finished running at all; and Mercurial is way easier to learn than Git.

And those are only fully packaged user-facing software.

I’d guess almost all of the Rust code for low level hardware access is maintained by a single person. Most of them once joined forces and created a standard, it had 4 developers last time I checked. The only usable cryptography library for C# has a single developer, and while on crypto, that meme got widespread because of OpenSSL, that had a single developer who spent most of his time on OpenSSH and other BSD user-facing software.

Also, while we are on crypto, the modern algorithms were all created by a single researcher, that got famous for a work on how to decide if you can trust a crypto algorithm. Almost everybody uses his code.

Anyway, that meme first appeared because of Javascript, when a developer removed his library (with ~10 lines of code) from the language’s repository and almost every Javascript software broke.

Using AI in the marketing is a sign you don’t have much else to show for.

To me it’s a sign that you have spyware included, will depend on a perfect network infrastructure, and will stop working in 2 years.

But my guess is that for most people it’s a sign the product is made by some psychopath-like company like Facebook.

So, you need a unix time value followed by 000?

That first part you can calculate with date +%s -d '2024-07-02 12:00'.