1,081 karma · joined August 9, 2018
These days I'm doing WebGL and ThreeJS is not fun either with upgrades, depreciated functions.
The whole ecosystem is a mess these days. I need to shave my beard.
One of the advantages for me: most people assume that "art projects" generally don't start with the expectation that one is going to profit insanely (contrasted with the perception when one says "I'm doing a startup"). The measure of success is simply getting the work out there into the public, that is all an artist can do. The rest is up to the consumer.
This is the perspective that works for me and keeps me happy and humble. For me, when I gave up trying to control other peoples perceptions of myself, my life became much easier.
(edit: I'm doing something in the NFT space, so it's also technically true as well as metaphorically) YMMV.
As a side note - AMOS on the Amiga was awesome, and PDS on DOS (with SVGA libraries) both me to start my first business when I was 15 (through-the-window real-estate listings). Even then the shame of being a basic programmer stayed with me, I would deliberately compress, use a 3rd party linker & hex edit the beginnings of compiled programs (on PC) to ensure nobody could work out that I was using compiled QBX (quick basic). I continued with VB, Blitz and the like until learning C# with Unity... then I felt the shame of not being able to do the equiv. of 80's assembler (shader programming).
Perhaps one day I'll get over myself and believe I'm not a lamer at heart :-)
I often think I was born a few years too late, things moved so quickly and I was a bit too young... TRS-80 -> Amstrad -> Amiga by the time I was 14 - and the Amiga was really complicated with it's custom chips.
Anyhow. Just a bit of a rant ;-) Thanks for reading.
p.s. Oh, just thought I'd add that I also played with RISCOS and BBC Basic during the period mentioned above and was blown away by how all the OS functions and so on were exposed to BBC basic, for me, this has always been the problem with Basic variants. Doing SVGA graphics on the PC with QBX required 3rd party libraries, proper TCP/IP under VB required IP/Works, and so on... back then I was always struggling - not with optimisation - but with access to features I needed that weren't offered through whatever dialect of basic I was using. BBC Basic on the other hand seems to be done right, I expect you could write any application you cared to without resorting to C or assembler.
I opined during the whole installation process: something is very wrong with the modern computing industry when a user feels the need to wind the clock back 10 years (and go to the substantial trouble of doing so) to obtain needed functionality when there is no legal alternative. (i.e. I licensed CS6 in 2012, I was used to paying 600 or so dollars every few years for an upgrade, but I'm done with paying another cent for "renting" creative cloud at it's ridiculous ever-increasing price and CPU absorbing DRMware client. Adobe had me paying since CS3 - and for eight years as a CC customer). Capitalism would dictate that there should be a viable alternative, and yet, there is not.
I also found myself thinking, what have we gained in the last 10 years? Telemetry? Desktop advertisements? New icons? Loss of backward compatibility. Mavericks - to me - seems perfectly usable even 10 years later, however I don't dare to connect it to the internet for lack of security updates.
So... I too wonder if the future of the desktop is retro.
It sounds jaded when I say that if this "rolling back" becomes a mainstream thing, surely big tech will come up with a derogatory term for it: "The Dr. Who's" who somehow undermine progress.
I can't help feeling that we're experiencing multiple business monopolies simultaneously: because in Adobe's case - there was tremendous pushback against their subscription model... all to no avail. Their vendor-lock-in is as strong as it gets.
Adobe's behaviour is also enabled by Apple and Microsoft in this case, newer versions of the OS's do not support CS6, and to use newer versions of Photoshop you'll need a newer version of the operating system.
So what do we get now as locked-in photoshop users? Creative cloud ever increasing fees, Adobe CC software that wastes computing resources, topped off with the privilege of Microsoft or Apple telemetry. Back in the day it used to be called spyware.
How are we moving in the right direction as an industry?
I am completely sick of it.
It seems we're learning the same lessons over and over again about the nature of failure in complex systems. It seems reasonable to me that we'll observe more of these failures as our world becomes increasingly complicated, particularly in social and economic systems.
Perhaps we should be teaching the fundamentals of complex systems in high-school just as we teach basic science? It seems to me there is a distinct lack of appreciation of the nature of complex systems in our culture at a general level.
Just as some people think it would be better to learn statistics than calculus in high school - I wonder if it would be equally important to learn about complex systems?
I'm interested to hear what others think.
I recall the computer based testing before and after the short-term dose of Ritalin. The graph of my body movement and failure rate - I became normal. I could do the task and it wasn't hell under Methlyphenidate. I was relaxed.
On the downside - the change in my behaviour and my ability to be more independent with administration etc. caused my partner and I to separate. My change was too much for her. It makes me sad, however I was an utter pain-in-the-ass for her the way I was. My invoicing and personal accounts were always such a mess, but now I can do these things myself. I'm next-level organised compared to how I was before.
My core work as a strategist / developer has also improved remarkably. I don't rush in and make stupid moves so much these days - and I find myself taking the time to understand things I never had the patience to understand.
In short, I feel like I've been living my life on hard-level my entire life. At 45 everything changed. It's just a shame I wasn't diagnosed earlier, but I didn't believe ADHD was actually a valid disorder.
Generalizations or rules of thumb can actually outperform complex quantitative approaches to decision making. Look at the 1/N heuristic for portfolio management for example.
Anyhow just my opinion - something for your curious mind to consider !
My major friction with basic was OS integration. The Amstrad had "call", "peek" and "poke" which allowed you to call Z80 assembly, read and write to memory respectively. Ever since the amstrad doing anything outside of the interpreter which required OS calls or the like was extremely painful - mostly because of the lack of compatible types (byte, word and so-on). Making a call, passing parameters, and getting data back was always a nightmare that required a C wrapper or assembly work-around. It was a black art for the basic programmer. Back in the day I felt like an imposter; compiling my basic applications, statically linking libraries in the link and compressing and obfuscating... purely to hide my lack of skill... I was an imposter ;-)
Both QBX and VB had a healthy third-party library market, and I recall licensing some great QBX libraries for SVGA support back in the day (I was making through-the-window display systems with a capacitive switch I designed). VB was a little better, I recall relying on IP-Works for projects that required TCP/IP support. DLL distribution could be a pain if not handled right. Realbasic had MonkeyBread software's libraries for OS level integration.
So... hopefully I've established some credentials for being a Basic-head back in the day ;-) Which leads me to a recent experience with Basic that absolutely blew my mind and made me rethink my entire position as an old basic programmer.
Back in the day it was pure shame for me to be a basic programmer. It was slow, interpreted, and anyone in the Amiga community that was leet in any way could code in 68000 and basic programmers were lamers. It was the same all the way back and I've always felt like I was a second citizen back in the day... not only from my leet peers, but also from the OS vendors that treated basic programmers in the same way (BTW I'm over all that lamer stuff these days, I learned assembly for the TRS-80 and wrote a game over covid... my 10 year old self was vindicated!)...
But back to the main point... BBC BASIC! Over covid I got into RiskOS (always wanted an Acorn Archimedes) and played with BBC Basic. OMG! You can do ANYTHING at an OS level with this language, total first party support for all OS api's. Although these days I can program as a generalist in C and the rest; I can't help thinking that RiskOS and the BBC micro did it absolutely right in terms of the basic language. And perhaps this is why basic wasn't really taken seriously was everything to do with Microsoft... why wasn't basic given the same 1st party treatment as it is on RiscOS?
Apologies if my post seems a bit confusing - just a bit of catharsis on a Sunday morning :-) Interested to hear about other peoples opinions... I'm playing with the idea of a basic to Erlang translator... old habits die hard :-)
I disagree here, it depends on how you are going to implement animation. For example, if you're using shaders to manipulate vertexes - that's rendering engine land.
> Physics simulations (fluids, soft bodies/deformables, breakables) are also unsolved in a real time environment.
Yes - and again, depends on where you draw the line between physics and rendering engine if there are code-crossovers on the GPU. You could say architecturally, ok - this is the GPU engine in a very simple case.
> Networking is tough; games have strict latency requirements, and perform all sorts of tricks to minimize bandwidth usage.
Yes - totally agree with you here. This is a deep problem. For this kind of game you probably want a deterministic physics engine so everyone is seeing the same thing (running local physics simulations etc.).
> Input (as you mentioned) is tough too, albeit solved for the most part by now.
Agreed, but it's solved well by specialised 3rd party tools mostly. For example, in the Unity Engine control disconnects etc are still an issue in the base library. Rewired is one solution to this.
> It's also worth mentioning that this is all work needed for a game _engine_ you still need a game on top of it.
Yeah. Managing gameplay logic - again - how does this all come together.
Anyhow, I'm glad they are giving it a shot. It will be interesting to see how it all comes together.
I'd like to see a project actually where someone makes a twin stick shooter without any kind of engine at the lowest level we can get to right now without too much hassle (e.g. GLSL, direct to TCP/IP, maybe FGPA for server). That would be super cool.
EDIT: Just for clarity, I'm not trying to start an argument with you - I suppose we're drawing straws on how to delineate functionality. And further, I don't see a clear game design from this group to start with. If it's just simple shapes like Geometry wars then art pipeline becomes simple - if the physics part of things is simple as well (a little momentum and friction), and the net side of things isn't battle Royale requirements - then it's not rocket science. I guess my point was that GPU programming had a very steep learning curve for me, and I started way back in the dat on 3DFX hardware (I'm not super bright when it comes to paradigm shifts). I think one of the things I didn't see was their idea on what hardware they aim to target and what the game design was in more detail. Back in the day engines were written to satisfy game design - but the most complicated parts of the engine were on the GPU side. Anyhow - respect. You've obviously got some background here as well ;-)
Edit: e.g. good simple twin stick shooter needs at least draw call batching and the rest to draw millions of particles and hundreds of enemies. Then there is the issue of animation — and the rest. Art pipeline ? Textures or vertex colors ? Rendering engine is a pretty big deal. The rest IMHO is pretty simple in comparison...
Assembly was cool back in the day Z80, 68000... then C, but I felt too stupid to learn that stuff when I was a kid. Ugh. ;-)