2,796 karma · joined July 16, 2012
Thanks for the comments/annotation!
I used dark schemes for years but having switched to a light one in recent months, I don't see myself switching back. This area is mired in dogma unfortunately.
If I started my career in the current era, there is no chance I would have been able to afford to develop in the Apple ecosystem (not just yearly subscription, which is crazy to me, but also the cost of the hardware as you point out).
Absolutely NOT! UE4 has great tools and awesome APIs for creating content from the perspective of an artist. The runtime, unfortunately, is mired with legacy code from a bygone era. It is also restricted by the need to maintain mobile support. Compared to an engine like what idTech has, or Activision, or Ubisoft, etc. the UE4 runtime is probably 10 years behind. There are numerous techniques such as those mentioned in the linked post that are simply not possible in UE4 because of how dated the RHI layer is.
Epic relies heavily on deploying Fortnite in order to test the Unreal Engine at scale. Fortnite itself is, in some sense, the test bed from which many improvements and fixes are carried back to the mainline engine. Any studio or publisher relying on the Unreal Engine to deploy to iOS or MacOS would be more or less immediately effected, especially given the volatility of Apple's APIs.
It's like when they made the argument why Netflix/Spotify should pay them 30% of the proceeds of all sales because it's good for consumers and people actually bought it.
I think it's just important to realize that spending isn't always a strictly rational process. That said, there are definitely significant pieces of engineering that go into a keyboard. Here, the keyboard is fully programmable and you can flash the firmware. For some people's workflows, this might be very important. No keyboard in your price range will allow that. This keyboard is equipped with a low-power ARM cortex, which means it can handle additional logic a typical keyboard can't. You can use "layers" and swap between them at a hardware instead of a software level. This means you can take your keybindings with you as opposed to needing to change the OS settings when you switch computers while using the same keyboard. If you have actual wrist issues due to an injury, frankly I would pay even more money than this to ensure that I can type pain-free or that the symptoms don't deteriorate. As someone that's worked in hardware, I can say first-hand that the plastic injection molds are extremely expensive for products not sold at a massive scale.
I could go on. I'm not a "keyboard collector" or anything, but I do have a keyboard that cost me over 100 dollars, and having used it for eight years now, I consider the price entirely reasonable given the utility its afforded me, and the longevity. Not to mention that I can replace keycaps if needed, I can replace the cord, I can reprogram it as my needs change, etc.
I can understand if English isn't your first language, that's not a problem. Tone-wise, I think if you genuinely are curious about something, just make that clear. Otherwise, the question comes off as a rhetorical one, where you're "asking" in the sense of "why anyone would be so stupid as to spend this much money is beyond me."
My two cents (as someone that doesn't have a fancy keyboard).
It's not just that. Basic patterns in C# are known to have pathological performance problems (implicit boxing, implicit heap allocations) that you simply don't run into programming in C or C++. These are things that tank performance in day-to-day programming that do not show up in carefully tuned benchmarks.
Source: Helped profile lots of C# games (not IL2CPP with Unity, although that's pretty bad IMO as well), not pleased with what I saw.
Also I’ve heard that argument a ton. It’s total complete rubbish as far as I’m concerned. Extrapolating, if you see a function call, what really can you say about the “cost” of that function? To me, without actual investigation, the answer is zilch. The function might be inlined, in the i-cache, referencing a lazily loaded symbol. It might be a small function, it might be huge, it may flush the cache, idk. If the goal was to be able to estimate the performance at a glance, well, we should use assembly, and even then the performance isn’t always clear.
A control flow problem worth solving is understanding async and multithtreaded code.
And yes the expressiveness of actual infix operators is, to me, a strict requirement. The language is for humans, not machines after all, and stuff like add(mul(add(a, b), mul(a, c))) for, say, dual quaternion a, b, and c is a non starter. Most of my code would unfortunately become unreadable and there are often no sensible variable names for those intermediate results.