ipozgaj

The cost of this acquisition will likely just get passed down to consumers by increasing the already ridiculous delivery and service fees even further... The only reason why I ever use DD is because DashPass is included in the CSR. Otherwise you pay $10 of extra fees for a $12 burrito.

At this valuation this is a very risky investment because the current price already accounts for future growth, so there is very little margin for safety or meaningful upside left. The sole purpose of this IPO is for early investors and employees to cash out. I wouldn't touch this stock with a 10 foot pole.

You also use your phone that requires cobalt mined by child labor, wear clothes made by slave labor in countries like Vietnam and Bangladesh etc, so what's your point? The world is not black and white.

You use more than half of those on a daily basis just by using any piece of modern electronics or connecting to the internet.

> These people have arguably contributed nothing to society for over a decade

React, React Native, GraphQL, LLama, PyTorch, RocksDB, Cassandra, folly, Hack, HHVM, OCP, Presto, btrfs, cgroupsv2/PSI, eBPF, zstd, roughly 12% of all Linux kernel contributions are signed off by Meta + Meta is the 5th biggest contributor to Linux kernel.

Also a ton of other projects that did not originally come out of Meta but get a ton of patches and support/funding: MySQL, Memcached, Hadoop, LLVM, Systemd, Rust, Python etc.

Perhaps research a bit more before you make these ignorant comments.

Any change that hurts WITCH (Wipro, Infosys, TCS, Cognizant, HCL) is a good change. If they just plain banned those five, there probably wouldn't even be a lottery.

Tech aside (covered well by other commenters), the presentation itself was incredibly dry. Such a stark difference in presenting style here compared to, for example, Apple's or Google's keynotes. They should really put more effort into it.

Loaded it. Typed "help". Asked me for $5. Closed the app.

You can do that with standard Linux tooling available on every distribution, see https://man7.org/linux/man-pages/man8/tc.8.html. What you're specifically looking for is `qdisc netem`, it can inject packet loss, reordered packets, duplicate packets, delay and more.

I am lucky enough to have worked on all three of these systems (TAO, ZippyDB, and currently MySQL) so can shed some light here.

Both MySQL and ZippyDB are datastores that use RocksDB under the hood, in a slightly different way and with different querying capabilities exposed to the end user. ZippyDB uses it exclusively, but MySQL uses both the traditional InnoDB and RocksDB (MyRocks). TAO is in memory graph database, layer above both of these, and doesn't persist anything by itself - it talks to the database layer (MyRocks).

I took a look and don't see any strong reasons not to use and support the official app. Tweetbot was so successful because it was competing against the official client which was (and still is) truly horrible, but I don't see that in this case Ivory has many advantages over the official client.

Most of the "new" features are just eye candy, but usability is still very poor and way behind what they had 10 years ago. You can't do even the most trivial things, like sorting stocks in your watch-list by market value or P/E ratio, comparing two stocks side by side etc.

There is also `colordiff` which works both as a standalone diff tool, but also as a colorizer filter for other diff tools. For example:

  diff -u a.txt b.txt | colordiff

It seems that the person in question was #2 on the "patent trolls top list" in 2016

https://www.rpxcorp.com/wp-content/uploads/sites/2/2017/05/t...

Yes, a small but measurable improvement. The biggest perf bump you can get is probably enabling various prefetching, but most of time you are doing a performance/privacy tradeoff (e.g. enabling DNS prefetching)

Manifest V3 and killing web.request API were the reasons that finally convinced me to go back to Firefox. Almost a month later, I didn’t find a single thing that would make me go back to Chrome.

My main complaint about fresh Firefox installations is that it takes a lot of time to fine tune everything. Every single time I have spend hours changing settings in about:config, from disabling telemetry, Pocket, changing networking/DNS settings, pipelining etc. Vanilla installation is just not well optimized.

If you use and like `ag`, I suggest taking a look at ripgrep (`rg`). It seems to be by far the fastest out of three (`ack`, `ag`, `rg`). And it has a pretty interesting codebase (written in Rust).

I wouldn’t recommend anyone to use this. Other than really poor implementation and quality of the algorithms (some of which are totally incorrect), code in that repo is anything but Pythonic - reimplementing a lot of things from the standard library, not using list, dict and set comprehensions, using indexes instead of iterators, copying things around for no reason etc. They didn’t even care to use linter to PEP8-ify it.

People commenting that $35 is too much for the content included - if you want an equivalent set of channels from Comcast/XFINITY, it will cost you almost 3x more. So it's a non brainer for me, and the fact I don't have to deal with Comcast is worth even more than saving ~60% of my monthly cable bill.

Not sure why are you getting downvoted, I came here to make the same comment.

QPM is a useless metric. When talking about distributed systems from engineering point of view, you always want to use QPS. QPM is simply not fined-grained enough to show whether the traffic is bursty or not. For example in this particular case, when you say 1M QPM that can mean anything - they might be idle for 50s and then get 100k QPS for the next ten seconds, or they might be getting 15k QPS all the time (like it's visible on the graph). Distributed systems are designed for the peak workload, not for the average one. Using misleading numbers like QPM leads to bad design and sizing decisions.

The only case where you would use QPM, QPD and similar metrics is when you want to artificially show your numbers bigger than they are (10M transactions a day sounds better than 115 transactions a second). But those should be used by sales, not by engineers.

It's basically the Sieve of Eratosthenes[1] algorithm, and it's possible to do it with regular expressions because numbers here are represented in unary[2] number system, where number of characters/tokens equals the number itself. It's a common trick for testing various Turing-machine stuff.

[1] https://en.wikipedia.org/wiki/Sieve_of_Eratosthenes [2] https://en.wikipedia.org/wiki/Unary_numeral_system

You don't need grep for that, ss can already filter by state on its own. Use: "ss -o state LISTENING"

For a moment I thought I was reading Buzzfeed, not the Economist.

Because the whole story was bs? Zuckerberg himself commented on that https://www.facebook.com/zuck/posts/10100828955847631

Correct, if you try to open http://<hostname>:9090/ it will get automatically started. I'm not concerned about the resources it uses, I just don't like having services that I don't use installed and listening on ports in minimal install, especially on servers.

One thing that I was pretty annoyed about while testing (server) beta and alpha was Cockpit web UI that is enabled by default. I know it's easy to disable it with `systemctl disable cocpit.socket`, but if you select "minimal/base install" you shouldn't get a full blown web UI management console installed and enabled by default.

Even if API gave you strong durability guarantees, it still wouldn't mean much. Disk caches, big enterprise SAN attached storages etc, they can also "cheat", saying they flushed the cache while they actually didn't.