วีดีโอ

C++ is the best imo.

im starting to hate JB

The stories in games are about as important as the stories in p0rn flicks. I play games for the action, not the story.

Javascript variables are a guessing game. No data types or hints.

OpenGL may be a bit too legacy-ish nowadays, but we have had core and forward-compatible OpenGL contexts since 2008/2010, we also have debug OpenGL contexts now, and for those who want a faster API with less error checking, there's also a no errors context which only reports out of memory errors and the bunch.

If I was coding alone, I'd absolutely do anything I wanted whichever way I wanted. Working on a TEAM, however, I can see where constraining my own personal coding style to match what has been accepted and learned by EVERYONE, academically, would lead to better outcomes. It's like if everyone spoke a primary different language, but everyone also spoke some German, it's easier to try to speak German than figure out how to go between everyone's primary language. Is it optimal? No, but it's better than the alternative for a group of people with a common goal.

I'm a C++ dev and I love JetBrains Mono NL

Can someone say what is simp please ? I've heard about simping but ..

There's a well established firearm metaphor that inspired Rust in the first place. At least Rust makes it really difficult to blow my own leg off.

Now imagine a team of 10 developers, different nationalities, everyone writing code how he feels like it. It's just not going to work for a business, a lot of people compare software written in the 80s to modern software but those are exceptionally different things, can you hack a table compositor that hacks stocks number prices and finds the average price that does a single task alone, or in a team without regard to structure as long as it follows the instructions in order to produce the defined output? Yes, and it's the right thing to do, you're not going for something that is readable or extendable you're going for something concrete easy to do so you can move on. But then you compare it with a modern day system where now this very same average stock price calculator suddenly has to work cross platform, on the web and be able to communicate with millions of users in real time and at the same time that functionality is now broken down in several different layers, it's no longer that thing that runs on my computer. Patterns, concepts and ideologies exist for a reason, it's because it helps teams work together, if we follow the basic design pattern of let say mvvm across all of our user interfaces that builds on top of oop best practices i know that when i am looking at a view there is a corresponding viewmodel that contains everything necessary for the operation and data that belongs to that certain view. So if i need to fix something that is broken, or extend the screen with a new functionality it's the place where i would start my task, i will add my visual elements to the view then go back in the viewmodel and add calls to any external services that might provide data for my elements or update data based on my inputs. It will allow me to do wonderful things like separate teams, i can give the UI based work to less experienced developers, the business rules viewmodels based stuff to mid-senior developers ensuring that the person would not do weird stuff like forgot logging any security related concepts such as certificate validation when calling external apis ect ect and at the same time, i would have a really nice way to introduce transaction ids, which will help the guys working on the given apis to track bugs on their end as the client would be able to generate transaction ids and we can easily follow up logs in case we have an error in a certain api making both development and troubleshooting much easier in the long run. Having these models, allows offloading the work to different team members parts of different departments with different areas of experience, that are better suited for the task and at the end of the day it's not just oh someone decided that OOP is great, it really isn't but it's a concept that works, it's a structure easy to understand and it ensures that we follow a common pattern recognized by the majority of developers. Missing design patterns is what you end up when you look at someones react code, then you start pulling your head when you see a file that has 8000 lines of code, that define variables make network calls, push routes and update components as well as define nested components on the same screen because the guy went through few tutorials and somehow got a job at a sweatshop. Nothing against my follow colleges that write good react code, you're just the majority in bad practices because there isn't even a single way to define a project structure in react to start with so almost everyone follows his own thing with his own package structure. It's baffling that this is a discussion in 2024, i know Jonathan is a "legend", but such remarks shouldn't be part of any intelligent discussion past the early 2000s let alone in 2024, just because when you work alone for something that works on your computer for you hack it works, doesn't mean the same concept applies for modern software requirements

My philosophy with rust is that slow is smooth, and smooth is fast. Am I writing critical infrastructure, where this is valid? No. Does it satisfy my autism and make it fun whereas I'd otherwise tear my hair out? Absolutely.

I don't know what the did I just watch.

He's right, web development sucks, probably the most boring field of software development.

So does he hate it for any actual reasons or just cuz the name is weird? How's the performance of it?

What does he actually like ?

This comment aged well. Linus Torvalds recently supported removing a dozen of kernel contributors of Russian background precisely because of concerns similar to this video. There are people whose jobs are to ship vulnerabilities - just different forms of the Trojan horse that the ancient Greeks used.

This makes no sense. Does he expect me to download a binary to view his website? Should we go back to frames and blink tags? What are we even talking about here?

He definitely likes "linear algebra done right" if he's purchased it 3 times

What path. Wtf is he talking about.

New to C++ and every time I learn about a new fun thing I look up a video about Jon Blow trashing it. There's one every time without fail.

Janathan Blow using emacs. I am pleased.

Ok, lets just pass around 20 parameters to every function. It will do the job. Oh , you pass a struct pointer ? Well, thats an object.

"It's so embarrassing that I don't even know what to say" is an all-time great line.

I generally like his viewpoints but this didn't seem logical. The main advantage of those languages is that they abstract away many things such that it makes it easier to maintain a large project. Maybe there is some validity in his argument but those labguages are not popular for no reason. Abstraction is necessary. You either build it yourself in C or use Python/Javascript/C++ to do it for you.

wow don't be a bad programmer now this is a truly fascinating revelation that had my mind jonathan blown

another W for the shadow wizard functional programming gang

I'm a web developer. Found a way to achieve a 10x speed improvement on half of our API endpoints. Would have made the code 30% uglier. Had an argument with my senior, whether we should do it. Lost the argument. Jon is right. Case closed.

Unix, which Linux is a clone of, was developed by people with masters degrees under the same roof.

Boys say: "give me evidence", Men say: "I guarantee", "I have been around for a long time", "100%", "how is that not true" and "how do you think that's not a thing". I think it's called conspiracism, but how can I disagree with the best game developer -who has been around since the beginning of the universe- ? /s

My dude rolling a joint

OpenBSD

In this video: Jon Blow on flushing the toilet -- it is such a failure.

bro needs to use Apple Silicon Mac lmao

If the software industry consists of logical people or guides by some engineering/first principles the yes but it is not. There could be an objectively bad choice and people will still say "right tool for the job" and "everything has pros and cons" kind of nonsense

"pretty fast by modern standards" The government could not install a toilet in 120 days in 2024

Please, don't be a video cheering Musk, please

It runs on the Macintosh, so existing written Vulkan functionality can float on macOS.

The original purpose of computation was to reduce friction. You program a system so that you can solve a problem which was previous with high friction. Bank transfers or company document storage were already solved with physical technology but instead now we are able to do so frictionless. People saw how they were able to make these physical solution frictionless by creating software that they abstracted the idea, what if the purpose of software isn't to make originally physical systems faster, but instead how can we make the process of creating software frictionless. Many of tools we have developed in the past were motivated by solving these physical problems, and thus needed to provide the tools needed to make something frictionless. What has happened in recently years, say last 1.5 decades, is that many of the tools we had in the past are replaced by one which are "frictionless". The problem with that is that these new tools lack the ability to now solve the real physical problem, which was to make these orginialy physical systems frictionless. Basically we used the tools which enabled us to make frictionless systems and used to only the tools themselves and resulted in the loss of actually solving the problem.

Jonathan Blow also describes the plot to Battlestar Galactica 2004

Jonathan Blow describes SystemD

associating behavior with classes was the brilliant improvement that OOP brought to the programming world. All of the other stuff: polymorphism, class inheritance, GC... that's the stuff that broke things.

Object oriented programming doesnt mean "pre planning" or this "uml modeling" thing that people do. You'll never "pre plan" code thats any good, I'm not smart enough, you're not smart enough. You absolutely should just start writing code, ideally through TDD in my opinion, and this would conform to his idea here that you need to begin immediately solving problems. TDD just helps with ensuring you're solving tiny problems.

In my opinion, namespacing is the reason why someone want to write C++, instead of C. C doesn't need namespacing when every task is own process. But when ~everything is put to same process to avoid context switching, that is where namespacing is important. And naming of functions, or everything... is extremely important. I just name things as "foobar" or something until I really what name should be and not forgot to check those. PHP function naming is warning example what happens if developer is not careful.

There are lots of huge code bases that are managed just fine with javascript. Yeah, you migh not have control over the memory and low level stuff, but you may not need to. The goal of the programming language is to solve your problem. If you can then manage your code base ( which is more about architecture rather than coding language ) and the super high execution performance is not your top priority, why does it matter you what language is written in. Programming is about solving problems. Stop treating it like a religion

Inheritance and class structures are such a pain in the ass... I do think there can be a place for OOP and I've found it pretty useful in game design when you need ~20 different versions of the same enemy class but slightly different. However it's grossly overused I feel to the point it just ends up being a bigger problem to manage in the end then not using it at all. Most programs in C++ should be structured like C programs for as long as you can I think. OOP should only be pulled out when all else fails. Crazy watching tutorials on TH-cam for C++ game programing and the first thing they do is make ~20 different classes just to do basic things.

Sometimes you don’t know ahead of time that you’re introducing unnecessary complexity… and then it bites you

We be POKE 53280,1

I learned programming from C64 Basic and it was a fantastic learning experience!! And then I moved on to Python which was nice but it also has a stronger mindset or ideology than basic. That’s fine as well, but it does make the learning curve steeper

Man JB's takes are interesting, but I also feel they are very wrong in some areas... Like what he's saying here is basically everything every Rust developer has said about C++ forever. However the premise is fundamentally flawed in saying "Don't use C++, you don't know how to use it's advanced features!" Because he's basically implying I should just write these features myself in C instead, that way nobody but me understands them! There is a reason every major game engine is written in C++ or Rust and not C. Also why use C when GO exists? JB you have good insights, but frankly you're too stuck in your ways, this just isn't good advice.

👏👏👏