HackerTrans
TopNewTrendsCommentsPastAskShowJobs

yagni_dev

no profile record

comments

yagni_dev
·há 3 anos·discuss
It's because borrow checker is very restrictive. Indices are a sanity escape!
yagni_dev
·há 3 anos·discuss
You have no idea what tooling means in this context!
yagni_dev
·há 3 anos·discuss
the only astonishing thing is how pathetic rustafarians are. Whenever someone writes something positive about a c++ feature the squad is working extra time to diminish the article/opinion. You are trying so hard, lol.... "constexptr if" is brilliant, simplifies a lot template code.
yagni_dev
·há 3 anos·discuss
"You only need to hire “software” DevOps, rather than people who neatly lay your cables, journey to DC to replace disks, etc, etc, etc."

Lol, what year you think we are? 1998? There are colo facilities around the world, you have 'remote hands' to take care everything related to hardware. You just need ansible/xyz to deploy you software, thats all it takes
yagni_dev
·há 3 anos·discuss
Customer is king indeed but why they expect/want to use latest boost if their infra is old? Use the latest version your infra supports, simple!
yagni_dev
·há 3 anos·discuss
the fact we might have got sick of your evangelism and lies hasn't crossed your mind I guess

>It’s basically a compiler enforced set of C++ best practices

Its not, its a whole different programming paradigm where the compiler dictates how you write your software. You dont let your creative facilities to drive you or whats best for your domain - you just obey the language rules...
yagni_dev
·há 3 anos·discuss
Segfaults happen, you run valgrind/asan/tsan etc. As long as the codebase is not horrendous its easy to fix. Third party packages complicate things, have to choose/use wisely/appropriately
yagni_dev
·há 3 anos·discuss
>But as more and more engineers joined us, some shortcomings of C++ came to bite us: unreadable coding style, memory leak, segmentation fault, and more.

- Seasoned devs but they never heard of clang tidy/format - Memory leaks on a new db codebase where each component should have clear ownership of data or pass to the next pipeline/stage - you dont even need smart poirters here, just a half decent design. - I am not even going to mention sanitizers, probably rocket science for them