myoon

Probably would still be an issue with contaminating the aluminum with carbon and possibly other impurities. You'd probably need some other process to purify the aluminum afterwards, which likely makes it too expensive.

I think you're missing the key point of statically typed languages, that the compiler catches errors for you. Generics are valuable because it allows users to write "generic" reusable functions that are still checked by the compiler. Of course dynamically-typed languages can do this easily, but that's not the point.

If this https://github.com/microsoft/fluentui-system-icons/issues/52 is addressed, then at least any developer can choose to set their own fill colors.

No, this is the fed fund rate, which is just for banks to borrow really short term (overnight usually) to each other. Most consumer loans are based on the prime rate, which has a few points added to the fund rate to cover the cost of borrowing.

The path provided is being able to load Angular 9 components into AngularJS components relatively seamlessly. This is helpful, but it's almost certainly a big leap to get your codebase compiling under angular-cli. If you manage it though, you can, in theory, do a bottom-up replacement of all your AngularJS components.

Another thing to think about though is how you're currently doing state management. Angular 9 is all about RxJS, and if you're currently managing state without it, your migration will be that much harder.

Probably a combination of wanting to work on games, and if you make it through the gauntlet you get exercise a lot of power and reap whatever "rewards" may come with that. Maybe it's a similar mindset to enduring working at a consulting/law/finance firm hoping to make partner, etc.

Two problems, first is this would either end all class-action lawsuits, or spawn way too many of them. If a lawyer is guaranteed an hourly rate to work any case, then why wouldn't they? Currently, there's a natural limit on class-actions based on the validity (chance of winning) of the case. Since most people can't pay for the hundreds (or thousands) of hours of work necessary, they're all on contingency. If contingency is no longer possible, then how would class-actions be regulated?

Second issue is that there is a huge variance in the skill of lawyers and that skill has huge impacts on the outcome of cases. It'd be just like fixing the pay of software engineers in terms of results.

If you go to the Razer subreddit, there's reasonable consensus that buying from the Microsoft Store, Best Buy, etc. is highly recommended for the extended warranty, which you will have a high chance of using if you regularly game on it.

This isn't comprehensive, but no one has really talked about Excel being unfairly leveraged to prevent the entry of competitors, gain an unfair advantage in unrelated markets, or exploit its consumers.

Now Google may not have done any of the above with search, but it's likely possible to argue that they have unfairly promoted their own products over others, or "unfairly" chose to not list certain websites.

It isn't perfect. The IO performance is currently poor and it doesn't play well with Windows Defender (wastes a lot of CPU). Also, since your IDE would live in Windows, you can sometimes have issues with Windows and Linux both interacting with the same files.

Not sure about land values specifically, but residential real estate in Japan generally doesn't appreciate much, if at all, outside the center of the most major cities. There are multiple factors I imagine, like shrinking population and the general aversion to buying used homes. Until fairly recently, homes weren't generally designed to last that long anyway. A lot of homes of the deceased are just abandoned due to the costs of demolition.

It's possible this could change somewhat going forward as newer homes have much better construction. This would still depend on the country figuring out how to grow the population though.

I think many were more concerned about .NET performance against tech in the same class, mainly the JVM, which previously blew .NET out of the water in the benchmarks for a number of years.

DSL frequency is usually between .25 and 1 MHz as that's what CAT1 was designed for, while LTE is usually sent over frequencies in the hundreds or low thousands of MHz. Shorter or higher quality runs of DSL lines can have slightly higher frequencies, but it's still not much.

Unfortunately, there are a few major downsides to sql.js:

1. Not API compatible with node-sqlite3, so you can't just drop it in and use it with knex or other wrappers.

2. Doesn't support in-place editing of a db. You have to load the entire DB into memory, modify it, and then save it back, making it unsuitable for any concurrent application.

I love the idea of the project though, and it would be awesome not to have to deal with compiling sqlite or using node-pregyp to build embedded chromium apps.

The WPF browser control is pretty weak. You don't have great control over which rendering engine it will use (default is to go to IE 7 mode!) except via writing a registry key to switch it. It provides almost no bridge between the JS and native code as well. I haven't used CefSharp, but I have used Awesomium, which provided pretty good JS-C# bindings, so I assume CefSharp has at least working JS-C# bindings.