Fuck it. Gun it at the brick wall. Jerry’s rigging up an emergency break as we speak. Don’t mind that the last piece to said break may be missing.

- Man who will probably die before we hit the wall

I was working at a company at one point that got a contract to build something I viewed equivalent to malware. Immediately I brought it up to several higher-ups that this was not something I was willing to do. One of them brought up the argument “If we don’t do it someone else will.”

This mentality scares the shit out of me, but it explains a lot of horrible things in the industry.

Believing in that mentality is worse than the reality of the situation. At least if you say no there’s a chance it doesn’t happen or it gets passed to someone worse than you. If you say yes then not only are you complicit, you are actively enforcing that gloomy mentality for other engineers. Just say no.

Well, assuming you meant type specifier, at least not before C99. After that it is required. C23 explicitly states that a type specifier is required for all declarations.

If you actually meant type qualifier, then no. That was never required.

Publicly traded corps just saw the letter “p”, assumed profit, and announced a 5 year plan to discover the rest of that sentence. Their shareholders are still upset it took them a whole letter before they had a plan…

But also, sorting big endian automatically groups elements associated with common functions making search, completions, and snippets easier (if you use them). I’m torn

To me on the security side of things caddy has a feature I have yet to see anywhere else: default reverse proxy headers.

Got something you want to lock down remote js loading on unless it explicitly requests an override? Default the variable to a locked value. The application can override it with it’s own header as necessary.

https://caddyserver.com/docs/caddyfile/directives/header

deleted by creator

Search telemetry in a web browser is absolutely insane. I can understand more usage statistics but search telemetry just makes it sound like they want data on who to make an offer to for the next default search provider slot.

Or worse yet, another half-assed partnership with some sketchy 3rd party with a completely fucked moral compass and a privacy policy to match.

Good video going over practical pros and cons currently:

https://piped.video/watch?v=s6zcI1GrkK4

A lot of people praise CS’s Overwatch mechanism for solving the issue while making it entertaining to users.

I would say something like that is probably the best solution we can give aside from appointing every user a ref and having them physically in the room with them for the extent of the game.

I wish nginx had the concept of default header values for reverse proxies…

I mean, you can kind of do it with macros but man…

I have the opposite problem now. Someone gifted me a Jester award on my profile and now I’m trying to figure out if it was because of a joke or if I am the joke…

All I can see are mantis men

It was at least good as a stand alone game but then the creators abandoned it really early.

If only you knew what they’ve been doing to the embedded devices lately…

We’re the front line dog. Strike me down so Debian Stable’s legacy may live on.

I mean, you shouldn’t really parse any language (markup, script or otherwise) with regex. The point is there are other tools for the job that get you closer to what the actual interpreter is expecting to see. It’s really easy to botch a regex and accidentally create new syntax matches.

Regex is fine for noncritical parsing. You’ll often see it used for text editor / IDE language syntax highlighting, but you should also have noticed by now how often that tends to break down with more extreme combinations of syntax.

I do agree that lexers should still be preferred for manual manipulation of existing langues, but do whatever you want. It’s not like any of us can stop you.

Something something furmark

If you’re just looking for RSS -> Push take a look at feedpushr

I use it with gotify without too many issues.

You say that like there a large overhead to containers…

Even in this case that overhead is negligible. Container configs and artifacts are also more portable and easier to backup.