dhd415

Amazon's record with OSS contributions is notoriously poor. For example, see their refusal to allow their query routing extensions to pgbouncer to be used on anything other than AWS:

https://github.com/awslabs/pgbouncer-rr-patch/issues/3

There's certainly room to criticize Elastic for their approach to OSS and/or their response to Amazon here, but Amazon's "open-sourcing" of a bundle of the OSS bits of Elasticsearch plus a few third-party OSS plugins is nothing other than self-serving, opportunistic PR.

With the rise of cloud computing, the effort by cloud providers to commoditize their complements, i.e., software, inevitably leads to this particular kind of conflict between companies backing OSS software who wish to deploy their own SaaS offerings and cloud providers with their own SaaS offerings. A common response is that OSS backers can build businesses based on support and consulting but I believe that's overly restrictive. Those kinds of businesses don't scale nearly as well as managed services and it will definitely have a chilling effect on OSS development if the kinds of companies that are permitted to be built on them are simply support and consulting. I don't believe that companies backing OSS have an exclusive right to offer managed services for their software, but the current situation with cloud providers offering managed services with only token engagement with the OSS community (and then only when forced into it by licensing restrictions) is not beneficial to OSS, either.

To be clear, no Elasticsearch code or features that were OSS were closed. As new Elasticsearch features are developed, some of them are now released as OSS and others are released with a commercial license.

Putting aside the ethical questions of this approach, I've not been able to determine how good a job will be within the first week. It usually takes me a couple months.

If you click the "History" link on the front page, you can look at a bunch of examples.

It's definitely the project system. I once worked on a solution containing ~150 projects. I consolidated all the code down to about 15 projects and the build time of the solution dropped by about 5x. I've been working in Java lately and frankly, I see little difference in compilation speeds between the two.

Wrapping a sync method in a Task causes a thread to block on the sync method's completion and blocking threads is much of what async/await is intended to alleviate.

Yes: https://www.holloway.com/g/equity-compensation

I'd dispute the idea that a car with 130k-150k miles can't be enjoyable. I've had multiple BMWs with more than that many miles that were plenty enjoyable. None of them had any drivetrain replacements though all of them had suspension replacements as should be expected as those are all wear components. I've even had other BMW owners remark that my 200k+-mile car drives better than their own with ~60k miles due to the recency of the suspension component replacements on mine.

There's certainly degradation that occurs to a car with lots of mileage, but it's generally with the interior and the electrical systems. There may be some exterior corrosion, too, if you live in the appropriate climate though corrosion resistance has improved a lot on cars lately. And, of course, all bets are off if you don't properly maintain the car.

401(k)s are fundamentally about the tax treatment of a certain class of employer-affiliated individual retirement accounts. There's a reasonable range of securities that can be held within a 401(k) account (often at least partially at the account holder's discretion) and some of those securities are considerably more risky than others.

Elastic maintains a page documenting the current status of their "resiliency" efforts on Elasticsearch:

https://www.elastic.co/guide/en/elasticsearch/resiliency/cur...

I've also had friends who have had their MailChimp accounts deleted or locked without explanation, warning, or recourse, so I wouldn't rely on MC specifically for anything business-critical. That said, if you have business-critical data on any cloud provider, you should be exporting periodic backups of that data to another provider so you don't lose access to it all if a single provider shuts down your account.

That applied only to certain AMD CPUs that were available in 2012. It's just an example in which there was some effort to take a "fairer" approach to per-core licensing. It's especially notable since the EPYC line is evidence of the great strides that AMD has made since then when MS just gave you a blanket discount for running SQL Server on AMD cores.

SQL Server switched from CPU-based licensing to core-based licensing as of their 2012 version and they included a "core factor" that reduced licensing costs if you were running on AMD cores to 75% of the cost for Intel cores to account for AMD's then-lower per-core performance.

http://download.microsoft.com/download/7/3/c/73cad4e0-d0b5-4...

I've encountered some well-run and successful companies that hire remote employees and the two things that seem to be common to them is that they're remote-first and remote-first from day one. Transitioning into either of those seems a bridge too far for most companies.

LSM trees are good for frequent updates on recent data. Frequent updates of old data are much worse on LSM trees since they trigger merges on the oldest (and typically largest) levels of the tree.

Some storage engines allow for in-place updates of records if the fields are fixed-length or if the updated variable-length value fits in the existing space. I've used some of those (e.g., MS SQL Server) to good effect in high-update scenarios.

VS has never been required to develop on the .NET platform. E.g., CSC works fine for C#.

The concept of "status illegibility" is certainly an interesting one that coincides with some experiences I've had. In a former role in which I reported to the VP of Engineering, due to his lack of ability to directly evaluate work, he would base performance reviews on a weighted average of your teammates' assessment of your work. As such, it was very much, as the linked article on status illegibility states, that the "illegibility of the status of any member of a group is proportional to his/her distance from the edges of the group." In other words, performance near the median was widely praised, but performance both near the bottom or top received criticism. It was not a pleasant experience.

Another hard-learned fact that he mentions is that being good at your job is overrated. Few of us would like to admit that, but as he explains, the benefits of some automation vs. no automation greatly exceed the benefits of some automation vs. better automation. The only workaround that I've found for that is evaluating roles for their need for technical excellence. Building a CRUD app to "revolutionize the [insert favorite industry here]"? It's not going to require or reward technical excellence. Unfortunately, the kinds of projects where technical excellence is legitimately required and rewarded are relatively rare.

Completely agree. I've taken to running Windows Server on my workstations for that reason though the price is much higher.

It's been a very long time since brick or stone were commonly used as structural elements in US houses. For decades, houses have typically been stick-frame, perhaps with brick or stone used for the facade. In such cases, the brick or stone is serving merely as cladding for the house just as siding would. Brick or stone facades are typically more expensive than wood or fiber cement sidings but the choice of the former rather than the latter is based on aesthetics, not intrinsic quality. There are definitely high-quality and attractive houses that have no brick or stone. For example, this older house was re-clad with fiber cement siding and it's appropriate for the character of the house:

http://www.fibercement-siding.com/wp-content/uploads/2011/09...

There is definitely a lot of corner-cutting when it comes to new housing construction in the US for the low end of the market, but it's usually seen with poor insulation and energy efficiency, low-quality cladding and paints, and "builder-grade" fixtures. Very rarely have I seen chipboard or MDF used. OSB, on the other hand, is used even in high-end construction and, as an engineered alternative to plywood, has a number of benefits over plywood including increased strength, lower cost, and lower environmental impact.

As for staple gun and nail construction, I can't say that I've seen the former, but nails are a superior fastener to screws for many structural applications such as framing because they have a higher shear strength than screws. A nailed stick-frame house doesn't require specialized tools or skills to build, is relatively low-cost and uses renewable resources, and can easily last 100+ years. It's an excellent choice for many houses in the US.

Or cheaper Glendronach for that matter? It's 40-60% more expensive than Macallan here.

Perforce has supported concurrent versioning since at least 2001 if not earlier. Individual files could be marked as requiring locks which is useful for binary files for which concurrent changes cannot be merged (one of the big reasons why Perforce is so popular in game development), but it's not either the default or only option. It sounds like your organization had severely misconfigured Perforce.

I'm not sure articles like this one do non-database professionals any favors by associating unrelated concepts that are often found together such as relational databases and ACID compliance. There are both relational databases that are not ACID-compliant such as MySQL with the ISAM storage engine and non-relational databases that are ACID-compliant such as Spanner, FoundationDB, etc. The data model doesn't imply one or the other at all.

It's because of selective incorporation. (https://www.law.cornell.edu/wex/incorporation_doctrine). For example, the Second Amendment wasn't incorporated against the states until 2010 in McDonald v. City of Chicago.

I think the article intended to highlight features specific to PostgreSQL. CTEs are undeniably great, especially recursive CTEs, but they're also part of the SQL:1999 standard and available in lots of databases.

Long comment thread on a previous posting: https://news.ycombinator.com/item?id=12166585

TLDR: Uber is using MySQL as part of their "Schemalass" key-value store (https://eng.uber.com/schemaless-part-one/), a somewhat unusual use case in which it may be a better choice than PostgreSQL. It's not really an evaluation of MySQL vs. PostgreSQL as relational databases.

LSMs do not guarantee that sequential key/value pairs are stored in the same SSTable so reading "n" k/v pairs, in the worst case, could require seeking through "n" different SSTables. There are datastores that use LSMs such as HBase that provide guarantees on top of LSMs to facilitate efficient range reads and, of course, many LSM compaction algorithms improve range reads, but the basic LSM is optimized only for single k/v reads. That's the reason, for example, why Cassandra doesn't even offer range reads such as "SELECT * FROM mytable WHERE KEY > x AND key < (x + k)".

I have the same setup and it's great for some development tasks, but its single-core speed can't match the latest processors. I actually installed Linux on my company-issued MBP and I run a bunch of dev tools on it via Xwin from my z620.

For those reasons, I like Xfce and LXDE on Xubuntu and Lubuntu, respectively. I use those for workstations, they've got the same CLI features as Ubuntu, and I don't need or want a bunch of GUI chrome in my dev environments.