That's just French for "masterful" or a way to describe lectures. There's a sense of greatness in that word that contrasts with the Mini in Ministral which is in turn might be a pun on "ménestrel" (minstrel), "ministre" (minister), or made to sound like Minitel (or all of the above).
While lighting is important, not using halflife.wad and going above the
original budget of 500 polys per "scene" is what makes modern works look much
better.
Most of the original textures are under 128×96 px and some suffer from awful
palletisation artefacts with purple and orange halos.
We still cannot use more than 8 bpp but we can use 512×512 textures and do a
better job at reducing to 256 colours. I use pngquant for that.
In GoldSrc lightmaps cannot get more intricate though, they're tied to the
texture scale so you cannot get a finer lightmap unless you also make larger
textures and scale them down, and these two combined will wreck your
"AllocBlock" budget in which all your textures and lightmaps must fit.
ericw-tools and its dirtmapping are still welcome improvements over the
"traditional" *HLT compilers.
For a proper "native i3 experience" I recommend setting gtk-titlebar=false and
unbinding tab/pane management keybinds. I already have a window manager, I
don't need a second one.
I also had to disable adwaita because when it's enabled closing a shell with ^D
closes all open windows, sometimes it leaves an empty window instead.
> - xterm still feel faster to me.
lxterminal also launches 6 times faster, I guess on a slow laptop without a dedicated GPU these terminals are not the most efficient option.
It's slow, you can't open links in new tabs, one wrong click and you have navigate to the right page and wait for everything to refresh again, but you can get the list of billed items. Plus a "Other subscription charges" that contains some mystery costs not linked to anything.
I've never heard a single good thing about Azure, and now that I have to work
with it I understand why.
The most egregious thing (for now) was an Auto Scale failure. For an entire
business day the autoscaler failed to spin up VMs which effectively killed our
product for the day. We could not scale manually either. No logs, no errors,
absolutely no idea what happened. Support tried to convice us for an entire
month that it was our own fault for misconfiguring the autoscaler by quoting
the documentation that was saying another entirely different thing.
After insisting for a month the issue was finally escalated to someone who
could read the logs and immediately see what went wrong: they had run out of
VMs and could not scale up.
So we have :
1. Unreliable services, breach of SLA.
2. Zero ability to anticipate, prevent, debug, or ensure the problem will not happen again.
3. Incompetent support lacking basic reading abilities trying to gaslight me.
4. An obvious issue that should have raised alarms long before it arose.
Thanks Azure.
This week I spend half a day trying to understand why Azure would not create an
Application Gateway using a configuration that was identical to another one we
had already (do _not_ attempt Azure without Terraform).
Turns out it was another outage with absolutely no way to know it.
Best part is the official fix: "Please, retry in case of failure during
the deployment." It takes 30 minutes to create said resource before it enters a
failed state. XKCD 303 applies.
After a cursory search it seems my Parisian-ish accent is at fault: https://fr.wiktionary.org/wiki/Annexe:Prononciation/fran%C3%...