jhall1468

I don't know if "from scratch" is really a fair statement. React accepts HTML in the render function, so the only thing you'd need to do is modify the variables to match JSX's variable syntax, which is exactly what you'd have to do with Vue.

I think it's all pretty much the same deal. You might argue Vue's template syntax is closer to HTML than JSX is, but that doesn't really feel like the major issue when slowly refactoring a large application.

I think you misunderstood the point you were replying to. The idea is that you can’t really have a discussion about what it enables or how it’s used unless you already understand the technical details. And that shows as a lot of the comments/blog posts about this topic are using underlying technical assumptions that are entirely incorrect.

That's absolutely not the same thing lol. What Amazon did is unethical. What you are describing is illegal.

Just because it's easy to fork in the UI, doesn't mean it's easy to get people to switch. Some people are actually concerned about the community as a whole, rather than their own projects.

And when maintainers respond to a significant amount of work involved in a PR for a bug with a note that they aren't interested because it's "boring" then they can be critiqued for being a jerk, because they decided to be a jerk.

If the maintainer had said, "Hey, I don't have the time to review/test/verify this PR so I'm closing it for now," the backlash probably wouldn't have been quite so severe.

You can't tax revenue when the business is losing money. No country in the world does that for a reason.

Literally everything you mentioned isn't a loophole, it's tax fraud. Tax loopholes are what they do within a single jurisdiction to avoid taxes. What you're suggesting is transferring money from one jurisdiction to another, which can't be done tax-free.

If you're discussing design and scaling at code review, you have a serious, SERIOUS, problem. That's what design docs are for.

Google shouldn't be restricted to a subset of the available technology because a niche browser isn't updating to available technology. Yes, a side-effect of this is that the blind community using Lynx can't use Google. While unfortunate, it's also a tiny, tiny, TINY community.

If you want to be upset, be upset with Lynx for falling behind. Or don't be upset and switch to JAWS, BRLTTY, Orca, etc. But the idea that anyone is supposed to support every possible browser is just silly.

That was the point of this entire thread. That MS doesn't care about Linux Desktop, so it's no longer a threat. The browser is the new threat, so being buddies with Linux is fine.

There's no secret plan here. Priorities have changed since 2002...

> So what are they going to do when they encounter a problem on windows? Pretty sure MS hasn't yet figured out how to directly install a Window manual into their userss brains, and the thousands of unanswered windows troubleshooting questions online can attest to that.

They call an 800 number to get help or send it back.

> your own technical ignorance and laziness?

That, right there, was exactly what the person was responding to. This attitude of "piss off and learn" is incredibly prevalent in the Linux community, which is exactly why it is (and will remain, for the foreseeable future) irrelevant on the desktop.

You can easily work 40 at tons of Amazon teams. AWS and parts of retail have the "crack the whip" culture, but it's not as bad as people think it is.

Walmart generates $500B in revenue compared to Amazon's $230B. While you aren't wrong that Walmart is doing well, comparing net profit between companies when one is 2x the size of the other is dishonest. It's especially dishonest when guidance from Amazon was a net decrease as they invested into 1 day shipping.

You can choose to not use Select, and just use standard KDP. This is an exclusivity agreement. You don't get to release your ebook elsewhere in exchange for higher royalties.

I'm quite familiar with them. But the colloquial term "computer" isn't the same as the historical term, and that's the point here. We aren't talking about the job, or a design that wasn't implemented, or a mechanical computer because nobody means that when they say "computer".