3,467 karma · joined May 15, 2009
For ephemeral ports, it isn't clear what value there would be for a string identifier vs. the fixed-width integer.
I can imagine a lot of ways to interpret this but none really make sense in the context of your post.
What "equality principle" leads to a conclusion that a government employee doing X must be paid a fraction of what a private employee doing X is paid? I'm confused.
It may be a union-busting technique, but I'm not sure about "classic".
I mean how often has the economy had to recover from a multi-year work at home mandate due to a pandemic?
The massive switch to remote work and the pendulum swinging back towards more in-office work is a unique phenomena, not a recurring "classic" situation.
If you can't remove dispachable generation because you need it to back up the intermittent generation then you've successfully increased your cost of energy considerably because you have to build and maintain two systems. Take a look at Germany for example or I think maybe trends in Australia.
You get legislate away dispachable generation as much as you want but until someone solves the energy storage problem you are just creating more problems tha you solve (unreliable and very expensive energy grid).
I'm sure I'm not the only person to have thought about how cultural differences are sustained over time on the account of synchronization challenges due to bandwidth limitations between cultures (language, frequency, latency).
OK, I can see how the resale scenario is different from the consume/utilize scenario. Thanks for the clarification.
Wouldn't that mean that every company that used telephony, railroads, airlines, or shipping would have to be behave like a common carrier?
I'm not sure what the correct balance is but I don't think it makes sense to force common carrier status to propagate in the way you seem to be suggesting.
> This section does not prohibit any lawfully authorized investigative, protective, or intelligence activity of a law enforcement agency of the United States, a State, or a political subdivision of a State, or of an intelligence agency of the United States.
I'm not sure if this is the relevant code for this Qakbot incident, I'm just trying to clarify that the law generally accepts that law enforcement officials get special dispensation from the regular requirements of the law in order to carry out their function or to protect the public.
The devil is in the details but arguing that municipalities shouldn't compete with private businesses is not the same thing as arguing that private businesses shouldn't have other private competitors.
I have no doubt that telcos lobby heavily to restrict competition. Last mile infrastructure regulation is complicated but I'm more in favor of a level playing field (i.e. regulation) for access to poles/conduits/rights-of-way than having municipalities operate their own broadband architecture or even worse operate and then protect themselves from competition by other providers.
You seem to be saying that your cabin community was able to find a solution that would not be acceptable to a large telco. Why isn't that OK? Why should the large company be forced to do something they don't want to do if, by your example, other organizations are capable of servicing those communities?
To rephrase the question: What, if anything, prevents smaller organizations or non-profits or niche companies from servicing areas that large telcos will only do through regulatory mandates? Can the business/regulatory climate be improved to facilitate these smaller organizations? Are there existing regulations (for example access to poles or conduits) in some areas that block smaller organizations?
While this is true, I think it is helpful to communication to resist changes to language. This isn't the same thing as opposing change entirely, but language needs to have a certain stability and common understanding to maximize its usefulness.
That is not a feature flag, that is a customer configuration option. They are different things and should not be treated in the same way.
Sure, it is possible for a feature flag to behave like a configuration option but they have different lifecycles and different audiences and so should not be confused. Of course it is easy to say that but harder in practice to maintain those differences.
I once received an application for someone looking for a position as a railroad engineer. Unfortunately my job listing was for a Ruby on Rails engineer. :-)
Surprise laws should bother you on general principles.
Tax unpredictability, high taxes, or capping profitability is a great way to scare off businesses from operating in your jurisdiction.
The article reports the effort as a "surprise tax".
The notion that humans, as a species, will not adapt seems farfetched to me. Humans have perpetuated themselves in a wide variety of climates for thousands of years.
I don't say that to discredit concerns about environmental change, its impact on future populations, or its near term impact on existing individuals. All I'm saying is that arguments based on existential threats are not persuasive to me and they tend to be used to assert power over others than to mitigate risk or improve the lives of people on the earth today.
Having 53 byte payloads is something only a committee could love.
It is quite typical for managers to delegate projects/efforts/initiatives to a subordinate for the express purpose of giving them an opportunity to develop and demonstrate the skills they will need in a future position/promotion.
If I assigned a stretch opportunity to one of my direct reports and their response was that they needed a promotion before they would do that work, that would be strong evidence that they were not going to be progressing anytime soon.