Companies that raise prices by doing that will be beaten by companies that don't very quickly. Alternatively, combined with the much weaker law enforcement, "illegal" (I'm not sure about the legality of cracking copy protections here) copies will flourish if it's close to being feasible, which it could be.
So there is a benefit in converting fixed upfront capital costs into rolling operational costs.
In most developed countries consumers can convert those upfront costs easily and cheaply through loans. In a country like India, loans are much more expensive.
Think of it like using cloud services instead of buying an upfront machine.
Would you if some random person, who for all you know could be an Uber/Lyft employee, and even if not, is someone who uses Uber/Lyft and therefore is likely happy with it, asks you a question about it?
You're telling me Apple doesn't have a conflict of interest policy?
That sounds strange.
So the Geniuses at the Genius bar can basically openly tell people that they can go to the other shop they work at across the door and they will do the repair at half the price? And Apple will have no policy against that?
Considering their main revenue sources will likely be decimated, it makes sense to focus resources on the primary browser engine, and allow the open source community to build out the experimental features, moving temporary resources there as needed.
The thing with Open Source is that even if Mozilla Corp goes under, all of us can continue building out Firefox like a regular open source project. Or the Linux foundation could pick it up, etc.
That's literally how Firefox was created in the first place, as an open source continuation of the Netscape browser.
Using Firefox will lead to improvements that will persist even beyond Mozilla Corp. In the meanwhile, Mozilla Corp can be looked at as an experiment to commercially and profitably develop Firefox, which, if it fails, will require us to switch to the non commercial models that are driving several other open source projects.
Hash maps also don't (usually) have external effects.
There arent many hash map methods that will actually modify the data.
Standard OOP, on the other hand, seems to encourage such behavior. So, for example, a Company object could contain a bunch of Department objects, each of which contained a bunch of Employee objects.
These people objects could also be referenced in areas outside of the company object.
If I called a company.giveFinanceDepartmentARaiseInDollars(10000) function on the Company object, it would have an unpredictable impact on the Department/Employee objects. It may also have cascading effects in other parts of the application that may not be clear.
On the other hand, if you represented this as a company hashmap, with the keys the department structs, you would have to do something like the following instead:
This contrived example shows some of the pros/cons. OOP allows us to hide a lot of behavior/changes, which may mean less repetitive code. OTOH, it hides a lot of behavior/changes.
Eventually data has to be bound to code. Otherwise you'd have apps where you either have functional code running and other apps that are displays of raw data.
The engineering question is what layer is it appropriate to do so. Under traditional OOP (your pre functional forward Java/C#/OOP C++), the answer was that code is almost always bound to data.
Haskell style functional programming binds code to data at the last moment possible.
The best answer is likely somewhere in the middle, depending on your application and usage. I find, for example, that UI controls work well with OOP, but most other stuff I tend to default to functional style programming.
I was fortunate in that I moved my team to Teams (I still find the name terrible) well before MS put a mandate out.
So our folks were comfortable once the MS EOL statement came out and the company started moving everyone over. Everyone else had quite a bit of a struggle for a week or so though.
On the plus side, I think there were very few complaints after a couple of weeks. Which probably had a lot more to do with how bad Skype for Business was (much worse than Lync) than how good Teams was (it was still fairly unpolished at the time...it's much better now...MS has been adding features and fixing issues rapidly).
If the reporter hasn't provided enough information to recreate the issue (it's obviously not a major deal breaking issue otherwise it would be obvious and easy to recreate) and they are internal to the company, tell them to provide more information before moving forward.
The author's approach is good for external bug reports, but they don't clarify that's indeed the case here.
I have to strongly appreciate the author for finding the root cause and tackling that instead of the symptom.
So often, especially in front end coding, you will see an exception being thrown because of a null value being passed in, and the "fix" checked in by the developer basically returns the default value if null is passed in, when they should be investigating and fixing why a null was passed into the function in the first place.
If your function has a contract that forbids nulls from You resolve the immediate bug, but this almost certainly leads to multiple bugs being created in the future (or worse, something that is quietly wrong, because 1 row in a 100 row table is missing and no one noticed) until the root issue is resolved.
Well, before this year there wasn't a global pandemic. That's really meaningless. This wouldnt be an issue if it had happened last year, or the year before, or the year before...1918.
The point is that any functional government would have accounted for the fact that there is a global pandemic, which if nothing else, might actually make it impossible for some students to even leave the US, before publishing this guidance.
Edit: Also, this is a deliberate undoing of a temporary allowance they had already made. From the first sentence of the linked document:
> Temporary procedural adaptations related to online courses permitted by the Student and Exchange Visitor Program (SEVP) during the height of the Coronavirus Disease (COVID-19)crisis will be modified for the fall 2020 semester.
Yeah, that's why the idea that H1Bs need to be restricted will help with US employment is remarkably stupid.
There are a few companies that abuse (abused?) the H1B program but that was always a small but visible percentage, but more importantly, actions taken under the Obama administration had drastically reduced the abuse.
The much greater percentage are employees who studied in the US, or worked with companies in India and then had them transfer to the US. Eliminating the H1B visa simply means that they will now do the same work from India or Canada instead, further reducing the number of jobs in the US.
People earning 80k in India, China, and heck even Europe, for that matter, almost certainly have a much higher standard of living than people earning that much in the US.
And you can find far more 80k level developers in individual cities in India than you would in a small mid level city in the US.
This is pretty much completely anecdotal, and not very useful, to be honest.
The informal stuff doesn't work well. I'm guessing they went to buy their furniture off the informal buses during off peak hours. So they didn't have to deal with the crowds the majority of people have to deal with during regular rush hours, where you will find people hanging off the buses, and others struggling to get in. Sure, the bus may come every 5 minutes, but you may have to wait a few buses to get in.
Further, these are private buses. In the US you can get a cab exactly where you want that takes you exactly where you want. You could also "rideshare". The reason you dont have buses to do that in the US is because people can afford single occupancy cabs. What the person is really complaining about is the fact that the US is richer and things are more expensive.
A cab is a proper analogy to the private transport that is being compared to. And the real complaint is that earning dollars and then paying in dollars in the US is more expensive than earning dollars and then paying in local currency in the 3rd world.
Companies that raise prices by doing that will be beaten by companies that don't very quickly. Alternatively, combined with the much weaker law enforcement, "illegal" (I'm not sure about the legality of cracking copy protections here) copies will flourish if it's close to being feasible, which it could be.