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.
The author did not want to use real addresses and was not aware of the 192.0.2.0/24, 198.51.100.0/24, and 203.0.113.0/24 ranges specified in RFC 5737 - IPv4 Address Blocks Reserved for Documentation.
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.
I've been using Hammer since the Worldcraft 3 days, it took less than an hour
of using TrenchBroom to know I'll never go back to Hammer or JACK.
It just works. The overall modelling workflow is much more efficient, it's well
designed, linked groups is a killer feature, it doesn't crash for no reason and
when it does crash you can submit an issue and get it fixed in a day (or fix it
yourself, it's FOSS), CSG (e.g. the carve tool) produces sane geometry in a few
milliseconds instead of crashing after a 20s freeze.
It also runs smooth and fast whereas hammer stutters all the time and feels
like it renders its viewports and UI at 20 fps.
The apparent simplicity is a feature in itself, not a lack of functionality.
0.48 is not even released yet (still a RC) you'll have to wait a bit more for 0.49.
There's nothing preventing you from building it yourself though, the master branch is stable and you can complete the game without a single crash or game-breaking bug.
> If Reddit replaces volunteer mods with paid mods we would get a more
> consistent moderation and almost certainly a more professional experience.
I can guarantee you the opposite. You'll have a site-wide abusable
Scunthorpe-incompatible report-based automated moderation with no proper appeal
mechanism in place because half a dozen underpaid interns/offshored employees
will be responsible for taking over the work of hundreds of moderators.
It's already happening in some cases. There's ways to make reports go directly
to the so-called Anti-Evil Operations team who will irrevocably override any
moderation decision and enforce abusive reports.
It's easy to get people banned, post some hateful content, wait for reports,
and then report the reports for report abuse.
> But I can't think of any other social site that has such a bad rep for moderation.
There are some legitimate cases of poorly moderated subreddits and mod abuse
(and the whole powermod issue), but beware, most of the time people complaining
about power-tripping mods and "not being able to say anything anymore" have
been banned for very good reasons (those reasons being straight-up hate speech
most of the time).
We caught "community builders" making disingenuous posts trying to pass reposted/translated content as OC to generate engagement. After getting caught doing so with their admin accounts they tried again using normal users.
They also had the bright idea to spam users via DM using a poorly templated message (verbatim "insert u/USERNAME") to promote localized copies of low-quality subs (the kind of trash you see on r/all).
> I'd be curious to know what's good or bad about it compared to GCP and AWS.
Documentation lies, support lies, metrics lie, bugs everywhere, and when something breaks the status page is always all green and support tries to convince you it's your fault anyway. They're only here to prevent you from enforcing the SLA. The distrust is pervasive.
I stopped suspecting my code, if something breaks outside of a planned maintenance it is _always_ Azure.
My latest support ticket: Azure App Service internal DNS server broke and there is no way to bypass it short of hardcoding IPs in /etc/hosts. Support told me that if I wanted App Service to work reliably I had to implement their DNS server myself.
To rephrase, my PaaS provider told me to spend time and money to implement the very platform I was paying them for, and it just so happened to be absolutely impossible because of an unannounced BC break a few months prior (which is another lengthy and frustrating story).
This morning I had a VM cut out of the network and 10% of my App Service traffic just disappeared. No explanation, no incident report, nothing.
These days I'm working with AWS, and it just works. If something isn't working you know it's your fault and that the answer is in the documentation. I'm not spending days on workarounds, I'm actually implementing as planned. I have no words to describe the relief I'm feeling.
> We never thought our startup would be threatened by the unreliability of a company like Microsoft
You're new to Azure I guess.
I'm glad the outage I had yesterday was only the third major one this year, though the one in august made me lose days of traffic, months of back and forth with their support, and a good chunk of my sanity and patience in face of blatant documented lies and general incompetence.
One consumer-grade fiber link is enough to serve my company's traffic and with two months of what we pay MS for their barely working cloud I could buy enough hardware to host our product for a year of two of sustained growth.
No need to worry, it's already happening. While I have not withdrawn anything (yet?), I stopped publishing new code to GitHub. I can't be the only one.
I was the one who suggested making it a prequel and have scientists watching
you and from behind the windows (tough I'm pretty sure Nyko forgot by the time
he completed the mod). Odd seeing this mentioned here.
I still have a toe in the Source modding community and I'm watching Desolation
with great interest. An absurd amount of effort went into this, augmenting the
engine, the editor, inflicting vgui upon themselves…
Source is _not_ a flexible and cooperative engine, lots of hardcoded stuff,
necessary workarounds, complicated workflows, but there's still a modding and
mapping community and my only wish is for our Lord and Savior Gabe Newell to
release the sources of Source (1), GoldSrc, and the tooling around them.
So much could be done. I should mail him, iosource needs to happen.
> As of June 3, 2021, there is no native support for Vulkan API provided by Apple devices.
> Apple deprecated OpenGL in iOS 12 and macOS 10.14 Mojave in favor of Metal, but it is still available as of macOS 11 Big Sur (including Apple silicon devices). The latest version supported for OpenGL is 4.1 from 2011.
OSX accounts for 2.62% of Steam users.
Implementing another graphics backend is prohibitively expensive for small studios whereas you could implement either OpenGL or Vulkan and get the other 97.38%.
And that's without factoring in the required investment in single-use hardware, people, and skills.
DirectX is another safe choice but I try to stay away from anything proprietary or Microsoft-related.
After a cursory search it seems my Parisian-ish accent is at fault: https://fr.wiktionary.org/wiki/Annexe:Prononciation/fran%C3%...