Видео

Dont be Fanboys , listen to what he says instead of gleefully saying it's a python dev complaining. He makes a point

2:11 i dont think its bad tbh, i dont even code in C++, i just read the keywords and saw a foreach that returns 2 to every element, so it must be a list with the size of the list passed, then it has accumulate, that i suppose sums the elements up, and then we sort it

“I am a pyhon developer…..”. Shut up.

Sounds like a really bad skill issue.

OOP is good for experiments and prototyping or smaller projects, because they do not get so complex. ANything else, it's unneeded unless it's needed. THe big mistake I hear people make is that they reach for OOP IMMEDIATELY before they even know if it will help them or not. That's like already starting optimizing before you even understand what needs to be otpimized. I think the issue is that people really believe they DO need it, which makes it tricky to not start with 10 layers of inheritance. Same applies to FP, however, I gotta say, I do find myself using FP A LOT MORE than OOP. Command pattern and strategy pattern are my most used OOP design patterns.

I csn see you have used C++ in your life as much as the duration of your video.

segfault says exactly where the error occurs, you just can't read...

functional is good for modeling a more abstract problem (closer to actual math) while oop is better at modeling already clearer and closer to reality systems (talking objects)

1. auto has its place, like with reducing pleonasm or trailing type deductions, not obfuscating intent 2. the STL is fine - what you're describing is C++20 mixed with fold expression; it's interesting to see the potential of these functions, but just because you can doesn't mean you should 3. dependencies, learn cmake fetchcontent 4. segfaults, learn to debug with gdb and read core files 5. smart pointers is not the same as raw heap allocation - it is a definite improvement

for segfaults just use a debugger and backtrace

Not preference. FP does not work on its own merits. OOP ois battle proofed. .

Stopped watching at exactly 0:02

Nah, its enormous but its not weird or bad. Its just a gigantic language. Also the solution they arrived at for metaprogramming is clunky. But thats true for almost all non lisp programming languages. Metaprogramming is just fundamentally weird and stupid (yes im looking at you rust) when you are not dealing with s expressions. Outside of that, its a perfectly usable and valid language. You dont have to use all the features all the time, lol. And yes, it does take a lifetime to master. But so does any worthwile semipowerful language out there.

The problem with C and C++ and Java is: they never deprecate anything. Nothing is ever removed, because there's too many people using ossified code bases who want to keep their old bad behaviour rather than having to convert a million lines of code to better practices. And so we end up with three different `malloc`s, fifteen new templates, and keywords like `auto` being misused to just hope the compiler will figure it out. Until these languages actually start deprecating old bad practices, they're always going to end up with a mess of old and new, bad and good, side by side and indistinguishable.

interesting, but why people insist in the idea of oop being about "modeling the real world"? i mean, you can use "real world" as models on any paradigm. a better definition would be that oop have behaviour and state coupled while state is implicit here in gereral, on the other hand fp have behaviour and state decoupled, immutable and explicit

sounds like this guy isn't great at c++

Best video I've seen in the topic. Thanks.

keep cpp as cpp and keep interpreted stuff for interpreted languages

As a C++ developer for about 8 years, i dont think this is a fair review... You should not blame the language for bad code. The modern features are there to make it easier, but is not something you have to use. So again dont blame the language, when its really just a skill issue for most people disliking c++

skill issue

how do you animate these videos?

the idea for refactoring "Perfectly readable" code to this amalgamation is usually perfomance thats just a bad case here because there wont be a big impact here, but once just by changing a function i've managed to get it 5x faster

C++11 and I call it a day

So FPOOP is better than FP? I don't think so... Also, abstraction doesn't have anything to do with encapsulation. If anything, it has more to do with polymorphism. It's not about a hidden implementation. It's about defining an interface without the need to provide an implementation. E.g. a library may not even provide an implementation to an abstract interface, class, or method and still compiles fine, whereas the implementations can be provided by the users of that library (and of course they happen to also know the implementation then). Basically, any client of a method/function/procedure should not need to know its implementation details if it's well written and has a proper interface/signature. That concern is orthogonal to abstraction.

Functional program feels slow as is due to data copy , it adds so much time to process that other get it done quickly, the most expensive taks from cpu side is moving data and not computing data. It seems aceptable tradeoff but you know deep down as project grows large the experience of ui feels laggy more and more which could be just avoidable if it wasn't copied data and shared instead .

Just turn ur car params init to slots and u are functional, or you can do some funky, you could functions which take car as a module and throw it in there, if u have many you could partialize. For the car example, if i were doing functional, i would combine it with modular ``` import car mycar = Car(100, "honda") car.maintenance_check(mycar) ``` For car module ``` from __future__ import annotations from typing imort NamedTuple from enum import Enum, auto clads Make(Enum): Honda:Manufacturer=auto() Toyota:Manufactuter=auto() class Manufacturer(NamedTuple): miles_for_service:int=100 ... class Honda(Manufacturer): ... class Car(NamedTuple): make:Manufacturer def maintenance_check(car:Car) -> bool: if car.Miles < Manufactucturer[car.Make].miles: return False else: return True ```

You seem like someone who doesn't really have much experience with C++. Not sure why you would make a video about it like you do.

im just trying to figure out how to remove a file i committed in a commit thats 7 commits back without changing any of the last 6 commits. i cant push bc that file is too large to push to github, i never meant to add it but i cant remove it no matter what i try.

Video is too short

C++ was one of my first languages so I kind of just accepted this is what coding software is like. Now I look at it and think it's pretty crazy. I still like it though. You do feel more pro coding C++ than other languages.

on linux package management for C/C++ programs is easy since you can install libraries through the systems package manager itll put all the shared objects in /usr/lib and all the headers in /usr/include automatically

as a software developer (C primary) dealing with C++ gives me pure pain. I have no idea such ugly language could be made. Using C++ in embedded software development should be considered a crime.

I agree that C++ has become weirder and weirder, I never use auto. I prefer to use classic syntax every time, I mostly develop for small micro-controllers and IOT and prefer to explicitly tell what I need it to do, usually the code is more efficient and faster than using mambo jumbo optimized and modern syntax and I need to understand what I have done after some time as well 😅

What a dumb video

0:21 wtf man I immediately grab my phone

same with python. i like python2 because of the less keyboard typing needed. for example the python2: print 'hallo' this in python3 needs this aditionaly round brackets: print('hallo'), this is much more typing work. two times press shift and search the round brackets key. why did they make this so complicated in python3? i go back to python2 because of this.

i want to add, I hate cout with a passion. printf already allows you to read the sentence in its entirety but with cout there's just << wrapped by <<. it's so messy and long.

Uh.... C/C++ has an entire system underneath it to manage packages; there's RPM, pacman, zypper, apt or whatever debian/ubuntu does...

Honestly, I hate tons of those bloody "std::"'s all over your code in modern C++. It's an actual torture when you're reading the code and complete waste of time when writing one

The condensed version is just functional programming. As a python developer you should love this. Also when running into a segfault you can use the core file to debug with gdb. Really useful

At 0:08, you have a syntax error. bool greater_than = [](int a, int b) { return a > b; }; You are assigning a lambda to a bool. You probably meant to write auto greater_than = [](int a, int b) { return a > b; };, potentially with a trailing returntype auto greater_than = [](int a, int b)-> bool { return a > b; }; One could even write static constexpr auto greater_than = [](int a, int b) { return a > b; }; because the Lambda doesn't capture anything. Or, bool greater_than = [](int a, int b) { return a > b; }(5, 10);

Love the visuals you used on the video !

I write and compile all of my code myself. It is the easiest and only way to do real development. If you are using someone else's code, 99% of the time they themselves couldn't compile and link their code without depending on a bullshit build system.

2:38 he burned c++ there. My ONLY gripe with c++ is the difficulty with installing libraries.

skill issue

modern language is what made me go from go to d and then to c++.

What theme are you using for the terminal?

The biggest problem with c++ is that devs think they need to use its special functions and features that it provides when simple c-style code 95% percent of the time is the best option.

Idk... kinda just sounds like a Python dev ranting about something they don't really understand fully.

3:14 Python user scared by ld.😅