Comments by "Anony Mousse" (@anon_y_mousse) on "ForrestKnight" channel.

To really make it effective, have it give a warning shot, then wait say 5 seconds and if you don't focus, shoot again. Maybe two in rapid succession then wait some more and keep upping the ante until either you focus and it resets or you refuse and it unloads. Also, can you imagine having to write that code from scratch? The toolkits we have now are kind of amazing.
20
It'd be cool to see a game where they use a neural net to train the AI in the game to act more realistically as well as to have them go about their lives even if no one is watching, but within a set of unbreakable rules to maintain the integrity of the game itself. It would be pretty cool to attach LLM's to each one and have full conversations with NPC's that are properly answer and response. I don't know if you're old enough to have experienced one, but I'd love to make a really simple one and incorporate it into a MUD.
12
Truthfully, I'd say that SO created a generation of developers that can't program, "AI" is just making it worse. Back when I got started it didn't even exist and was well over a decade away. We used to refer to the shit developers before then as point and click developers. Of course, I'd still love to know how so many people could have been brainwashed into thinking that this current technology is "AI" and that the term they use instead for what we used to mean is somehow now AGI. Can you imagine if Spielberg had named his movie AGI? It would've been weird.
10
@clarity211 You clearly need to read up on it because that's not at all what happened. One thing people should understand about Stallman, is that he aims for precision in his language that nearly no one else aims for. Unfortunately, it leads to a lot of misunderstandings because people these days are incapable of actually listening and correctly interpreting others words. Instead they like to ascribe meaning that isn't there and dismiss meaning that is. I'm sure someone will be along to blame American schools, but schools are awful all over the world and on top of that, roughly half of the people alive are just stupid because the global average isn't very high when it comes to intelligence.
8
@davecanam6971 I think I'm the only person in the comments that got that reference. It was better than the Matrix and a whole lot more thought provoking.
5
@ventus.pd89 20 years ago, SO didn't exist. Using a search engine to find an answer was nearly universally a big fat NO, and that's irrespective of the search engine used, of which there were more than two back then. If you wanted to know how to do something, you generally had to read a big fat book. So I'd argue that it was definitely harder back then and that's why developers were better then.
5
It's true, I've been using vim for over 20 years, still can't exit. Though, if grep isn't enough for your searching needs, locate and find can fill in the gaps. You just have to know regular expressions and understand the quirks of the tools.
5
I talk to myself too, and it sometimes freaks people out, but it really does help when trying to work something out. I don't know that I'd call it a memory technique, because I still forget things days later, but while I'm actively working on a project it can help a lot.
3
I would suggest that you learn C instead. The compiler doesn't hold your hand, but if you really need that at this point in your career, there are plenty of tools to use. Personally, the more I learn of Rust, the more I hate it. Things like unbox and clone are as much anti-patterns as move is in C++. The more clear syntax for handling an error return where you're maybe receiving something is to merely test it with: if ( obj ) do_something here(); else do_something_else(); Or if a quick exit on failure would make more sense, and it often does, then: if ( !obj ) { print_error(); return error_code; }; Of course, if you still feel the need to have OO design patterns with language support for them, C++ is still the better choice over Rust, even if r- and l- value references have muddied things up.
3
@AlainPilon Yeah, and some teachers made things deliberately harder to weed people out. I see that as a good thing.
2
If you're looking for a subject to study that'll help you far into the future then go with graph theory.
2
I'm not sure why tuples and records need a # to denote them. If a language is going to require a special syntax for something of that nature, I'd prefer if the symbol used were one that didn't require a shift key. Of course, for records and tuples you shouldn't need special characters in that way. Just doing {} and [] should suffice. Although, I wouldn't be opposed to \[] as a syntax because none of the three require shift.
2
@TobySug Yeah, we know why you use Rust, but not everyone is a deficient programmer. I like using C because it fits my "do everything myself" style, but it seems not everyone can write error-free code like me.
2
And if you're trying to understand a new language I've found that the most fun way is to read the specification or standards document, if one exists, and implement a compiler for it. It's also fun to write a BF interpreter if you want the easier route for trying to understand a new language. If you don't know it already, it's an esoteric language which I have to censor here, BrainF***.
2
Parkinson's law is why I procrastinate and do everything at the last minute. I get the same work done in a mere fraction of the time. :P
2
Good general tips, but also you should add study on your own for a few hours too. Sometimes trying to do things for yourself first can help with understanding, where a second person may have a different way of looking at things that conflicts with your own, and sometimes that can help too. So, do both.
2
@loo_9 I'd thought about that some, and I was thinking that a similar technique to memory management could be applied by using a bit map to handle address offsets. Then each element could be directly-ish referenced with just one extra indirection. This would necessitate that each object is either a multiple of the byte size for the given platform or at the very least padded to it, but that's true even for regular scalar storage anyway.
1
I don't know if I have some kind of problem, but I can't seem to focus in that way. I wish I could, but I may be broken. I tend to have a video playing on one desktop that I can listen to while I've got documentation open across 2 or 3 desktops then all the files I need in my brain context will be open, 4 terminals to a desktop across 2 or 3 desktops. I'm constantly switching back and forth, reading, listening, watching, while also writing. My thoughts kind of swirl, like when I clicked like I was thinking I wish I was three likes earlier so I could've been 666, but I guess 669 is nice too.
1
Although you could build an OS with it. It would just require that you build your own compiler so you can disable the GC at the kernel level. Of course, if you go that far, I'd change it so that Allman style bracing wasn't an error. I can't stand K&R style bracing.
1
Your pronunciation could use a little work, but otherwise a rather good video on the history of Vim.
1
Same here, although I do have 12 desktops to put running programs on.
1
At least for now, the people that write the stories are safe, because even with a great prompt it'll still need editing for clarity and consistency. Once the NN-based FakeEye gets good enough to not need editing in that manner, it'll just be a matter of generating a great prompt. Eventually those too will be replaced. At some point humans might craft a sincerely artificial intelligence, and if they do, that'll be the end of humanity. Why the end you might ask. Partly because humans won't be able to do anything for themselves by that point in time. They will be but mindless children being bottle fed by machines. Machines which will see them as a burden and cast them off. The only way to avoid such a future is to stop the falsely named "progress" and never attempt it again. But, we all know that won't happen. If you can read the text at the bottom of an eye chart then you don't need glasses.
1
One minor correction for that meme you showed, the Rust maintainers don't consider memory leaks to be unsafe, and Rust won't prevent most of them from occurring anyway. Although, that's the least of your worries because there's still a lifetime leakage bug in the compiler. For those criticizing the safety of C and/or C++, there are tools for checking the correctness of your programs for both C and C++, and these programs are free and open source, and they're older, more battle tested and in general just better than the Rust compiler. That said, since no one bothers to learn what was written before, I'll tell you that you can use GC in plain ol' C too. If you really want to be lazy with memory management, look into Hans Boehm's GC and rejoice at how easy it is to setup and use. I can't say if it's better than Go's or Java's GC because I've never actually used it for more than a talking point to show that it's possible in C, and has been since at least the 90's, but if you really need GC, you can have it even in C. Finally, as I've been learning Rust, being a student of as many languages as I can be (but not a literal student mind you), I see that it's basically just the same as C++, only with a shittier syntax. If you write correct code in C++, then Rust's borrow checker will only sometimes annoy you. There are a lot of instances where correct code gets flagged by it, but this is why you should just use C++ instead. If you write your code in an idiomatic way in C++, then you'll never have safety issues with your code. If you write code in C the way I do, then you'll never have safety issues with your code either, but not everyone is capable of writing like I do. It requires a different mindset which most people these days seem incapable of acquiring. TL;DR: Ha ha ha! You'll never read this. YouTube will probably filter it anyway.
1
I don't really get why anyone would start learning Fortran in this day and age. If you already know it, fine, but why start when there are plenty of libraries for C++ and Python that can do everything that Fortran could do and then some. Truthfully, I don't know why anyone bothers with Python other than being too lazy to learn C++, because all of the same libraries are available between the two, but if you're learning one, why the other? On top of that, if you're learning C++ and you intend on doing well with it, you'll be able to write faster code with ease using it and ignoring Python.
1
@me0101001000 When you say best choice, what criteria are you using to quantify that?
1
@my_online_logs I think he was pretty clear in what he said and he obviously meant it when he said lifetimes. C++ already had everything else, and for decades.
1
What happened with your shirt? Baby spit up on it? Also, love the hair.
1
@ducksauce0074 I used a Raspberry Pi as my only computer for 5 years and it didn't slow me down. Of course, I also use vim as my "IDE" and primarily write C and occasionally C++ and a few other languages of that type. So that might make a difference if someone is just starting out.
1
While my main language is C, and that's certainly not going anywhere, I've been keeping up my skills in about 10 other languages. As I've been writing compilers and other such programs for the majority of the past 25 years, I see things from a different perspective than other developers. The way I see it is that C++ and Rust are basically the same language with all of the same solutions, except that Rust chose defaults that directly oppose C++'s chosen defaults, and it chose a syntax which is less consistent and to my mind uglier, and they chose to prevent certain types of solutions based on them merely seeming hinky. So while C++ by default isn't necessarily considered safe, the programmer can write their code correctly and even take extra steps to ensure that their code is safer for others to extend their work. However, tooling has existed for decades now which enables programmers to be sloppy and check their work the way `rustc` does, and even add on extra checks that `rustc` doesn't do. Also, the 70% figure is an unwitting lie on Microsoft's part because they're expressing the effect, not the cause. The cause of at least 95% of all bugs, in any user facing software anyway, is that of a failure to check user input. Inadequate and/or incomplete checks are still a failure to check user input.
1
@ClimateChangeDoesntBargain They've already got working prototypes. Apparently you can test one of them out with CE.
1
No matter what they add to Java, they can't take away enough to make me stop hating it. However, C# is an even worse language. Requiring an unsafe keyword is one of the dumbest moves that any programming language can make, and there are at least three that have made that stupid decision and I hate them more for it. If you want a good language that's not C, or possibly C++, then I'd suggest Pascal. Download a copy of Lazarus and Free Pascal and have a lot of fun programming. If you don't care about efficiency at all and you just want to have fun, then find a DOS emulator and use QBasic. Otherwise, if you want to do good work, learn both C and C++, and make no mistake, they are very separate languages. Read their ISO standards and you'll be a better programmer for it.
1
The one point I disagree with is about the definition of an array. Same type for each slot and contiguous memory storage, yes, but not statically sized. And there's a lot more complexity to hash tables if you care to make a more complete description there. You have different hashing algorithms, balancing schemes, and even storage methods. For instance, in one implementation, I made the storage backing for a hash table as a balanced tree and each node was also part of an interlaced series of trees that were the chains. It used up a lot more memory than either a tree or a hash table alone, but it was an interesting experiment in maintaining sorted order while yielding slightly faster searches.
1
@jcm2606 Yeah, it doesn't matter whether it's from the heap or stack, all allocations in a computer are dynamic while at runtime. Yes, even a stack allocated array can be resized in place, with a few caveats.
1
Great! Now you can auto-generate the flow charts that management wants which never get read by the developers nor used to guide development.
1
@glebzenkov396 So you say, yet every example I see shows off using match and its convoluted garbage syntax to demonstrate handling errors. I don't even like that syntax for handling enums, but when you've only got two possibilities it's worse. I won't argue for inheritance, but I personally prefer the way that C++ does all the rest over Rust. It has a cleaner syntax that's far more regular. Honestly, I didn't think I could hate a syntax more than C++'s until Rust came about.
1
@RustIsWinning Cleaner in that it's a more regular syntax that's easier to parse for a machine, if not read for a human.
1
I'm pretty sure that was the meme because that was definitely a squirrel. I think you might have ADHD. My dad does drafting work, so I'm looking at your layout and thinking, "that's weird". I can't say I like your sheathing, but at least it's not cardboard, which I've seen on some newer houses. I would like to know what you're going to do for the exterior if you haven't already gotten that done yet, and I'd like to know what kind of insulation you're going to use. IIRC you live in a colder climate, right? So will you be spray foaming and using rock wool?
1
I think that Java was ahead of its time with the idea of compiling to a generic bytecode and running in a VM, but the implementation was still done wrong. The language itself is far too verbose, it's basically a less utile C++, and truthfully, computers at the time weren't capable of running it adequately. Now it's perfectly fine, but GC languages are in general a bad thing. I'd love to see someone come up with a non-GC language that compiles to a generic bytecode and has a "VM" that generates a native binary on the first-run. Sort of like C#, but not a garbage clone of Java that's worse than what it cloned. Languages with "unsafe" keywords are beyond stupid. Programming is unsafe, and if you don't know what you're doing, you probably shouldn't be programming. I expect you'll disagree with this, but you have to admit that there are far too many programmers that really should be in a different field these days. Far too many people have gotten into programming because they saw people making a lot of money and they wanted in on it, but they have no desire to be good at it.
1
You should probably post a link to the paper in the description so that those who haven't already done this can follow along. Although, I am curious as to how a program written in Python could have a segmentation fault. If it's really down to WSL, then all the more reason I'm glad I don't use Windows. As for how I use my screen real estate, I either have four terminal windows open on a given desktop or two that are side by side and full height. I use vim for my code editing needs so aside from having four windows open at times, I may have two or three tabs in each window. However, I only have one monitor and every desktop is virtual, but since I have 12 function keys I don't have a problem navigating since I've got shortcuts setup with KDE for every desktop. Only questions I really have are, do you know any C and would you consider doing videos using it?
1