marcos100

Mozilla removed a lot of power-user features and customization from Firefox claiming that their telemetry showed that few users used them. That's the reality now, nobody wants to develop and maintain things for the 1%.

Wouldn't they be liable for not helping law enforcement?

Exaclty. Play Store takes a cut from what it is selling, so they should be more strict what can be sold, not lock the whole platform.

And can you give a number on the "vocal minority"? Because companies usually sell what customers want and if the majority of the phones on the market is big, then that's what people want.

No economies of scale. Niche things will always be more expensive.

I want my self-driving car to be a better driver than any human. Sure we can drive without LIDAR, but just look up the amount of accidents caused by humans.

Just search for crash tests of modern vs older cars to see which one is safer.

Because it works really well

We all should think about optimization and performance all the time and make a conscious decision of doing or not doing it given a time constraint and what level of performance we want.

People write bad-performing code not because it's easier, it's because they don't know how to do it better or don't care.

Repeating things like "premature optimization is the root of all evil" and "it's cheaper to get a bigger machine than dev time" are bad because people stop caring about it and stop doing it and, if we don't do it, it's always going to be a hard and time-consuming task.

Do you share a part of you charge with the people that contributed? If not, what you're doing is the same as what others did when they took your work and profited from it.

You've all agreed what can and can't be done with your code based on the license you used.

If you want to make money with software, it's proprietary or dual-licensed (A)GPL with CLA. Anything else you'll bait and switch on people.

I believe the future will be to feed all your docs into a LLM for people to query.

As a backend dev, I love the technology. The problem is that you have to choose between a not-so-scalable solution (Server, signalR) or a minimum 2mb initial payload (WASM) that can easily go to 5mb.

Interested on how many concurrent users you have for Server to be a problem. Can you elaborate more on your performance issues?

Exactly. At least you have to show that you know what you're doing and it's deliberate. Depending on the seniority, I expect some kind of justification in the comments, like "it's O(nˆ2), but since the input will be very small, it's ok".

In real life people do a lot of O(nˆ2) code without realizing, and usually it's just some unnecessary loop inside another loop. I want to know that you care about some things.

Rewriting also costs less. Be it a typo or significant parts of a code. This allows you to try more things.

Because "we don't have the budget".

Exactly! Gramma and my luddite uncle are the most vulnerable to whatever bad actors want to do.

Agree, but for me, maybe because I'm so used to not having them that, when I see it, it grabs too much attention. It doesn't feels right.

Here you have selection bias. If you're a US company and you have to bring someone from outside the US, you'll probably bring the better ones and, as someone already said, if they are fluent in English, they are probably at the top.

Come work for a Brazilian company to see the that we have mediocre people everywhere.

Unless you really want it, it's usually better to skip v1 of anything, Apple or not.

Didn't WhatsApp had like 50 employees in total when they were sold to Facebook?

Crazy parents don't read books.

I can't see a case where an UUID PK is better than an INT (or BIGINT). Why would you do that?

Whenever you interview at another company you're evaluating what is your worth in the market, instead of just guessing. It's always good, even if you don't intend to take the offer.

If you show it to your boss, it means you intend to leave if he does not match it or offer some other perks. It's not forcing anything, it's negotiating.

By Modern Razor you mean Blazor components?

Why would it be worrying? Lack of jobs outside cryptocurrency companies? Language features focused on crypto?

Seems like .net shops uses DDD+CQRS+ES by default. Don't ask me why.

Hey author. This looks like a very approachable book given the subject.

Still on chapter 2, but really enjoying it. Instant buy for me.

Thanks for your effort.

So, just to clarify before people think I'm an OOP advocate and it's perfect, I don't, but I think it has it's place.

> There are definite degrees to this. Agree. The question is, does OOP leads to more buggy code? Maybe yes, so we ban OOP? Because that's the sentiment I get whenever someone is against it. In your example, is it ok allocating a new object every time? If you can't afford to do it, what do you do?

> Why do you believe that's the reason why? I think in terms of proportions. For example, if you have 80% of all code written is OOP, chances that you'll find a bad OOP is greater than finding bad code in any other paradigm.

What if people learn programming using FP or DOP? There would be less buggy code? I don't know, but I think in the end, OOP would become the popular choice because, in my opinion, it fits very well the way we think about our world and we would end having this same conversation.

What isn't a footgun in the terms that you declared?

I believe people dislike OOP because the vast majority of code is written using OOP. If everything were written using data oriented programming or whatever, people would have the same reaction as they have regarding OOP.

Tokio as in the rust Tokio runtime? You think that, because of tokio, rust became more bloated? Why?

I know rust, but I haven't used async apart from their tutorial, so I'm really curious about what are your thoughts about it.