Ace17

17 ms·

121.
by Ace17 8y ago
Fun related quote from reddit: "you can tell if someone started game development as a hobby because they ARE using an ECS."
122.
by Ace17 8y ago
Interesting talk with a critical flavour about C++ modules by John Lakos (CppCon 2018): https://www.youtube.com/watch?v=K_fTl_hIEGY&feature=youtu.be...
123.
by Ace17 8y ago
"The question of whether Machines Can Think... is about as relevant as the question of whether Submarines Can Swim." - Edsger Dijkstra (EWD898).
124.
by Ace17 8y ago
IMHO the "casual" reader should be able to understand the body of one function in isolation ; i.e, she shouldn't need to to dig through other functions (callers/callees). This is exactly why all functions should be kept
125.
by Ace17 8y ago
Just because I'm using a C++17 compiler doesn't mean I'm happy with the standard library. I still have to google every time I need to sleep the current thread ; and don't get me started on iostream! However, I'm hap
126.
by Ace17 8y ago
> Would it be nice to know who upvoted you? No. Bad idea IMHO. > So, would you be okay if I saw that you upvoted a comment of mine? Please note this is a entirely different question. But still: no, it wouldn't be OK. I fail to se
127.
by Ace17 8y ago
Testing is like eating. You can do it well, bad, in harmful or pathological ways, in healthy ways, too much, too little, for ideological or misguided reasons, at the wrong time ... but if you stop doing it completely, you will eventually di
128.
by Ace17 8y ago
I suggest you have a look at OpenSSL.
129.
by Ace17 8y ago
https://github.com/thi-ng/tinyalloc/blob/master/tinyalloc.c#...
130.
by Ace17 8y ago
Probably not. However, such a limitation is rather easy to workaround. Which means now, buggy commits are going to look suspicous.
131.
by Ace17 8y ago
I agree ; however, the tricky part - I believe - is not computing the message string in case you're not going to print/record it.
132.
by Ace17 8y ago
Corresponding citation from John Lakos about why macros could be necessary: https://www.youtube.com/watch?v=K_fTl_hIEGY&t=3140
133.
by Ace17 8y ago
The preprocessor: Bjarne Stroustrup has been willing to get rid of it for a long time. C++20 modules are a step in this direction. However - as pointed out by John Lakos - you still need macros to build zero-cost logging facilities.
134.
by Ace17 8y ago
> But from the startup founder perspective, you can't let yourself be paralyzed by the fear that everything will go horribly wrong. Some middle ground here is definitely needed. Even for startups, things going "horribly wrong&q
135.
by Ace17 8y ago
> What could be some reasons behind him doing so? Giving his readers the ability to read the book without requiring them to install proprietary software.
136.
by Ace17 8y ago
> The fail-safe code that Toyota had put in place wasn’t enough to stop it. > “You have software watching the software,” Barr testified. > “If the software malfunctions and the same program or same app that is crashed > is su
137.
by Ace17 8y ago
This looks somewhat similar to good old modularity and decoupling. Does "optimize for deletion" differ in some way from that?
138.
by Ace17 8y ago
> I would argue that the condition that you provide sources to your users is something you owe the author. But perhaps I'm over-philosophical. No, I think you're right. But you only owe it to the author if you're a "d
139.
by Ace17 8y ago
Yeah, it's unreadable. Too bad, the article seemed interesting.
140.
by Ace17 8y ago
> Having realized that the world is not a programming problem, > AI obsessives want to make it into a programming problem, > by designing a God-like machine. We invented programming to solve problems from the real world. What do yo
141.
by Ace17 8y ago
Ever had this discussion with a coworker? Coworker: "I hadn't enough time to do it right" You: "Given enough time, how would you do it differently?" Coworker: "............" (crickets) IMHO it's not r
142.
by Ace17 8y ago
> Perhaps the biggest hurdle is that the code is not best read linearly. The reader must understand the order of evaluation, which follows very simple rules, in order to understand the code correctly. Could you please give some details a
143.
by Ace17 8y ago
> the only problem with exception-based handling is the lack of explicitness. [...]. Writing "exception safe" code is tricky and non-obvious. Does it still hold if you assume automatic resource (memory/locks/handles&#
144.
by Ace17 8y ago
Yeah. BTW it's also true for native apps running in user-mode.
145.
by Ace17 8y ago
> the only problem with exception-based handling is the lack of explicitness. It's too easy to call functions without being aware of the set of possible errors. That's the whole point of exceptions.
146.
The D Language Front-End Merged Into GCC 9(phoronix.com)
269 points by Ace17 8y ago|90 comments
147.
by Ace17 8y ago
> until most of them use different versions, so you will miss out on the advantage of dynamic linking anyway -- updating a library would only fix security holes in a subset of your programs. You might as well just statically link everyth
148.
by Ace17 8y ago
Doesn't generalized static linking makes fixing security holes a maintainer's nightmare? What about keeping libraries dynamic, but allowing different versions to co-exist? (basically, it boils down to considering different version
149.
by Ace17 8y ago
This is not so simple. What about "NullLogSink" and "StdoutLogSink", both being implementations of "ILogSink"? Classes are very well suited to statically formalize the communication points (aka "interfaces
150.
by Ace17 8y ago
RAII is a very powerful technique. However, it has actually very little to do with object-orientation. To my knowledge, the only other langages having it are D (multi-paradigm) and Rust (explicitly non-object oriented).

More ›