Late to reply, but I think this was thoughtful enough to warrant it.

I think that A is a way forward as a proving ground, but it has limited use. Having to include a standard runtime/library is no small impediment to building good websites/applications. A language designed around compiling to Javascript instead of WebAssembly can avoid this issue to a useful degree, and will have better DOM support.

That's just a stepping stone to D, which is browsers supporting a new language outright as a first-class alternative to JavaScript, or supporting a more capable runtime/standard library usable by whatever is compiled to wasm. And when that happens, maybe the DOM model can be improved upon, too.

That is not likely to happen without some new language that happens to meet the need of a some new use case of wide interest. It's not a tomorrow solution, but in time it can happen. I just hope that when it does, it doesn't bring problems with it.

Yes, the reasons behind a language being unnecessarily hard to learn do indeed validate complaints.

Javascript is a mess. Typescript helps. But it is still ultimately salvaging a mess.

Javascript didn't get to where it is by merit. It got there by existing momentum.

Brendan Eich had ten days. It was a miraculous work. But it was extended beyond its utility and the world is worse for it.

> The solution isn't to excoriate AT&T for their poor performance, but to move on to viable technology.

If AT&T was topping out at 25Mbps or more, this would be an issue of the limits of DSL. But 3Mbps in a densely populated area is certainly not that problem.

Eventually, though, yes, it will be time to move on from DSL. AT&T is the one that has not moved on to viable technology. Fiber is not outside the scope of AT&T. They can start with fiber to the curb, and move on to fiber to the home... both of which they already do elsewhere.

There are two times to transform the market with a converged laptop/tablet:

The first time when it was practically possible. Apple didn't even try. Microsoft brought out the Surface, and siphoned off creative users. Apple is still not hurting, but they lost a lot of influencers.

We're now at the second point, and Apple has the ability to do it right. With their improved ARM processors, a converged tablet/laptop can now be done without such large compromises. The time to strike is now--or at least a few months from now. Signs point to Apple at least preparing for the possibility, but if they miss the boat again then it will be a huge disappointment.

Intel didn't just make a strategic decision to not move past 14nm. They had problems moving to 10nm.

That they've been able to accomplish what they have on 14nm is no small feat.

There are certainly ways to criticize Intel for sitting on their laurels in some areas, and certainly they did something wrong if the 10nm process they were working on didn't work out (though it's easier to criticize than to succeed at hard problems). But being on 14nm isn't just because they didn't want to compete.

Fulton County is not run by Republicans.

Fulton County had some oddities with their vote results when using a system that made fraud particularly easy at certain points, and the recounts did not address any of the oddities.

Most of the court cases have not actually made any decisions about the claims made, because the blockers have been procedural.

Still, no fraud has been proven... it just looks suspicious and no actual investigation was made.

Fast food restaurants trying harder outside the US is not a condemnation of a nation.

The US is my favorite country in the world. But yeah, McDonald's is better everywhere else I've been. That doesn't mean America sucks. It means McDonald's sucks.

Blocking someone on Twitter doesn't prevent you from saying whatever you'd like on Twitter.

Not being able to participate in specific threads is not being silenced.

I have seen a bit of the world, and "the civilized world" is apparently in your view a few large cities.

I would have zero problem with showing the domain name in it's own space (maybe colored green for HTTPS and red for HTTP), with the path following it with gray text.

It's an easy solution that hides nothing.

That worked a bit better a few years ago.

Today, AMD is running cool and Intel is making space heaters--and will apparently continue to for a couple more years.

This is a completely separate question of whether the rates are abusive and should change. They are abusive and they should change.

But the FCC does not determine the law. The FCC sets regulations within the bounds of the law.

Sometimes the FCC doesn't have authority it should, and sometimes it has authority it shouldn't. But whether it's good or bad in any case doesn't determine what the law says the FCC can and can't do. The FCC is not a telecommunications dictator.

If the law says that this particular slice of telecommunications (which is not a general case of FCC's telecommunications charter) is the state's domain and the courts have upheld that, then the state law should be what regulates it.

People can't seem to grasp that they can sleep whenever they choose to, regardless of what the clock says.

If there's an argument for using that as a standard, make it.

But what we have is the choice between and an objective standard and a subjective standard according to the opinions of people who can't grasp that they can get up when they choose instead of when the number they're attached to on the clock comes around.