jiriknesl

Now, if so many jobs will be done by AI and robots, why would countries accept any immigrants, except for temporary fixing of consequences of unsustainable fertility rates?

Back in the day, I bought an office software and I owned it. Now, I rent it and over years, it costs me 5* more.

Back in the day, computer games were paid once. Or if you had a pack. Now, it is a series of $1-$2 small sales for thing here and there.

And I could go on. It is tiring. I think payment fatigue is very much a rational thing.

This sounds a lot like... when you move into a property, and you don't maintain it like your own, less than 2 years, things start to break.

My wife or I clean all bathrooms with strong cleaner, every week. I suppose, the author did not. And it isn't landlord's job to clean rooms.

I don't think it is true.

There are massive communities around tools far more simple than Ableton was even a decade ago, like SP404, Akai MPCs, Elektron Digitakt.

Many musicians treat any item as an instrument, not as a plaform. There are probably dozens of videos on youtube, where musicians explain, why they use more limited tools instead of Ableton.

To make a successful music tool (that includes DAW), you have to own a powerful workflow, that some group of musicians love or need. Extensibility is fine, but not the only way to succeed.

There are now people making music on pocket trackers that have ± same amount of features as modplug Tracker I used in the end of 90s.

The thing is, when you make a music with a guitar, you don't want your guitar to be 'built around composable scripted modules'. You want to play an instrument, and the UX should enable it, and generally get out of the way.

Most of the attacks on Rust, I have seen, have nothing in common what people are implementing Rust.

It has a lot in common with the fact Rust is very low level language, a direct C++ competitor, and many people use it for apps that could be easily implemented in much higher languages and run fast enough.

A driver or kernel extension in Rust? No problem. A todolist SaaS startup with no users? It's better to use Rails, Django, or Laravel for that.

Oh yes, absolutely. For hundreds of thousands of years, every elderly person had something like 8 children, 40 grandchildren and was busy with them.

Now, people fill this time with TV, because if they have kids, they live 5000 km away.

"The average person gets no benefit from this" this is a very bad take.

In Europe, innovation in the end help everyone. Better healthcare starts with the rich, and ends distributed to everyone. The same is true for everything else.

I think you oversimplify things a bit.

Are those names erased during compilation? It has a massive impact.

If you have indirect calls, how are those resolved? That matters a lot.

What is even the language, after the code is compiled/interpreted. Does it disappear like in many languages? Do you have some parts available, but not all (like in PHP)? Or do you have full runtime at hand and you can mold it like in Smalltalk? There are languages with no runtime, languages with some runtime, and languages with full image in place. Each has massively different pros and cons.

When you say Haskell and Smalltalk are name focused, you are technically right, but developer experience is extremely different.

I don't want to be overly negative, but it seems to me that author considers just different flavours of C.

There is a massive difference between Clojure, Prolog, and Forth.

The whole:

    type name = value—type-focused
    name: type = value—name-focused
    var name type = value—qualifier-focused

Is so much deep into details of how syntax might look like.

If you are choosing between Kotlin and Go, it is for the platform, not the syntax. If you decide between Haskell, Idris, Scheme, you do it with the syntax in mind.

I guess, these things are long somewhere in the mind, before people execute.

People change countries, partners, careers not because of one book. This is usually the last drop. They were long-term unhappy, yearning for something else.

And as this guy wrote, he was sick, he was burned out. I suppose, he wasn't able to limit his screen time, it was all or nothing. Sometimes, those big changes work better than incremental steps. 20 years ago, I went from a pack of cigarettes a day to zero. If I went to 19, then 18, then 17, I might still smoke to this day.

As always, it takes into account only a subset of what constitutes wealth.

The state owns national parks, army equipment, buildings... Also, the state owns an impact on regulated companies, subsidies, etc.

Just the US army receives funding about $1 trillion a year. It must own equipment, weapons, and buildings in a value of many trillions.

Every single citizen has a share in all of what the state owns and controls. The state also partially controls the wealth of billionaires.

So I suppose, that the top 0.001% holds as much value as... the bottom 5%?

Oh yes, this is 100% accurate.

Very often, when designing ERP, or other system, people think: "This is easy, I just this XYZ I am done." Then, you find that there are many corner use-cases. XYZ can be split to phases, you might need to add approvals, logging, data integrations... and what was a simple task, becomes 10 tasks.

In the first year of CompSci uni, our teacher told us a thing I remember: Every system is 90% finished 90% of time. He was right.

Even browse-wrap is legally binding, if visible enough (and it is visible just under the confirmation button on that massive Cookie Acceptance modal dialog when you come to YouTube).