Lol, changing the country of origin doesn’t constitute innovation from a consumer standpoint…

Now if this was using 5nm or chiplit or any of the other buzzwords of the day it could be marketed as innovative in the modern sense of the word.

Realistically there is no innovation left for ARM platforms. They all use the same core schematics. They only control data flow and peripheral IP as a manufacturer, unless they feel like building their own core from the spec (nobody really does that anymore as ARM has been desperately trying to standardize everything). The most “innovation” I’ve seen has come from stubbornness around keeping legacy bus architecture around instead of adopting AXI (even when all the IP they are trying to use already uses AXI and they keep having to make translation hardware).

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

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…

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.

It was dead however long ago when I submitted a PR. Still unmerged with no activity on the request so I just never went back to check.

It’s good to hear that they are working on it again though, if that is the case.

It depends on what you want. Do you want containers that don’t blow away your firewall? Podman is nice, but docker can be configured a little to avoid this. Want things that autostart and don’t have issues with entry points that attempt to play with permissions/users? Docker or podman as root is necessary. Want reasonable compose support? Podman now needs a daemon/socket. Want to make build containers and not deal with permission/user remapping at all? Podman is really nice.

Do not attempt to use podman-compose. That app is dead.

Unfortunately if you want to make tools that will be used by other people then you must add docker support. It just owns too much of the market.

They have been around for a little while now. Had one in college ~4 years ago. Upstream kernel support was a little rough but spec wise they were impressive alternatives to the RPi 3B

Friendlyjordies watchers knowing it would be abc that advocates for this…

Cross platform! You know, accessible across all our platforms

Can confirm. Software is trash. Wanted me to connect it to the internet and setup a cloud access account. Like, dude, you’re a glorified battery pack I’m not adding a backdoor because you want to tell APC when my warrenty is about to expire so I can get marketing emails.

I present to you the holy hardware compatibility table:

https://networkupstools.org/stable-hcl.html

Anything not listed there is not worth buying.

I’m not seeing this on Arch Linux right now so it may be a Deck specific regression