bashcoder

A burgle.

It's been several years since I've released anything new, but here is some instrumental work:

https://soundcloud.com/bashcoder/popular-tracks

By way of documentation, this refers to FCC Part 97 rules, specifically §97.113(4):

"Music using a phone emission except as specifically provided elsewhere in this section; communications intended to facilitate a criminal act; messages encoded for the purpose of obscuring their meaning, except as otherwise provided herein; obscene or indecent words or language; or false or deceptive messages, signals or identification."

In fact, we couldn't switch to Scylla prior to 2019 because their support of incremental counters wasn't yet complete.

Hi Alex - This looks a lot like what Scylladb did to unleash the potential of the Cassandra space, with a fully optimized C++ rewrite of an Apache project. Did you draw some inspiration from their efforts?

As a satisfied Scylla convert, I'm looking forward to trying Redpanda.

Agreed. We have already migrated 90% of our workloads to graviton2. After running our performance tests, it's a no-brainer price/performance boost.

Yes - this is the issue for me with the Razer controllers: They are right-handed only. Like the Sherbet, the Azeron is 3D printed, which of course makes it much easier to manufacture left-handed models. The Azeron looks good, but at nearly 200 euros it's pretty pricey.

These have always been magical devices to me. I still use and maintain an old Heathkit capacitor tester that uses one as its indicator.

CPAN also exists, but not as it once did. Perl 5 wasn't just a language, but an ecosystem.

“Meat’s back on the menu, boys!”

In your view, does this study fall short of answering the “is it true?” question?

Alternatively, it could also be in the interest of many for these patches to have an inordinate negative affect on performance with Intel CPUs.

I am reminded that Linus has experience in the CPU industry (Transmeta), so he is in a position to see both sides on this.

The most striking thing here is that Linus has apparently dismissed incompetence as a rational explanation. Yes, he is often brash, but usually he is accusing someone of sheer stupidity. He does not do that here. Linus alleges that we are being lied to - that we don’t know the full story, nor Intel’s motives.

Furthermore, we are left to wonder if Microsoft is also being fed “bullshit” patches, and if they may be less discerning than Linus regarding a proper solution.

Yes - I’ve had five kids. The sum total cost was less than the claim in the title of this article.

The author misses one key point: it’s not only about debt coming due on their scheduled dates. It’s that much of this debt is also saddled with covenants that can cause a debt to be collectible at any time if the terms are not met. Things like a company's loan-to-value ratio, leveraged inventory through high accounts payable, and other financial metrics. In short, market troubles can force long-term lines of credit to abruptly come due.

It was my understanding that CoreOS was started as a minimal Linux distro tooled for hosting and orchestrating Docker containers. IMHO, Docker still has a long way to go to impress the security community.

Maybe, but in the meantime I can't imagine a scenario where such a direct financial threat to a business isn't vigorously defended by Symantec. I'm not a lawyer, but certainly they must be working to determine if they have a legal basis for seeking an injunction against Google. They could even be building some sort of legal theory based on tortious business interference, contending that Google is doing irreparable harm by trying to come between Symantec and the expectations of its paying customers.

How about you bump to 0.14 now, with this patch included? 0.13 is the Homebrew version, with data collection still enabled.

Fair point, but it's also fair to note that Perl 6 development began 17 years ago.

To a large degree, the ongoing utility of Perl 6 depends upon the continued vibrancy of the CPAN community. IMHO, CPAN is anything but vibrant by today's standards.

While CPAN hosts a vast archive of nearly 35,000 modules[1], many are aging. Fewer than 800 modules are known to exist for Perl 6.[2]

[1] http://www.modulecounts.com/ [2] https://modules.perl6.org/

You can request pre-warming for additional ELB capacity, when you know far enough in advance that you will have a spike. AWS customer service responds by asking 10 clarifying questions via email. The thing is, we can't look under the hood to see currently provisioned and utilized ELB capacity, so we just have to trust that AWS engineers will properly allocate resources according to the answers to those questions. IMO, it's a rather cumbersome process that would be better implemented as a form.

If you install this Chrome extension, it has the ability to "read and change your data on all google.com sites." Why is this necessary? Seems like quite an overreach.

I probably should have said that it "can" run on any node. Yes, currently it does run on every node, but their roadmap doesn't have the requirement that every node be actively participating in elections.

I'm sure that you have seen fleets of dedicated Zookeeper nodes. I rather like that etcd is simply a service that can run on any node, and does not require a separate role-specific fleet of servers just to do coordination. That was the point I was attempting to make.

I listed what I like. "Excites" is your word.

I guess what I meant by "from scratch" is that they aren't burdened by legacy code, and aren't limited to using the Paxos algorithm.

If you look at Deis, for example, it basically outsources a lot of node management to Chef Server, which in my view creates a great deal of technical debt on day one.

I know that there are lots of heavyweight folks who swear by Zookeeper as both a reliable and powerful tool, and for good reason. Unfortunately the docs can be fairly inscrutable, even for experts, and it typically requires the maintenance of a separate cluster of Zookeeper nodes.

So I like that etcd is a fundamental component of CoreOS, with these features:

  1. Written from scratch in Go
  2. Implements the Raft protocol for node coordination
  3. Has a useful command line app
  4. Runs on every node in a cluster
  5. Enables auto-discovery
  6. Allows CoreOS nodes to share state

Haha - we posted the same link, so I will +1 yours instead. This article is very much in keeping with the spirit of that book. A friend kindly gave me a first edition from 1954.

The author makes no reference to a non-compete agreement. His former company claims that he stole their code and put it into his public repo, not that he is violating his non-compete.

If the accusation is false, it's easy to prove. But the problem is that a company can bankrupt an individual with just the legal fees involved in the discovery process and depositions alone, even if it doesn't go to trial. So most folks are forced to yield, as the author is doing.

The writer is also incorrect about the nature of obsolescence. Something only becomes obsolete when a better system prevails and the old system falls out of use.

This has not happened, and if it ever does it probably won't look anything like what the author proposes.

When comparing to AWS, it's worth noting that both Linode and DO continue to charge hourly fees for instances that have been stopped but not destroyed.

AWS does not do this. Stop an EC2 instance and you stop paying hourly instance fees. Even if it hasn't been terminated.

There are small fees for maintaining EBS volumes if you are using them for inactive instances, however.

For future reference, AWS security bulletins can be found at:

https://aws.amazon.com/security/security-bulletins/

The author suggests that Amazon only made one post, updating it throughout the process. But at the link above you will see four posts regarding this issue, with the first one having been updated once to add information. No, they are not timestamped, but they are dated.

While it may be fair to criticize AWS for its customer communications during this process, I'm fairly certain that if he had a backstage pass to such a comprehensive process of remediating thousands of production systems with zero downtime, he would perhaps find the team somewhat less... amateurish.