This video talks about every single confusion I had with a university project to simulate cricket matches and doing math with them. So many objects needed to modify each other that the structure started looking like a maze rather than a hierarchy. And boy, did that cause problems.

Did I just hear an American English accented tuber say "sikth" for "sixth"? What in the flying butter monkey?! Who are your parents, I need to have a talk with them :P

Ooohhhh..... This explains what stack means. Lol. And what high level or low level means. Ohhhhhhh...... So the bugs are the inconsistency between the calls.... Ohhhh......

5 years ago i watched that original video on OOP being bad and it blew my mind , being a university student. Honestly that video was pivotal to my career and where I am now. This one just happened to pop in my feed. Thanks

Lots of strawmen arguments and yes-men on this.

so basically, more clickbait

Lots of BS -no real explanations

This is the best video for people that call them selves programmers.

I have plenty of arguments against OOP. Mainly this has to do with the convention of combining of data and processing in the same class, unnecessary limits of inheritance, or the need add work-arounds like dependency injection to make up for the limits of the OOP concepts. So I'm in no way advocating of OOP per se. This video however seems to be all about how bad abstractions are bad. Sure. Stop making bad abstractions. Alright, I get that that's easier said then done, but still. Stop. Making. Bad. Abstractions. Or at least fix them, when you realize they are bad. Also is there any viable alternative at this point? Functional Programming is great for math problems. But let's not kid ourselves; it has a steep learning curve, and a lot of limits that make it useless for actual real world problems. And procedural programming is just OOP but with less features. Again, I'm all for anti-OOP. I have been determined to try and invent something better for at least a decade. Give me some other option.

Interesting in why you picked this framework over something like sentence cards or something like that a la AJATT or other input-based methodologies.

people trolling around with "OOP is the standard today" but don't actually know what the REAL difference is between FP and OOP. you can do whatever you do in OOP in FP as well with namespaces, static functions etc... but at that point why not just use OOP? these are the kind of questions to ask yourself, if im trying to do something in a way just to avoid doing it in that way then why not just doing it in that way ?

This is fantastic. Great work as always

i thought you will come with next part of , WHY OOP SUCKS ?

This looks like a very efficient and simple framework for practicing reading/listening comprehension, I'll give it a try. Good work 👍

I tried using it on windows but it's not detecting any sources from the static folder. I downloaded the source and ran japanese.exe and I followed the instruction with an example folder in static(static/example) and test.mp4, test.ja.vtt and test.en.vtt in the example folder but the import page doesn't display any source. What might I be doing wrong? I'm using firefox if that matters

Thanks; This is the best OS intro. vid.

Have you heard of yomichan? It’s another browser extension that also allows you to see definitions of Japanese words when you hover over it. Original project is no longer maintained but a fork called yomitan seems to be keeping it updated. Also I would say to just watch what you’re most interested in. It may not the best for learning but it will keep you engaged and that’s arguably more important.

This is a video I need to watch on repeat.

Man what this man said clicked a bell for me. Once objects share state publicly or via methods encapsulation flies out the window. And this is a problem I have been having often. Where it is hard if not impossible to isolate a problem to a class. I must seek out the codepath that used the class instance. Many Win32 functions copy entire string when returning data to user. Such as when getting the Window caption. My God! This is functional programming and I didn't realize!

I am more than 500 days into learning a language (not Japanese) with Duolingo, so I have some experience of app based language learning. Quick reaction - one key benefit of BW's approach is the use of real world spoken examples (so anime TV, podcasts) rather than simplistic sentences. That might make it harder at first, but may produce a more real-world useful usable knowledge set. (Even if your day-to-day life does not consist of mirror-shaded razor girls). BW focused on comprehension. But for many purposes you may also need to translate into the foreign language, and of course speak it. Never going to be a substitute for in person conversation with native speakers.

You are back!🥳

nice work

The creation of the excerpts could probably automatized, like you drag in some anime episode with subtitles, it automatically extracts the text and then splits it into maybe one minute chunks, or like even 15 seconds if you are a total beginner. You already do automatic tokenization right?

Interesting.

he's back!

12:14 it is not a linear increase: at an angle of 45 degrees (halfway in between) the dot product is not 0.5. The change is not linear but sinusoidal, it's proportional to the cosine of the angle between the vectors.

Skill issue

"Who cares. It's effing garbage" ... LOL Thanks for making me laugh so hard 😂

You now what these examples need? Interfaces. And factories.

To the people that are commenting that this are just bad OOP examples. Yes, you are right, they are bad examples, but those people sell those examples again and again as the good examples on how to do OOP right. And this happens quit often with OOP. Not only this, but those people sometimes even show a bad procedural example and sell the OOP as the better version. Saying that OOP is in general bad is as wrong as saying that procedural is always bad. In the end a programmer must make it readable and understandable, but to me it often seems that people who at least did some procedural or functional programming instead of only ever learned OOP come to far better, shorter and more usable solutions as those OOP heroes.

and spring framework abstracted everything to hell

شكر Thanks it was helpful

I watch this video about once a year. For the longest time, I thought I just didn't "get it" with respect to OOP. As much as I tried, I just didn't see the point of it 95% of the time. Every textbook example I saw about OOP seemed to be much more obtuse than the equivalent regular functional programming with the promise was that the advantage would be clear with more complex real-life examples. Most of the time, that never happened for me. Thanks for making it "OK" to not follow this industry standard practice, which I believe is just making code harder to write and understand!

شكرا Thanks this was amazing

Thanks, I hate it. Super corporate sounding.

شكرا thanks it was very helpful ❤

3:57 This そう is the one used for quoting hearsay. The appearance version is tacked on to the infinitive like 並びそう

Little late to the party, but how are you practicing language production (to use a fancy term for it)? I'm also journeying to learn Japanese. Kanji recognition comes fairly easy after drilling for both reading and listening, but when I'm trying to remember a word: say a word, or write a word I often draw a blank. I struggle to remember the correct pronunciation or even the radicals in the kanji. I'm interested in what other fellow learners are doing.

41:25 "an anonymous function which doesn't see anything from its enclosing scope" is present in C++ in the form of a lambda with an empty capture clause, i.e. [](T arg1, U arg2) { /* You can only use arg1 and arg2 */ }.

I mean it’s probably the same thing as ISAM and sql, I think isam database are better the sql but sql rule the market 🤷🏼‍♂️

this "use" feature in 41:35 is somehow present in c++ in form of lambda functions, where you declare copy variables inside [ ] braces. It's not as simple as the example through.

There's some serious insight here, and I get that you're passionate about this, but maybe skip the "most important video" next time.

Just think about an int vector. Why would it be better to keep track of its size in an independent variable instead of asking the vector itself?

8 years since this masterpiece. I’ve progressed with simple procedural code to the point where I physically cringe reading others peoples OOP code labyrinths

all of the strong patterns and principles used in the industry are using OOP, for example SOLID, Design Patterns, Clean, Hexagonal architecutres and Domain Driven Design

The popularity of Java style OOP now seems obvious to me, and is caused by three main factors: 1. No or less memory management. 2. Autocomplete. Browsing for methods is a real thing, although it wasn't common in my generation of programmers. 3. SVO order - typical in western languages. Sadly, functional languages use VSO or VOS - which are very uncommon in modern language branches. But you are completely right that subject-object aren't usually well defined in programming, so the Japanese might think of Ruby as being OVS while English speakers consider it SVO.

ever since i started coding I resonated with the points made in paralysis analysis. granularizing large classes and jumping through a bunch of methods is very annoying. and the interplay between objects can be challenging.

This video is great. The topics discussed in this video(dogmatic usage/forcing of object-oriented patterns without good reasons for it) is one of the reasons I like the Lua language so much. It doesn't get in your way and lets you just do what you want. It's flexible enough to support object-oriented programming, but doesn't force you to use it.

Object oriented programming is an indefensible scam

Title should be "Do not use OOP on everything, even though that's the only thing you were taught at school."