วีดีโอ

Thanks a lot, just what I was looking for to get started. For me, it wasn't auto-starting on reboot, so instead of using: > sudo systemctrl start docker ... I had to use: > sudo systemctrl enable docker

nice project wat the doodle! lets goo, lets make html element nodes and overload the dom, html bomb, can we do it?

Good response, echoed a lot of my own thoughts when reading the article! Regarding point 5 of the tl;dr (10:15) my understanding of the author's point is that he considers that people use C or Rust (or other systems languages) unnecessarily, in contexts where application languages (of which Go was offered as one example) would suffice. I'm not very persuaded by that either, however: 1) In my experience at least, most greenfield applications or servers these days are already not written in C to begin with. This is a part of the problem that has already essentially solved itself via market pressure, because people were unhappy with the productivity that C afforded them, and have already migrated to languages like Python, Go, or Javascript. There used to be a time when large desktop applications or tool suites were entirely written in C++, which in many cases was the only viable alternative at the time, but my perception is that this isn't really common anymore today. 2) It is not always a linear step up in safety/ergonomics along that chain. Go lacks protection against multithreading bugs, and infamously has had poor abstraction capabilities around things like error handling or generic data structure types (until recently). Python codebases with dynamic typing rapidly become hard to reason about once they grow past a certain size, causing productivity to nosedive and affecting correctness/reliability. There are many stories from developers praising Rust's features for data modeling and how they actually improved development velocity with it. etc. Memory safety bugs aren't the only bugs, and not even the only *security* bugs! Logic bugs can also affect security, and not as many languages seem to think it's important to give developers tools to adequately defend against these as well. 3) There are contexts where a language runtime might be prohibitive. Go tends to fare very well here, but deployment of Python apps to end-users tends to be challenging, and even if that's ok for servers or some kinds of desktop apps, I certainly wouldn't want to pay the startup cost of a JVM for each command in my shell scripts, for example! I think a disappointing trend with these kinds of articles I notice is that more "machine-oriented" programmers that think in C a lot seem to overestimate how comfortable the average developer is with an environment like that compared to a more abstracted or math/functional-like language. There's a learning curve, but I think their familiarity with that model tends to bias them towards assuming everyone also finds it intrinsically more intuitive to use, which I really don't think is the case. As with most things in these discussions it's hard to get actual conclusive evidence about any of these things though.

hey Doodle, if you haven't tried it, I'd go over the doodle outline in black pen and then try the 'Trace Bitmap' feature? have you tried that?

Everything is crap once the PMC and their MBA locusts infect it. See: David Graeber. Saved you 5 minutes.

Disagree with most things on the video. We need more focus on documentation rather than getting working software fast. Focusing on the later just leaves you with rushed unmaintainable crap that can only be understood by the underpaid, inexperienced junior that was too eager to prove he's an asset to the company by getting shit done fast. I do agree that non-technical managers can be an issue, but in my experience having nobody correctly translate a client's wishes to requirements to proper documentation is just a recipe for disaster later on. Clients change their minds, then nobody is certain this change wasn't what they originally stated (or worse), the manager decides they know what the client wants and what the client wants is not written anywhere other than a nebulous 5 words sentences per requirement. And I also agree on agile snakeoil salesmen being cancerous bullshit. I had to attend a course like that and it was worthless. Full of "exercises" that just wasted hours that could have been invested in other things. All because the company wants a scrum certification.

If you work at a company, chances are they're not doing agile or anything close to agile. It's also not a methodology, it's a mindset. As long as you adhere to the principles, you're doing agile. So, even you get a fail.

Tlrw; Agile is bad because companies aren't doing Agile. Not very insightful.

You messed up the sort. It must be `arr.sort( (a, b) => b.age - a.age )` or, even better: ` arr.sort( (a, b) => a.age > b.age ? -1 : a.age < b.age ? 1 : 0)`. I'm not sure what is happening in your example. Another thing. `sort` is a function with a side effect. It sorts the array in place (though, it returns a ref to the same array). You should use `arr.toSorted( ... )`. A good try, but you should prepare better for your videos. Anyway, I'll put you a thumb up for efforts.

the topic looked very interesting but i had to stop the video because it is unwatchable on mobile devices think about increasing your font size, especially if you only use 2/3 of the screen real estate in your videos

theres lot of alternatives to neofetch!

great to see the progress doodle, both in your content and the hyperfetch rust project 👏👏👏👏

lets goo doodle 🙌🙌

Qemu please

Sweet... I use Linux too... I like the simplicity.

Can you give a tutorial on how to install a virtual machine on Linux?

Thanks!

Burn out after 20 years of career! What a resilient man