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".

Turing is the easiest because he's the only one that makes any sense. You have to get incredibly philosophical to have Hopper or Lovelace on the list as they very obviously did not invented the computer.

I mean, it seems like you are suggesting 3 incremental non-backwards compatible changes. I'm not sure how that's better. Nobody is going to sign on to the first two, so you end up with the exact same situation we have now, but took a more complex approach to get there.

Gboard doesn't have in app purchases, the other one does. The rules are different because the apps are different.

I'm confused as to what you think is mail fraud? Amazon is just fulfillment in these cases. It's clearly marked in the same place on every page, and as such, avoidable. It's purely a profit motive for Amazon, but I don't see how it's mail fraud.

The savings implies they saved $2B over AWS. I can't read the article since I don't have a BI account, but unless they saved $2B over AWS (rather than $2B over their previous infrastructure) it's definitely misleading.

Higher density is inevitable in mega-cities. Geographic boundaries are just a apart of reality. I agree that transportation is key to this expansion, but the Palo Alto's and Seattle's of the US only have way way to go and that's up.

First to market in hardware, especially 30+ years ago wasn't a minor advantage it was an enormous advantage.

And I'm not suggesting Kodak should have just went for digital in 1975, as that wasn't cost effective, or practical. But they should have, arguably, understood it was the future and at least pretended that it was a possible revenue stream. Instead they actively avoided it, and doubled-down on the "we're a chemical company" for decades. Then they went bankrupt.

How much of that $1300/month goes to dental and medical insurance? Because with no family to support, I don't see how you aren't paying close to half that in insurance.

Not who you asked, but it's almost guaranteed to be lower. It's extremely rare to be both remote and get paid at the prevailing salary of the company. That only works for companies that generally don't allow remote, as they don't have COL-adjusted salaries to worry about.

As an Amazonian that works remote, I have the same payscale as everyone else in Seattle.

I agree, generally, but that's ignoring geographic boundaries which are huge for cities like Seattle and San Francisco. It's not the main issue (regulation and zoning are) but it's still a big piece of it.

I'm not fond of the slippery slope argument, particularly when it comes from NIMBY's that bought their houses when markets were at a low because nobody wanted to live in these cities.

Bay area residents, Seattle residents, etc need to get over themselves and accept reality for what it is. They aren't protecting anything but their own sense of self-worth and the "theory" that bad things will happen if a 3 story apartment complex comes into the neighborhood.

The reality is, most of them want their property values insanely high, for when they are ready to sell and move to cheaper cities.

1. I assumed it was implied. Why else bring it up?

2. If there was a means to sue Amazon for hosting databases, Oracle would have already done it a LONG time ago with MySQL. The burden is on you to prove your claim.

3. You are free to talk as much as you want, just expect push back when you aren't right, a lot. ;)

Why?

To add to that: It was a Kodak engineer that effectively invented the self-contained digital camera. Kodak would have been unanimous with digital photography had they recognized what they had. Unfortunately, their leadership was in charge of a chemical company, and as such, they failed miserably to capitalize.

Note: Amazon employee, but opinions are mine.

Amazon did not replace Oracle with MySQL. You seems to talk a lot given your knowledge of how Amazon operates internally and how licensing works is... blatantly false.

All of those DB's that could "pursue" a lawsuit are built on open source licenses which Amazon is not violating.

But the most important point here: The idea that you have to write a database to be happy to be off Oracle is insane. Amazon moved to an alternative that doesn't have a deep license designed to financially screw their clients as much as possible. That's a win.