11 ms·
I found this to be a great reminder of how far we've come in 16 years, but it's also a reminder of how little some of the basics have changed. We still advocat
by falcolas 12y ago
I found this to be a great reminder of how far we've come in 16 years, but it's also a reminder of how little some of the basics have changed.
We still advocate going down to A lower language for the fast boys, but we can more or less forget about having to write ASM for all but the most complicated algorithms.
We still fight platform differences, and DirectX is still one of the most powerful and developer friendly frameworks.
Low level knowledge is still mocked by some individuals, yet C++ is still the God of graphics and video games.
- emodendroket 12y agoIs it not the case that many/most games now are some smaller C++ components being scripted by something higher-level?
- dfox 12y agoThat was the case in second half of 90's and 00's, today most engines got back to C++ plugins (or plugins in same language as engine itself) and simple declarative logic in game data. (this has to do with both performance as with various walled gardens that do not allow general purpose scripting)
- emodendroket 12y agoThe Apple App Store has allowed scripts for some time for this exact scenario. I'm not sure which other walled gardens you mean though.
- deleted 12y ago[deleted]
- emodendroket 12y agoWhy would that be a reason to prefer to implement your entire game in native code?
- mkehrt 12y agoUh, yes they can, and have been able to for years. What they can't do is download and interpret code.
- dfox 12y agoIn that 16 years, we got new (and mostly unnecessary) layers of abstraction on what existed previously. Whole single-page-application crowd (eg. Sencha, React...) is busy reinventing things that already exists three layers of abstraction down from the level on which they code. DirectX was interesting in that age because of exactly the thing in article: you can allocate sound buffer and one surface and view that two COM objects as hardware and not care much about performance implications of the abstraction in between. Once you start drawing to (to borrow X11 terms, as I'm not too familiar with GDI/DirectX) IndexColor surface that is shown on TrueColor display, you get slowdowns in the abstraction layer on the order of "2005 highend Windows NT workstation renders at 2FPS what random office computer from '94 on DOS rendered at 60FPS" (see OpenTTD for example of exactly this performance regression). For last 25 years hardware acceleration for graphics is readily available for all performance tiers but still, you need to have quite low-level understanding of how the hardware works to get reasonable performance (and as for working-around hardware and driver bugs, we are currently in mostly same situation as 25 years ago and it was better in the meantime).
- moron4hire 12y ago>> Whole single-page-application crowd (eg. Sencha, React...) is busy reinventing things that already exists three layers of abstraction down from the level on which they code. Except, you know, that part about running on the open web. The web is a deployment platform. Developers want to write the least amount of code to be able to support the most users possible. That was supposed to be Java, but it didn't work out that way. Deployment is still a platform-specific issue in Java, because users--for whatever reason--hate WebStart and its ilk. Add to that the fact that smartphones just plain don't support Java in that way and suddenly the browser makes for the only pragmatic cross-platform toolkit for building applications. Yeah, JS sucks. Yeah, DOM sucks. Objectively, they are terrible. But for as bad as they are, there aren't any good alternatives. And no, building from source is not an alternative.
- TheOtherHobbes 12y agoBuilding from source is happening anyway. The browser is pretty much a js logic/html+css view compiler. It just JITs it when the page loads instead of creating a downloadable binary. With node/io and Go, servers have been build-from-source for a while. Given the snarly mess of frameworks/tools/languages/abstractions used in web dev, it's not obvious you'd get worse performance or inferior code using JIT LLVM and some newly minted update of Visual Basic or Swift with component/object/view caching.