Nightdrive
191–200 of 256 posts
Re: Nightdrive
#192I'd call this a "demo" for sure -- harkening back to the mid-90's when people built things for fun / just because they could / to explore
Re: Nightdrive
#193Re: Nightdrive
#194Nice but I usually turn my lights on when I drive at night :-)
Re: Nightdrive
#195> ’Maybe it's a "demo"?’ There’s a long-standing tradition of people creating realtime graphics software on personal computers that doesn’t offer any interactivity. They are indeed called demos and the community is called the demoscene. It goes back to the late 1980s and had a golden era in the mid-90s on Amiga and PC. (Pre-Internet, watching and making demos was one of the few socially and creatively oriented things…
IMO the author could very much submit this to a demoparty in the "demo" category (assuming they'd substitute the music with a fitting original work). These days, the only notable difference between demos and intros is file size. If it's bigger than 64kb, it's a demo. You can totally have a short, single-effect demo like this one, and there's plenty such demos out there. Ergo, I disagree, I think this counts as "full-…
Re: Nightdrive
#196Re: Nightdrive
#197> ’Maybe it's a "demo"?’ There’s a long-standing tradition of people creating realtime graphics software on personal computers that doesn’t offer any interactivity. They are indeed called demos and the community is called the demoscene. It goes back to the late 1980s and had a golden era in the mid-90s on Amiga and PC. (Pre-Internet, watching and making demos was one of the few socially and creatively oriented things…
Re: Nightdrive
#198Earlier quoted context omitted.
Great work on this though! Super impressed. Would be fun to clean it up and convert to typescript.
Honest question. What do you see "not clean" in the original code?
A compiler would tell me what all the types should be and if they are being respected. I'd also write a lot of unit tests to make sure that the code is doing what it is expected to as well as enable refactoring more easily. The code isn't formatted consistently, so that also makes it hard for me to read, I'm kind of OCD about that and having tools like eslint/prettier, which do it automatically, makes this super easy to fix. Linting the code would also point out other issues that the compiler misses. Putting it into CI would ensure that all changes get checked and builds would fail, if there are issues.
So I guess that is what I mean when I say 'clean it up'.
Re: Nightdrive
#199I'm amused that we share initials and a passion for this kind of project! Mine's https://rezmason.github.io/drivey . One key difference: this guy built his demo from scratch, whereas mine's a port of someone else's work. It's great to see another implementation, with its own techniques and features.
Amazing to see you in comments; your version was inspiration for this project: https://twitter.com/j_miskov/status/1490358867104083972 The video didn't generate much interest so unfortunately I didn't release anything playable.
I can't take credit for Drivey's aesthetics, I'm just honored to have carried it to HTML5 ;) Somewhere out in Australia is the original programmer who I'm sure would love to see this, but who also loves avoiding the spotlight.
I just did a quick scroll of your Twitter feed and jeez you're prolific, this stuff is really cool. I'll try Hexpress this weekend.