"The scene is dead" has become a meme by now. For example the "new talent" Meteoriks award is introduced with "For a scene that has been dead since 1999, our walking dead are pretty fresh". It is well alive. Sure, we still see some of the same people from 1989, and the average age is certainly going up, but it absolutely doesn't mean we aren't seeing new blood. Styles change, technical achievement is usually seen in…
The demo scene is dying, but that's alright
51–60 of 127 posts
Re: The demo scene is dying, but that's alright
#52I would love more outlets for creative coding, I feel like neocities is a bit like that. That said there isn't really a scene or real sense of community (AFAIK). I mean someone liked something I uploaded once, but I never interacted with them again. Cohost had fun vibes like that as well, but I guess it's no longer with us. Same with Glitch, but admittedly I didn't use it in the last few years, but it was my go to op…
Re: The demo scene is dying, but that's alright
#53The demo scene inspired me to keep my next‑gen terminal [0] tiny: it is under 5MB (Mac download was once 900 KB) and my aim is to get all downloads down to ~1MB. If demosceners can do it, regular indie devs really have no excuse. This scene isn’t dead; we should just look beyond 3D glitter. See File Pilot [1] for another compact, clever example. [0] https://terminal.click [1] https://filepilot.tech
Re: The demo scene is dying, but that's alright
#54Earlier quoted context omitted.
For me, one of the greatest examples of this style is Reaper[0]. A completely functional professional audio DAW in a 12 to 20MB download (depending on your architecture and OS). -- 0: https://www.reaper.fm/download.php
On one hand, seeing multiple megs described as slim makes me want to pinch myself, because that’s very far from my understanding of reality. On the other, today these apps always seem to include a bespoke toolkit of some description (as both File Pilot and Reaper demonstrate), whereas slim golden-age Windows apps leaned very hard on the GDI/USER/COMCTL one, and those libraries are quite hefty. (Unlike, say, the Visua…
We shouldn't forget that half of the documentation on how everything should work was only released after anti-trust investigation and pressure from courts.
https://www.geoffchappell.com/studies/windows/shell/index.ht...
By that time, Windows had already switched to shiny fresh undocumented technologies.
You should remember that a lot of software around the Millennium simply re-implemented latest fashion trends (Office controls, XP styles, etc.) on their own in not quite exact ways, not just because programmers back then wore skins, and ate raw meat, and feared nothing, and because such third party toolkits were available commercially, but also because official interfaces to do the same were not offered until later releases (or sometimes ever). I vaguely recall discussions of teams within Microsoft sometimes doing the same, resulting in Office controls sharing no code with common controls used by the rest of the system which look exactly the same.
The irony is that web browsers, being the most popular kind of application, and interfaces built on top of their technology simply ignore the native interface toolkits, and do everything independently, which is even more extreme than some old school custom paint handlers. A lot of work has been spent on re-implementing native look and behaviour there, multiple times.
One of the examples of actively supported applications interfacing with shell object hierarchy without using system dialogs I can name is Tixati, which needs to have file picker(s) at hand inside its own dialogs. It's not open source, but it has been using GTK, custom controls, and probably some sauce on top. Given the user complains about its performance or missing items, and regular appearance in change log over the years, I'd say it's a wrestling game for the author. At the moment the tree is lazily populated at the first appearance, which is fine, but not unnoticeable.
It is a bit hilarious that showing a list of file names in some directory is a trivial example on using system-provided iterators for the novice programmers, but adding icons matching those that Explorer shows (handling links and other special files, special directories, non-filesystem-based locations which still have files user might want to choose in them, etc) to that list suddenly becomes a nightmare.
Re: The demo scene is dying, but that's alright
#55"The scene is dead" has become a meme by now. For example the "new talent" Meteoriks award is introduced with "For a scene that has been dead since 1999, our walking dead are pretty fresh". It is well alive. Sure, we still see some of the same people from 1989, and the average age is certainly going up, but it absolutely doesn't mean we aren't seeing new blood. Styles change, technical achievement is usually seen in…
https://www.youtube.com/watch?v=IFXIGHOElrE https://www.pouet.net/prod.php?which=59105
Re: The demo scene is dying, but that's alright
#56In all fairness, the conditions that saw the demo scene rising are so remote to be almost incomprehensible to the new generation. "You see, when a cracking crew beat the protection of a new game, they would upload their hacked version to an elite BBS and repackaged it with a little intro and a trainer. They had to be very creative and skilled, often working directly in assembler, in order to achieve impressive imager…
Re: The demo scene is dying, but that's alright
#57Earlier quoted context omitted.
The very broad definition is people who write artistic shaders frequently limited to a binary size, sometime 4kb, sometime 16.
That's a very narrow definition, really. In general demos have neither much to do with shaders (except insofar that you have to write shaders to do 3D on GPUs), nor are they size-limited in general; only certain subtypes are.
Re: The demo scene is dying, but that's alright
#58Re: The demo scene is dying, but that's alright
#59The demo scene inspired me to keep my next‑gen terminal [0] tiny: it is under 5MB (Mac download was once 900 KB) and my aim is to get all downloads down to ~1MB. If demosceners can do it, regular indie devs really have no excuse. This scene isn’t dead; we should just look beyond 3D glitter. See File Pilot [1] for another compact, clever example. [0] https://terminal.click [1] https://filepilot.tech
Early access for a terminal... $60 for a (year subscription???) file explorer... I expect more MBs if I'm paying for these things!
Re: The demo scene is dying, but that's alright
#60Earlier quoted context omitted.
The vim and emacs guys had to join forces to flame the greater evil - Electron-based editors.
And they’ve lost. Everyone and their cousin uses Electron editors while showing up to FOSDEM on their MacBooks to discuss kernel development. It’s already long over. We’re just starting to notice. The EFF is baffled - why do they yell in a void now, when just a decade ago they stopped SOPA/PIPA with dramatic effect? The free internet and the communities that support it have lost their voice and their cultural support…