I heard Elon Musk state in an interview that they gave every new line of code 1 point and every deleted line of code 2 points so clearly at least Tesla seems to value fewer lines of code.
Um, even if it's mature technology that doesn't negate the costs of operating two different databases which is a large part of what the original presentation is about.
Indeed! The "Latency Numbers Every Programmer Should Know" page from Peter Norvig builds a helpful intuition from a performance perspective but of course there's a lot larger cost in terms of complexity as well.
Yeah, this is what doesn't make sense to me. Why not leave the current approved app listing up? Why, during an update would they completely remove the listing for previously approved versions?!? Is the process really that broken?
Thanks for your video. This no doubt foreshadows the Raspberry Foundation eventually moving away from the Broadcom SoCs to their own custom SoC for future Raspberry Pi iterations as well.
It's not a matter of whether a contract was breached. People tend to get upset when trust is broken. I suppose your argument is that people shouldn't have trusted RedHat because no money was exchanged but that's not really how trust works in real life.
Lucene is a pretty low-level search library. It has no concept of clustering etc. etc. What ElasticSearch built on top is far from trivial. Furthermore, ElasticSearch pays a number of people to contribute back to the Lucene project.
As far as I know AWS hasn't contributed any code of note back to ElasticSearch or Lucene.
It's a bit more muddled then that since AWS isn't using the true ElasticSearch bits but rather an OpenDistro fork of it that they created themselves. So is it still ElasticSearch? Mostly, but it's not exactly the same thing either. But of course AWS would want to leverage the name recognition of ElasticSearch...
It was interesting to me how many of these were related to making async calls to adjust state resulting in race conditions. In many cases the argument was made that async calls were not justified. Many times we follow a particular call pattern in order to keep things consistent without fully considering whether it's necessary and/or safe.
Also I wasn't aware of the tool named Frida[0] that she kept referencing so I had look that up.
I guess the downside of using this mechanism is that if you already have an external monitor attached then you can't use this solution? Or is there another way to use Deskreen? For example, my Mac laptop is already plugged into a large external display so there's no free port for a dummy plug like this.
The downside of that attitude is that if a chat program is only used for what governments consider subversive activities then it will be targeted to be shutdown. It is much better to have a general-purpose, secure chat program that IS mainstream making it more difficult for oppressive regimes to target.
I think one of the issues (beyond media's propensity towards sensationalism to draw attention) is that the extremes at either end of a debate are very black and white. Black and white can be explained in a single sentence many times but everything in between is nuanced (or grey as you called it). The problem with nuanced positions is it requires more than a 280 character payload to explain...
This. We run CentOS for non-critical stuff and RHEL for stuff that really needs support. If we need to switch off CentOS we certainly won't be using RHEL either. Doesn't make sense to be running a Debian flavour mixed with RHEL since the two a significantly different.
I wonder whether we'll see the day when the satellites themselves can contain say, Netflix/Amazon/Disney cache servers to cut down on back haul traffic?
You've got that right. We're quickly heading back to the days of "This website best experienced in IE6." (replace IE6 with Google Chrome). It's not a good thing.
This helps mitigate some risk but if you're using OAuth or rely on receiving future emails via your @gmail.com account you're still out of luck regardless
And there are ways to manipulate RAM access patterns to induce errors as described in the initial Rowhammer attack paper plus later RAMBleed papers. Hopefully this newer DDR version is designed to be resistant to this type of attack.
That's not true unless you mean "free LTS" JDK from Oracle. There are several other projects providing free LTS, TCK-certified builds including: RedHat OpenJDK & Amazon Corretto to name two off the top of my head.
What's funny is there were versions of the JVM for Sparc way, way back in time (Java 1.1) that had so-called green threads which were multiple threads mapped to a single (or multiple) native threads.
This is based on the Apple/Google API initiative. Now if only we can get the provinces onboard with this. One of the things about Canada is that the provinces are largely responsible for funding and delivering health so that federal government can not mandate that the various provincial governments adopt this. A couple of provinces have their own applications but none of these apps have approval to use the Apple/Google APIs so hopefully they'll drop them and use the Canadian one instead. It makes more sense to have a single app for the whole country.