throwaway12iii

That is a bunch of bullshit and you know it. AWS have made a tiny contribution to Linux.

An Open Source advocacy group with cloud providers on their board, and cloud providers who pay them hundreds of thousands per year. Their mission is to be evangelists for their definition of Open Source. The one that benefits cloud providers.

Of course a lobby group like this should be transparent. But I don't expect a group like that with closed mailing lists to actually be Open.

For the amount they make off community work, they contribute a tiny amount.

Right near the top of their list (in your link) they brag about contributing to Linux. Let's see how well their brag stacks up? Looking at the contribution reports on Linux, are AWS in the top 10?

AWS are not even on the list. https://twitter.com/ibrahimatlinux/status/768631239683158016...

How is a cluster more difficult for users in 2019? Most devs I know never even set up Redis. It just works through Docker/Ansible/cloud.

Have you benchmarked cluster VS locks and threads approach?

Lots of other ads have used the facebook logo and not been taken down.

It's pretty funny when people are manipulated so easily by facebook PR.

Both systems are visas. Fact.

Rust is bad at managing DOM memory in Firefox.

From the rust Oxidization page (hip name):

- "Crossing the C++/Rust boundary can be difficult."

- "For components that are relatively standalone, with small and simple APIs."

- "This minimizes the C++/Rust boundary layer issues."

Not only does Rust not have a good JavaScript integration story, it doesn't have a good C++ integration story.

Most of Firefox is still (8 years later) not written in Rust.

Chrome with C++ has a waaaaay better safety record than Firefox. Guess what? The C++ in Chrome tries to ensure memory safety for JS.

The C++ Chrome tooling does a better job of memory safety as a whole system than Firefox.

Which developers of Free and Open Source projects do you sponsor?

Tibet.

The USA has millions of african americans in jail working for free. More than in slavery times.

Both the USA and China are Nazi like entities in some ways.

Apple makes more than $10 billion per year on advertising just from one deal with Google alone. Microsoft has $7 billion advertising revenue.

The crowd goes mild.

Samsung supplies Apple too.

The biggest selling electric car is from Japan. The Nissan leaf.

Yes, you used the weasel word "reputable" - but what better reputation is there than having the most sales? Nissan from Japan sells the most electric cars.

Apart from sales, the Nissan Leaf scores 7-8/10 and 4/5 from the critics. Which is around the same as the Tesla model 3.

If the critics think they are ok, and they sell the most of all electric cars... then they can be considered reputable.

By abused you probably meant abused without payment to Google, or abused by people external to Google. People who pay or are Google can continue their abuse.

In 2012 neither a column store or spinning up a cluster was magic or state of the art.

Redshift delivered on sales and marketing.

Amazon made their fortune on the backs of open source contributors many times, and this is just another one of those times.

You critique them for __NOT__ using well tested libraries, and then critique them __FOR__ using well tested libraries.

It's very common in the C/C++ world. The main reason is that you can easily use it in other projects.

Until one of the C/C++ package managers gets good and wins, this is the nicest alternative.

Note that people don't necessarily develop the libraries in one big file or don't have dependencies. Many newer libraries use a single C file as a distribution format.

The other nice thing about it is that if the code is small it can be more easily debugged and audited by humans. If it pulls in hundreds of thousands of lines of code, that can be a problem. Also, small code is a requirement on some projects because of speed or memory limitations.

Yeah. Avoiding slow things like classes, threads and adding time.sleep(10) is the trick.

Yeah. However you have the option to not pause if it is important. You can control where the memory management happens. You can either keep references to the memory, and call gc.disable(). When you are ready you can let go the references and enable the gc.

PyPy now lets you control where memory management happens. Making it possible to control worst case performance. For many production apps this is a big deal.

CPython already has a lower latency GC than PyPy, gc.disable() already works, and allowed manual memory management when needed.

Reference counting allows you (if needed) to keep references to memory in your python code, and free them in the right spots.

This is PyPy becoming useful for a lot more production use cases. From web APIs that have a latency SLA, to audio, games. In many cases peak performance is not important, it's the minimum performance.

What is wrong with LTS releases? That's what python 2.7 is.

And the company went bankrupt (if it wasn't bailed out by MS).

Or... the Chinese phones are better (for them).

Fossil fuel cars get a huge discount for causing pollution and health problems. If other countries subsidized the damage that fossil fuel cars do as much as the USA then I'm sure there would be similar adoption as in the USA too.

man 3 getaddrinfo