plexchat

7 ms·

1.
by plexchat 10y ago
Yes because the code emitted by a compiler is directly proportional to the size of the specification? I fail to see the point.
2.
by plexchat 10y ago
Source? I've never had an issue compiling legacy code.
3.
by plexchat 10y ago
Old news. See https://www.reddit.com/r/cpp/comments/4ibauu/visual_studio_a...
4.
by plexchat 10y ago
It's somewhat analogous to how we went from 16 bit registers to 32 bit registers with the extended opcode variants, so if you understand x86, x86_64 isn't really much of a stretch.
5.
by plexchat 10y ago
I hate to be a naysayer because this is great work and all, but frankly, managing all these platforms is going to be a nightmare. In a traditional engine, the code for each platform is embedded at the lowest level of abstraction. That is th
6.
by plexchat 11y ago
I think these are salient points. Part of my rationale for writing it the way I did is that howistart is slightly editorial in nature and is a collection of opinionated overviews of a professional workflow by design. In the real world, C++
7.
by plexchat 11y ago
The speed of the GC isn't the issue (although it certainly can be). The non-determinism is. It's hard to control when a GC should happen, and when it happens at a bad time, the ramifications are perceived as an awful user-experien
8.
by plexchat 11y ago
Other languages , not all other languages ^^. Yes of course there are several languages that map more directly to one's mental model of how code is executed. Rust (which you're working on) is an one such exception. Optimization
9.
by plexchat 11y ago
At PlexChat[1], we intend on using C++ to write a lot of our infrastructure (where it makes sense, that is). The language has advanced significantly in the last decade and writing idiomatically correct, and safe code, is much easier than it