rewmie

53 ms·

571.
by rewmie 3y ago
> I feel like the new generation of devs got used to working with these abstractions and by some measures they seem highly competent, yet it feels like they're missing some critical knowledge; like they don't understand what&#x
572.
by rewmie 3y ago
> For one of those companies, I was literally just a part-time contractor. Once it's set up properly, it should be easy for regular admins to operate, and devs can just follow the templates for configuring a service. It's not r
573.
by rewmie 3y ago
> C++ has been gradually back-porting Rust features, I would hardly say that move semantics, or reusing temporary objects instead of deep copying them, is something invented by Rust. Also, move semantics were introduced in C++ with C++11
574.
by rewmie 3y ago
> But we don't ever "patch the OS." Our cloud provider does that for us. This is absolutely not true. Unless your cloud services are limited to function-as-a-service and serverless/containerized applications,you are i
575.
by rewmie 3y ago
> I don't see why students can't go to another state to get their education. As a non-american, I am baffled by this way of thinking. Higher education is supposed to be a way to ensure that a state is self-sufficient in terms o
576.
by rewmie 3y ago
I have a Beelink SEi8. That little guy kicks serious ass, and cost me around $300. It's slightly larger than a Raspberry Pi 4, and supports up to 32GB of RAM. I see people talking about the Mac Mini, but it can't hold a candle to
577.
by rewmie 3y ago
> I've seen M1 Mac Minis for sale under $200. Are you sure they weren't scams?
578.
by rewmie 3y ago
> (...) and to be honest I never completely understood the need for specialized time series databases. The need for specialized time series databases is explained by the basis of any software development process: reuse ready-made high-le
579.
by rewmie 3y ago
> Bigger cmake builds are doing dependency resolution, find_package(foo) #... target_link_libraries(myapp foo::Static) > configuration tests, I don't know what you mean by configuration tests. I don't think I ever added any
580.
by rewmie 3y ago
> or any number of other end-user-configuration complicated systems as such If you think that cmake is complicated, when in reality all it does is set targets using a declarative stye, then programming might not be for you.
581.
by rewmie 3y ago
> ...a Makefile and vim (or emacs, or even nano, I'm not going to judge your kink) are fine. If they are not fine, then C is probably not the right language for the project. Sorry buddy, you might believe Makefiles are fine only if
582.
by rewmie 3y ago
It would be very interesting if there was an application that generates Roost HSM code.from State Chart XML, similar to how Qt handles it's state machine implementation. https://www.w3.org/TR/scxml/
583.
by rewmie 3y ago
> Its important to note the article was published on April 1st. Haters don't waste time trying to understand what is before them. They just see a superficial opportunity to unleash hate and just go for it, logic be damned.
584.
by rewmie 3y ago
> This kind of post is why I do not understand C++ programmers whatsoever. It's basically a demonstration of the absurd amount of time C++ takes away from you by being the moldy pile of shit that it is. What? Exactly what led you to
585.
by rewmie 3y ago
> You might be confusing "monastery" with "church." Many religions besides the catholicism have monasteries, and exploit the same social loophole. Countless Buddhist monasteries also operate as a spa hotel of sorts.
586.
by rewmie 3y ago
What leads you to believe that protocol class + concrete implementations + factory can replace pimpls? I'm going to make it simple for you: take a Qt widget. You define its widget layout with Qt a designer, save a UI form file, and get
587.
by rewmie 3y ago
> pimpl went out of style maybe a decade ago This is a meaningless statement. As others in this discussion already stated repeatedly, pimpl is a very basic and fundamental C++ idiom that is pervasive in all application, and some framewor
588.
by rewmie 3y ago
> There isn't a good reason why private methods should be exposed in the header. This makes refactoring the class implementations much more of a pain in the butt than plain structs + global functions. Irrelevant. Private member func
589.
by rewmie 3y ago
> if you are using classical polymorphism, you can get essentially the effect of PImpl (...) No, not really. That's only an option for the rare cases where you control the whole class and all it's members, and you can break any
590.
by rewmie 3y ago
> Exactly this. Pimpl idiom is just a bandaid and typically goes against the main benefits of the language. No, not really. The pimpl idiom is a basic technique that is employed to "improve the software development lifecycle",
591.
by rewmie 3y ago
> If you don't care about heap allocations then why are you using C++ :) Because more often than not it is a made-up problem that at best is classified as premature optimization. Take, for example, Qt and how it uses it's UI fo
592.
by rewmie 3y ago
> I'll be glad if I never have to see PIMPL ever again. It makes tracking down the actual implementation of some functionality so much harder than it has to be. Not really. There are two main flavours of pimpls: one where the impl c
593.
by rewmie 3y ago
> Cement in an uncontrolled environment is not going to work as a capacitor, even if it works in a controlled environment. Some water will get in. Concrete always has water. It's part of it's composition. What exactly led you t
594.
by rewmie 3y ago
Bad header organization is perhaps the gravest yet unspoken cardinal sin of both C and C++ development. I lost count of the number of times that I had to deal with cyclic dependencies accidentally introduced by someone when they started to
595.
by rewmie 3y ago
> strikes me as something of a language flaw that without pimpl any addition/removal/ modification of private member functions, or even renaming of private member variables triggers full recompilation of every source file that
596.
by rewmie 3y ago
> Heap fragmentation is another For the rare cases where potential pimpl users care about heap allocations, there's a pimpl variant called fast pimpl with replaces the heap allocation with a opaque member variable that holds memory
597.
by rewmie 3y ago
I agree, in particular by the way unity builds can break code that relies on internal linkage to avoid conflicts between symbols. But it's nevertheless a technique that's supported by cmake and can be enabled by flipping a flag.
598.
by rewmie 3y ago
I feel you're just adding noise to an otherwise interesting discussion. If all you have to add is handwave over "Pimpl has so many other drawbacks" and to reply "google them" when asked to substantiate your baseless
599.
by rewmie 3y ago
Which ones?
600.
by rewmie 3y ago
CMake supports unity builds right out of the box. https://cmake.org/cmake/help/latest/prop_tgt/UNITY_BUILD.htm... And support for ccache is not an option to some build systems. For instance, Visual Studi

More ›