cyberprunes

I would say that a big ball of crap qualifies as bad.

I used dart for a couple projects just around it's 1.0 release. I really liked it back then. They were working on some neat ideas. I remember futures and streams being really really interesting in 2013 or so. Originally Dart was competing directly with Typescript. It wasn't clear who would win at the time. Typescript focused on being a superset of JS and Dart made the mistake of trying to push its own VM into the browser which never really got traction and so transpiling to JS and depending on gwt was the only answer for dart on the web (I think) and the js output was pretty hairy. Dart web was dead. Go was already getting popular on the backend and so Dart had nowhere left to go until Flutter. Dart's fate is now Flutter's fate.

I would revise that to say "The Knowledge Graph View is mostly bullshit". That seems to be the core of the argument anyway.

It's not about "node flexing" and neither is it about letting the system do the work for you. You still have to do the work of turning information into understanding.

I agree that we lean on things that are often too complex for our given tasks (the industry encourages it) but I'm going to push back with a little Rust rant. I'd argue that RUST is actually represents a simplification not a complication. Perhaps GC was an over-complication. Perhaps app/system language separation was an over-complication. Perhaps the idea that memory/cpu limits don't matter because there is always more on the way because hardware keeps improving royally screwed us. Perhaps OOP is a disastrous over-complication. Perhaps energy costs and efficient resource management is actually a hell of a lot more important than we believed it was. Look at all the bloat we blindly accept in the name of productivity which in many cases is dubious. Rust may not be the be all end all of languages but it does shine a bright light on the brain rot that has consumed the software industry.

I like the interest in modernizing the terminal as an interface. There's still room for innovation and improvement. That's probably the big reason. Unfortunately this push is mired in app culture yak shaving bloatware bullshit (with a few exceptions). I'm surprised the market hasn't been flooded with Web3 DAPP terminal apps that will "revolutionize the terminal somehow, bro". Anyway, I love the enthusiasm but I'm not using a 100MB+ terminal app that requires a cloud account. I'll keep on BASHING like its 1989, thank you.

That's legendary stuff right there

Word

I would encourage you to at least consider that your issue is a bug or perhaps a wsl version issue rather than throw your hands up and point to a conclusion from years ago that windows is a pretty toy and just not up to the task.

I'm not much of a Windows fan but I do understand the usefulness and convenience of having a linux dev environment when forced to use windows for one reason or another.

Whenever a white person claims reverse racism or discrimination and then brings to light what that instance entailed I have yet to find that it comes close to what a black person experiences as racism. (Maybe you are different) It may feel unfair to you but you just aren't going to get far on the white people experience racism too argument. It's a loser except among other white people with hurt feelings.

I was inclined to agree until the choice to use the term "colored person". That's an obvious and well known racist trope with very recent historical ties to segregation. I'm not sure if it was a deliberate statement on political correctness but I really think it undermines your argument and makes it seem like a disingenuous crock of horse manure.

Disagree. Sure rust has a notable syntax tax (not what it used to be) but that's the easy part! It's the concepts and mindset that are the biggest hurdle in Rust. Going to C++ first won't help you there. If you already know it, great but Rust is a different language and you'll spend a lot time trying to transfer C++isms over until you realize writing effective Rust is not like writing effective C++ and you go through a process of unlearning. In my view, learning C++ for the purpose of learning Rust is massive waste of time.

That's great advice.

I want to agree with this because teaching IS a great learning tool but one needs to have some idea of what they are doing. Teaching helps to identify the problem areas we fool ourselves into believing we understand well.

Youtube is an amazing resource but it's also an ocean of incompetence and phony expertise by people doing exactly what you prescribe. Just be careful not to contribute to the ever expanding circle jerk of self congratulatory mediocrity. No one wants that.

Man, you just summed up my exact struggle as well.