Redundancy vs dependencies: which is worse?
I believe that there are just two intrinsic forces in programming: You want to minimize redundancy and, ideally, define every piece of knowledge once. You want to minimize dependencies – A should depend on B only if it absolutely must. I think that all other considerations are of the extrinsic real-world kind – domain modeling, usability, schedules, platforms, etc. I also think that I can show how
Things from Python I'd miss in Go
Let's assume Go has one killer feature – cheap concurrency – not present in any other language with similar serial performance (ruling out say Erlang). And let's agree that it gives Go its perfect niche – and we're only discussing uses of Go outside that niche from now on. So we won't come back to concurrency till the very end of the discussion. (Update – the "killer concurrency" assumption seems
C as an intermediate language
Here's a Forth program debugged in KDevelop – a graphical debugger without Forth support: Cool stuff, not? The syntax highlighting for Forth files – that's someone else's work that comes with the standard KDevelop installation. But the rest – being able to run Forth under KDevelop, place breakpoints, and look at program state – all that stuff is something we'll develop below. I'll show all the req
C++ Frequently Questioned Answers
C++ FQA Lite: Main page This is C++ FQA Lite. C++ is a general-purpose programming language, not necessarily suitable for your special purpose. FQA stands for "frequently questioned answers". This FQA is called "lite" because it questions the answers found in C++ FAQ Lite. Note: some parts of the FQA are not up to date with C++11/14/17. You can contribute to the FQA on GitHub. Metadata Purpose Def
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
