In the many years of commuting to an open plan office I think 4 hours was probably the max, and usually it was less.
Since working from home, I'm not sure exactly but it's a lot more, and honestly it's more than is healthy. I'm still less tired overall though.
Honestly this is usually bad advice nowadays, for a bunch of reasons:
Modern allocators do the same thing as object pooling internally, usually faster. They rarely interact with the OS.
A GC will do things like zero old memory on another thread, unlike a custom clearing function in a scripting language.
Object pooling breaks the generational hypothesis that most modern garbage collectors are designed around; it can actually make performance much worse. Most GCs love short-lived objects.
Object pools increase code complexity and are very error prone; when you add a new field you have to remember to clear it in the pool.
If you are in a non-GC language you probably want something "data-oriented" like a slotmap, not a pool of object allocations.
Having said all that, it still all depends on the language/VM you're targeting. The guy in the video clearly benchmarked his use case.
If I went back to the early days of C, it would be because John Connor sent me there in a time machine to destroy the first compiler before it could become self-hosting
lmao. as long as the people selling the stolen art pinky promise that the art theft machine didn't steal any art, everything is above board
Game engines had a lot of growth speculation for the past decade. There were a lot of harebrained ideas about how game engine tech could disrupt loads of existing industries and provide the foundations for various new ones. e.g.
And so on.
For every idiot idea there is some large R&D team full of poorly-managed developers desperately trying to apply unity's completely unsuitable technology to a problem it can't solve, on the off chance that one of them turns into a money printer. There's also probably a bunch of marketing people, sales people and suits trying to get past regulatory barriers, etc.
Whenever reality hits on one of these hype bubbles, a lot of people get fired. It just happened to VFX, for example.
I don't think TIOBE rankings mean much, but C# is genuinely doing quite well.
In the games industry it has become the only language that is commonly used both for entry-level gameplay scripting and for implementing game engines.
It still has a lot of overhead compared to languages like C++ and Rust, but has proven to be a workable alternative for games that aren't straining against the limits of modern hardware.
Aside from the anti-labour implications of this stuff, even as a consumer it is horrifying to imagine a world where we are constantly questioning whether or not some media was generated by AI. There's something violating about it.
I don't care if a machine learning system is being used in some very self-contained way, like to do basic voice-to-speech in a game with a lot of procedurally-generated text. That can even be an important accessibility feature.
However, as soon as it's being passed off as a real human performance with emotional depth and authorial intent, it's gross and I don't want it in my brain.
This actually could have been much worse. I heard they are trialing a system where they lay off one employee every time unity is installed, but luckily there have only been 1800 installs since September.
I use a Tokonami KX450, which is not the newest but it's the most widely available military-grade model that the average silicon shop is able to customise.
With that in mind you'll want a uranium microreactor to really get that turbo button cranking out the keycodes (the french stuff is cheapest but ukrainian kit is worth the extra), as well as a mercury cooling solution and ideally a set of maglev keys for all the most common letters (NOT backspace; frankly you should remove that key entirely to avoid habits that damage your WPM).
Assuming you've got a solid pair of high-torque power gloves that should get you up to at least 20000 WPM, which admittedly won't cut it if you're trying to keep all the NPM dependencies up to date in a modern bank's transaction processing software, but it's probably enough if you're just doing a bit of data analysis in python.
The real question is how we got any portable solution to this problem in the first place.
To me problems are fundamentally economic and political, not technical. For example, the unique circumstances that led to a portable web standard involved multiple major interventions against Microsoft by antitrust regulators (in 2001, 2006, 2009, 2013, etc). The other tech giants were happy to go along with this as a way to break microsoft's monopoly. Very soon after, Google and Apple put the walls straight back up with mobile apps.
If you go back before HTML, OS research was progressing swiftly towards portable, high-level networked GUI technology via stuff like smalltalk. Unfortunately all of the money was mysteriously pulled from those research groups after Apple and Microsoft stole all the smalltalk research and turned it into a crude walled garden of GUI apps, then started printing money faster than the US Mint.
Whenever you see progress towards portable solutions, such as Xamarin and open source C#, React Native, or even Flutter, it is usually being funded by a company that lost a platform war and is now scrambling to build some awkward metaplatform on top of everyone else's stuff. It never really works.
One exception is webassembly, which was basically forced into existence against everyone's will by some ingenious troublemakers at Mozilla. That's a whole other story though!
Most common reason for being bad at programming is finding it boring and thinking the tools are needlessly obtuse.
If anything this is a sign of great intellect.
this would make a great print, no joke
What a bunch of elitist horseshit.
As a senior engine developer at a games company, this is how I see it:
To me it's not really excitement so much as "oh god how do i make this ridiculous language do the correct thing".
I'm way more scared of rogue implicit copy constructors. I wonder if cppfront has any plan to fix problems like implicit copy and pessimising move.
I mentioned it elsewhere here but I think the Terra research language has explored this area more thoroughly than Rust, just because that's its only purpose. The website and academic papers are definitely worth a skim: https://terralang.org/
It's basically a powerful LLVM-based compilation library exposed where everything is exposed through Lua bindings. The default Terra compiler is just a Lua script that you can pull apart, extend, rearrange, etc. It's all designed for ease of experimentation, whereas Rust has to worry about being a rock-solid production compiler.
Honourable mention to C# source generators too. They are janky as hell but very effective.
If I understood correctly, the closest thing I know of to what you are describing is probably Terra:
https://terralang.org/
It is an academic project with various papers presenting case studies that do things like change the whole programming paradigm the language, or the execution model, or the syntax.
The wider paradigm is called multi-stage programming. The other obvious languages to mention are the lisp family, and more recent spin-offs like Julia.
The biggest selling points are probably the developer community, the ease of console support, and the larger track record of commercially successful games. Plus if you are a beginner the resources that come with a commercial tool can make a huge difference.
In a perfect world I'd just recommend the open source thing to everyone, but if I knew an artist who wanted to make a game I'm not sure that would be good advice.
Three things off the top of my head:
Yeah, I came across that. I presume it just uses the GCC statement expressions extension under the hood.
No can do though, it has to work with MSVC too.
in 100 years all smartphones will look exactly the same as now, except they'll all have the hapsburg jaw