That’s certainly news to me. Suppose it just really needs the latest version. There was a noticeable improvement to stuttering and fps.

That game is interest though. Some things the community sees as bugs, like the audio glitches, have been claimed as an artistic choice.

• Sable - but you’ll want to use protontricks to install dxvk
• Stonefly
• Far - 1 & 2 are both good, but I still prefer the first one
• Vane
• Lightmatter

It’s on a comeback right now: https://steamdb.info/app/753650/charts/#1m

Please people, these stand alone guides are fine but continual use of the wiki ensures it is kept up to date. These should not act as or be used like a substitute.

https://wiki.archlinux.org/title/Linux_console/Keyboard_configuration https://wiki.archlinux.org/title/Xorg/Keyboard_configuration

The real problem: Define beginner distro

Every user is starting from a different point. There is no such thing as a beginner distro. You can say this distro is good for people who can grasp the idea of a command line or this distro is good for people who have no idea command line interfaces exist, but that doesn’t differentiate between beginner friendly or not.

Just note that if you somehow get out of those meetings, incorrect information will be propagated somehow. Even if you put the correct answers in an email and send it to everyone involved. If someone has a way to prevent that from happening please let me know. It’s killing me slowly.

That was this reality. Very briefly. Remember AI Dungeon and the other clones that were popular prior to the mass ml marketing campaigns of the last 2 years?

Yeah, I’ve been using it for about a year now. It’s a little frustrating that it will learn my misspellings before it suggests a proper replacement, but otherwise I have no complaints. Direct upgrade over the stock AOSP keyboard.

The entire post was off-topic as FUTO does not qualify as open source. That being said, the mods should probably update community rules instead of murdering a discussion thread.

Removed by mod

I’d recommend tmux for that particular use. Screen has a lot of extras that are interesting but don’t really follow the GNU mentality of “do one thing and do it well.”

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

Bash, just because everything else already uses it. That and bashisms have infected nearly all of my scripts as I clumsily bump into the limitations of POSIX string manipulation.

I have found some very fun things with sed branching patterns as a result of these limitations though…

https://www.gnu.org/software/sed/manual/html_node/Branching-and-flow-control.html

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…