dan00

> IMO none of these things point to a AI being a bubble (over-hyped, demand does not match the stated value). It mostly points to the opposite, there is massive demand for AI and every layer of the supply chain is struggling to keep up with that demand.

Yes, the demand is there for the currently unsustainable price. Lets see what happens when the dumping of money into AI stops and the companies are forced to increase prices a lot.

Humans just have the cognitive ability to be violent on a larger scale. Otherwise I also don‘t really see much of a difference to animals.

As a vim, linux, shell guy, I still love my mapping of Caps Lock pressed to CTRL und Caps Lock released to ESC.

Being able to reach CTRL and ESC with the little finger while keeping your hands on the home row keys is great.

I think I read somewhere, that your preferred hand is better at staying in rhythm.

It‘s exactly the kind of words that venture capital wants to here.

Looking at code, it‘s easier to spot the missing check for an error code, than a not catched exceptions.

Also error codes are part of the signature of a function, which exceptions aren‘t.

> Often when someone wants to talk about a situation involving difficult feelings, they're actually trying to process those feelings: to understand where the feelings are coming from, to be validated, and to be able to take a broader perspective.

Right, talking about feelings is a way of regulating yourself.

Conflicts with my wife are a lot easier if I'm able to empathize with her emotional distress, acknowledging it, instead of jumping directly into logical problem solving. If I'm only looking logically at the issue, I can't really understand the issue she is having.

I like the view of the therapist Terry Real, that during conflicts you can either be right or stay connected. That doesn't mean that you hide your views, but that you also emotionally acknowledge the view of your partner. It's surprising how effectively this takes out the fire in conflicts.

> The only country 1st world country not to have really obese people is Japan (~5% obese ~20% overweight). (~35% obsese ~70% overweight US) and I'd wager a large part of that is the fact that kids cook for themselves in school so they learn early what a reasonable meal is.

There might also be a genetic factor, why japanese are less obese or overweight, because the difference for diabetes patients between US and japan is a lot smaller.

That's absolutely useless and that's great!

> The problem here (again, i think) lies in the fact that we don't often see the grander value of our everyday works and yearn to do SOMETHING grander, more impactful, but we don't know which, or how, and in time it will torment us each time we do our normal work.

I think it's a kind of yearning that can't be satisfied in the outside world. It's an inside problem and can only be solved there.

The dryer could tell the garage door to open, to reduce humidity.

Well, I'm only saying locale dependent file formats!

You really shouldn't be limited by only one language: https://github.com/charyan/unirust

It's the few highlights in the cacophony called life, that makes life worth living.

I‘m using cgdb, which is a minimal ncurses wrapper around gdb. It‘s a lot better than the TUI of gdb.

I think the problem with "big" language ideas is, that as long as they match exactly your needs, they're great, but if they're slightly off, they can be a pain in the ass.

I'm wondering if languages could provide some kind of meta information, hooks or extension points, which could be used to implement big ideas on top. These big ideas could then be reused and modified depending on the needs of the project.

It was always so draining going for lunch with work colleagues, that couldn't stop talking about work and tried to eat as fast as possible.

Like in life itself, if you‘re trying to control your programming job too much, you will be just miserable and fuel your anxiety. The complexity and unpredictability of the future can‘t be completely controlled. IMHO the only solution is to believe in yourself, that whatever is thrown at you, you will find a way to cope with it. Otherwise you‘re only worrying the whole time what the future might bring.

The deeper your questions go, the less likely you will find answers for them. If you insist to find an answer, can't continue living without finding it, you're going to have a quite miserable life.

The mind is an incredible tool, but if you point it against yourself it can give you the worst suffering possible.

In way this shows what meditation has become in the western world, a tool to become more productive, to become a even more effective, harder worker.

We don‘t get how our culture is making us sick, how we try harder and harder to get to the point of happiness and satisfaction, and never realize that this path doesn‘t work.

The wages in east germany are still quite a bit lower compared to west germany.

I think the naming of the ‘else’ branch in the loop could be more telling, like using the name ‘finally’ or ‘finish’.

I would interpret it differently. A man getting that easily bored by just one project, might as easily get bored by just one wife.

Yes, the breast cancer screening already has quite questionable results.

You might try an other diet that‘s more filling and creates less cravings. So less carbs and more protein and fat. I don‘t think that willpower really works in this regard long term. It only creates frustrations.

You have to start somewhere and if you can switch just one software, which you can later also use on linux, it seems like the perfect way to go.

Switching is always painful and will result in some troubles. So keeping it at a minimum is a good idea.

> I love Rust precisely because of this. You can leverage the compiler to drive your development and design. If it's hard, then it's probably wrong!

Yes, I had the same experience writing code in Rust and Haskell. If the design works nicely with the language, then also the design is better, more modular, simpler dependencies and easier to understand and extend.

> No big plan and then engineering the small pieces to build it. I've mostly followed the small pieces that drew me at the time. I'm aware that this approach could just as likely lead you to wasting your life on whimsy and end up with nothing, but I have to say I'm surprised with how well all the parts fit together for a pleasing whole.

In a way you’ve to be lucky that your interests are valued by the time and culture you’re living in, because you can’t control them. That might be the only difference of wasting your time or making it.

> Watch your compile times though

And your error messages. ;)

> I would add that, after stack, tooling is not a problem anymore. It's not as good and polished as rust's cargo but it's ahead several other languages.

In a way Cabal 3 is even ahead of cargo, by being able of sharing build libraries between different projects and still having a sandbox like build for each project.

> There too many different ways of doing things (eg. strings, records), compiler errors need improvement, prelude has unsafe functions (eg. head), exceptions handling is not something I want in a pure language, ghc extensions change the language so much that using some extensions almost feel like having to learn another language.

For such a self called safe language, some things are almost comedy like, like getting exceptions for uninitialised record fields or unhandled alternatives in case expressions.

But Haskell still has a place in my heart and I‘m still following its development. But for my side projects Rust has replaced it, by being at some things even safer, but foremost safe at the places it‘s most important for me and also quite a bit more pragmatic. For me Rust combines the best parts of Haskell and C++.