Skip Navigation

Posts
0
Comments
223
Joined
3 yr. ago

  • That's my first thought, but my brain keeps trying to inject one immediately following "Surely." No idea why.

  • I feel like there needs to be a comma somewhere in that sentence but I don't know why...

  • Unfortunately this doesn't seem to apply to publishers or developers that don't have a landing page

  • 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...

  • Some of them advertised specific performance improvements.

    I'm not going to rag on them though. Some of them did have performance improvements and basically created the tools and optimized defaults that propagated to standard distros, allowing the gap to close.

  • 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

  • For people using bash that are thinking "how do I do that":

    The bash-complete package adds the _command function for recursive completion on commands that accept other commands with their own arguments. It's what sudo uses last I checked. You can add complete -F _command stfu to your bashrc to link it to the stfu command.

    https://man.archlinux.org/man/bash.1#Programmable_Completion

  • 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

  • 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.

  • I don't get people being worried about an offline application designed to run one shot as the current user not receiving updates. I do get maintainers dropping the package from package repos now that it is officially archived though...

  • 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...

  • Cool, saw your logs just a while ago with the error about being unable to execute /bin/sh so I figured as much. What did you do to get there? I've never had an update fumble that hard...