u/gargamel1497

Title. How do I make the raylib window stay always on top, even when the program does a fork()-execve() and starts another program?

I've looked through the cheatsheet, but I haven't found anything.

Any help would be appreciated, thanks.

Hi.

How to play an inbetween version on consoles other than the Xbox 360?

As, you can play the disc version, which is usually the oldest version available for the given platform, or update it to the latest version, which is either 1.12 or 1.13.

On the Xbox 360 it's trivial to download Title Update files from the wiki, put them onto a random USB stick, and just have them working.

But how to do this for the other consoles the LCE is available on?

The wiki does not have any links under the release pages like they do for the 360 Edition, and, having done some research, while our dear sea-people have archived the initial version of pretty much every LCE edition, the inbetween versions are nowhere to be found.

Someone might say it's impossible.

That would be a fair point, but there are YouTube longplays of TU31 on the PS3 Edition, which means that at least this one version has been archived for a non-360 console.

If anyone knows more about the topic, I'd be grateful.

What are the best file systems for storage drives? That is, drives or partitions that do not contain the operating system, but are instead used for backups, data storage, and such.

By "the best" I don't necessarily mean the fastest. The hard drive in question is a mechanical one, so its speed is limited anyway.

Right now I'm using NTFS simply because it's the most portable file system I know of. Every single operating system I use (except for NetBSD....) supports it, so I can access the drive from every system I want, except for NetBSD of course.

In FAT32 the maximum file size is 4 gigabytes, and sometimes I store virtual machine hard drives in there, which are most often larger than that.

ExFAT meanwhile doesn't seem to support UNIX permissions which is a bummer as I also store executable shell scripts over there.

The Fast File System used by NetBSD and OpenBSD is nice, but it's only supported by those two operating systems and there is no way of mounting it anywhere else.

Linux ext file systems have a similar problem. ext2 can be mounted on BSD systems, but ext3 and ext4 can't. Windows can't read or write to either. Yes, Linux Reader exists, but in practice it tends not to work the way it should.

HFS+ is a really cool file system, having been designed for a non-UNIX operating system, later adapted to UNIX needs.

There is a FUSE driver for HFS+ that can be installed on any Linux distro (and I assume on OpenBSD too), and, for once, NetBSD supports HFS+ natively. Or so I'm told. And Mac OS X obviously supports it. But Windows doesn't, and I happen to use it once in a while.

So, I think, the question should really be worded as: Are there any files systems that are supported by all Unix-like systems (including NetBSD) and Windows, that allow files to be larger than 4 gb in size, and that support POSIX permissions.

Thanks.

A few days ago I noticed that when you collect an item to an already existing stack on the hotbar in the 360 edition only the counter increases.

But I can distincly recall the item stretching upwards and back down again in every other edition.

Investigating this reveals that this item stretching is disabled on the 360 but enabled on the PS3.

With every such discovery I'm beginning to regret getting a 360 in the first place, as it's the second time the PS3 edition has proven itself superior.

After a half-year-long Java project I'm writing something in C and the lack of a garbage collector can be positively felt in terms of performance but at the same time managing all the pointers can get messy.

There's a whole nother language decidated to solve this problem (while creating a thousand more), but there's got to be a simpler solution.

And yesterday I thought, why not just mark the ownership of the various pointers I've got in my project?

By ownership I of course mean which struct (I do use OOP, sorry) is responsible for freeing that pointer.

And I #define'd three constants.

The MANAGED constant means the struct that contains the pointer has to free it.

The FOREIGN constant means that it's somebody else's job.

The SHARED constant means that it ought to be someone else's job, but it may not be freed when the program exists and should thus be freed.

I place them before the whole declaration in this manner:

MANAGED FONT *fontGothic;

SHARED struct WORLD *currentWorld;

FOREIGN struct PERSON *thePlayer;

This doesn't mean anything to the compiler, but it's just a quick way of telling me what is what.

It is definitely a very stupid idea and I apologize for posting it. I'm just a silly dude who does silly things.

Hi.

Do the legacy console editions use the system language or do they use the language they have preinstalled on the disc?

The context is that I have a PS4 Edition disc that has an ugly ahh sticker that proclaims it is translated into the local language, and when booted on a friend's console it indeed shows up its hilariously translated UI in the local language.

And I wonder whether this disc could be used to play Minecraft the right way, that is, in English.

That friend's console was set to use the local language as its system language, so that might have been it (I don't have a PS4 myself), but the sticker can also mean something.

And today whilst I was reading the Wiki I stumbled across a changelog for some old version of the PS3 edition which said that some translations were added.

The legacy console editions don't have an option to set the language, so this is where my system language theory comes from.

I'd appreciate being enlightened on the matter. Thanks.

The source code of the Java Edition is in decay. We can all experience it by looking at how unplayable modern versions are without performance mods.

But performance is not the only thing. Bad performance is a result of overengineered code.

When I was making mods for Indev and Infdev during the beginning of my career the codebase was very simple and well-structured. The main class contained a lot more than it ideally should, but it's the fate of all Java codebases and there is no running away from it.

A few weeks ago I was revisiting 1.11.2 Far Lands and I noticed that the code was now a bunch of Factories.

I haven't seen the latest source code (why would I?) but seeing the dramatic change I'd bet it's ridden with layers upon layers of abstraction, factories, and so on.

String IDs are a huge part of it. Old Minecraft used numeric IDs. Later, in 1.8 I believe, shortcuts were added, but they still just pointed to those numeric IDs.

In 1.13, everyone's least favourite version, the numeric IDs went away for the most part, replaced by stringId's which are by definition much slower.

Bad performance is a byproduct of "good code".

And, on a sidenote, the reason the LCE runs so well on such old hardware is partly because 4J didn't give a phick about good code.

In Java when they ran out of space in the texture atlas they removed it, implemented automatic atlas generation, and all that nonsense which only wastes CPU cycles and makes the thing slower.

4J just increased the size of the texture atlas. Yeah.

Old Minecraft had two classes. Iirc their names were Block and Item, and they stored the static instances of every single block and item in the game along with their IDs and such.

Modern Minecraft probably has registries instead of this. And yes, for mods it is a godsent, but not so for performance.

That's been some yapping about things most people don't care about, so sorry about that.