pouët.net

Hi!

Tomorrow begins Amiparty in which it is not only about the Amiga, but generally about an alternative. Some of us will bring Linux-based machines.

I wonder are there demos, which were originally designed for Linux (and which were then eventually ported to other platforms). Searching pouet is hard to guess whether it was opposite situation. First - production on Windows and then on other platforms.

What do you think, what productions should we show on Linux?

Thanks!

bbdemo ? do you like textmode ?

fortnight and space cadet from mfx.

http://www.pouet.net/prod.php?which=51762 uses specific Linux h4Xx0ring techniques to get to 1k.

helsinki-spiegelberg by tsygä

Use some sort of virtual machine to run windows. Problem solved ;)

Oh, it's actually pretty easy to figure out because most of the linux-ones suck.

http://pouet.net/prod.php?which=52218 this one is linux only :)

The problem of most linux demos is that they DON'T WORK on any recent distro. With or without source.

I realize this is not answering your question but... For linux demos libraries are all the fuck over the place and named all sorts of different things. If more people can release a static binary that would definitely help. You can offer it along with your tiny dynamic binary, if you feel it's too big. It would help a lot- thanks. I'm not a big fan of hunting down libwhatthefuck.1.2.3.so in order to run your demo.

sigflup has the leading.

I don't think there's much point in releasing e.g. Linux/x86-exclusive demos (apart from some obvious platform-specific experimentation). Here's why:

1. The only way of releasing future-compatible binaries on UNIX platforms is to release the source code, and even then it is not guaranteened that the end user is able to compile the code on the first place. If you want to release a binary, it's always a much better idea to release e.g. a WINE-compatible Win32 binary instead of, say, a Linux/x86 binary.

2. It's very difficult to be Linux/x86-exclusive, as some other X86 operating systems (like *BSD) happen to support Linux/x86 binaries quite decently :)

My comment to this possibly old thread. I'm sorry if thread-resurrection is not commonly done here. However it if it done, nevermind the former sentence.

Linux-based operating systems are the way to go. Opensource equivalents of the usual programs will most likely be developed.

And I don't think you can call yourself a hacker, and not get into what linux is about, and then reboot into windows, and have yourself a good laugh.

And if you read my thread about audiovisual optimization of Linux-based systems, really trying to run windows at those kind of rates, whatever the hz does these days (interrupts?), say switching it to maximum, which is 1000hz, with some unknown shareware, made by some poor developer, who probably had to read through obscure documents, in order to do that.. windows stumbles.

I am running Linux at 3 times that speed, at it is excellent.

I don't know what the closed source mindset of common demos are either. You are not making any money on it. Why not open it up, and benefit from eachothers code, and spend less time zombiefying yourself, just to get that effect, the other guy had. At the expense of normal life, and activities.

Infact, to me, open source, atleast GPL, represents much more the times of 64k machines, where the assembly could be listed, and it wasn't too much to go through, and you could learn from the code from there. However the projects are much larger now, and it isn't feasible.

sorry, demo hackers in general hate linux for a bunch of good reasons. Welcome to reality Neo.

also, what is that 1000 hz thing about? A simple window cleared to black every frame runs at > 3000 frames per second in this old windows laptop I have, nothing special to do... so, what is that linux audiovisual optimization thing about?

iq: don't waste your time trying to have a serious discussion with a previously banned troll.

That perfectly sums up what demoscene is about :)

actually, it is possible to create demoscene "linux compliant" demo, but to do so they should:
- have an opensource license.
- be packaged the linux way, with a config / make / make install scripts, ( which represents some works, but there are tools for that. Note that should fix the different linux/bsd version problems),
- the author/porters should post their packages to most popular distributions 's depots, and subscribe as maintainer of these packages.

searching for "demoscene" at the ubuntu default depots, you can find "amoeba" packaged correctly.
( Thus the ubuntu maintainers can recompile it and test for compatibility at each new releases)

Its the schedulers timer frequency for context switches, iirc.

higher: more interactivity, less throughput, but also more overhead
lower: more throughput, less interactivity, you get it...

why?

...So that the demo's package can be maintained and ported.
I'm not telling anyone to do that, I'm just pointing out that it's the way linux work, and that the whole package/maintainance thing (config/make/install,..) is the real reason why some linux demo may become incompatible with new updates. These things also manage package dependancies, another reason that could forbid a single spreaded executable to work.