splix

Yes, I understand they looked at the source and re-implemented a bunch of it when they started 10 years ago. But in the result it's a very different code. I mean, it's 45K commits so I believe they implemented things by themselves in majority of those commits. I guess we just have different understanding of the copycat term.

Copycat is a bit of a stretch here imho, considering it's in different language, and even the general architecture. But I agree they are very compatible on the protocol level, which they used as an advantage as people don't need to rewrite their code when they migrate.

I would say it's opposite. No one contributes to open source and the developers have to make money on the side to work on the project (i.e., do consulting/tech support/etc). Or more often companies with money come to fork an open source project from the developer, and continue pretending it's their own now.

I like Scylla and we use it, so I wish them well. But what I don't understand with this announcement is how it supposed to work if they don't publish the pricing model. Just "contact us to get a quote". How people are supposed to make advance plans without clear pricing?

I don't think that Java serialization is designed for such a small object with just two fields. It's designed for large and complex objects. Obviously it would be slower and much larger in size that a columnar implementation designed and heavily optimized for this scenarios. It's not a fair comparison and too far from a real use case.

Try with nested objects and at least a dozen of fields across this hierarchy. And different structure for each row. It's still not a use case for Java serialization, but at least closer to what a real code would do.

Same for Protobuf, I guess. Also the JSON serialization plays the same role more or less.

Maybe something like Avro Data Files is better for a comparison with columnar formats.

I've got an education in Russia and I don't recall such practice. Maybe some of professor do that, but that's more like an exception. Most others test your way of thinking. They even allow you to use text books when preparing the answer, though usually they allows only books they bring to the exam.

You definitely could. But I guess it should be secure by default. Even if you didn't implement any check on the server.

Because people are lazy or they may forget to implement the security checks, or simply be unaware about them.

Ex., when you hacked up a super simple script to display a number of today's users of your startup to display on the big screen in your office. You would probably want something as simple as possible. This page is just 3-5 lines of code. Maybe one-liner even. No authorization or other security, as it's for the office intranet.

Without CORS any website that is visited by people from your office could fetch that number on screen.

As I see from the public stats, it's about the rate people get for a car loan in US. And a car could easily be above $70K. From personal experience, when I had no credit history (i.e., the similar situation) I was charged twice of that rate. So it doesn't seem to be a lot.

But the "older code" is already written. And it's written with meaning "a null may occur". It doesn't seem to change anything related to legacy.

And since one of them may be a default option (i.e., the `nullable` as it's the current state), then it's just:

    private String? foo;
    private String! bar;
    // or
    private String foo;
    private nonnull String bar;

We've been using it for a while, and I'm absolutely happy with the project.

Before that, we had a Kubespray based setup. It's a bunch of Ansible script and it allows to make any custom setup, like absolutely anything as you in control of the machines. But the other side of this is that it's extremely easy to break everything. Which we did a couple of times. And so any upgrade is a risk of loosing the whole cluster, so we decided it must be run in VM with full backup before each upgrade. Another problem that it takes about an hour to apply a change, because Ansible has to apply all the scripts each time.

Then we migrated to Talos, and it's a day and night. The initial setup took like an hour, including reading the docs and a tutorial. Easy to setup, easy to maintain, easy to upgrade (and it takes minutes). Note that we run the nodes as VMs in Proxmox, so the disk and network setup are outside of Talos scope, as well as backups, and it's actually simplifies everything. So it "just works" and we can focus on your app not the cluster setup.

I'd suggest to run it on top a virtualization environment, like Proxmox. That solves a lot of problems, and not just related to Talos. Basically, you split k8s and the resource management, networking, disks, etc, as well as getting backup, migration, etc.

While the author probably wants to own the main code, I'm sure there are other things he may want to get help from external contributors.

For example unit tests. At least to show that it works, and how to use it. Also a build config, like gradle/maven, so others would be able to use this lib.

Google "Cryptographic Right Answers". There are a couple of different posts, but they agree on the most of the things you would look for.

Ex.: https://gist.github.com/tqbf/be58d2d39690c3b366ad or https://www.latacora.com/blog/2018/04/03/cryptographic-right...

There is some info at https://ydb.tech/docs/en/concepts/

How do you measure that? Do you include only companies with _no_ experience in a particular language before starting a new project using that language? Companies usually continues the language they have an experience with.

Except some areas where you don't have much flexibility. Like for AI you chose Python even if you have no experience. Or for a website, you don't have much choices and have to use TS/JS even if you don't like them.

Going for a 30-90 days to a country usually means you rent a short term overpriced Airbnb. With longer visa you can get a normal one-year lease, for most likely the same price.

For a public API you want to provide a clean and easy to use example.

It's much easier to do it with REST. In docs you can just have a _curl_ example. And the JSON req/resp are easy to copy-paste anywhere else. You can start experimenting immediately, even in the same browser tab with js console.

With protobuf there is an initial barrier, because before you start you have to download proto definitions or a client library.

Easy to execute and has no risks, all for the same salary. So the system gives no incentive to take down real criminals

Oh, yes, you're right, it's more like anecdotal experience. I didn't specify that, but I actually meant the time period when I don't expect them to break, which is about a year after the purchase. The device is still under warranty so I'm saying that some brands make it easy to replace it, some do the opposite.

There is no brand that never produced a SSD with a fault. I had tried all major HDD/SSD brands, and I think every single of them failed at some point.

What is important is how they handle that. I had a faulty Sandisk and it was replaced with a working one without any problem or unnecessary question. Some other brands annoy you with stupid questions, puzzles and other tricks trying to avoid doing a replacement. And some just ignore any requests (ex. Samsung, from my experience) to replace a faulty SSD.

After the last incident (with a week of downtime) I learned that they have a paid support, which you have to sign up in advance so it didn't work for us at that moment.

Now we signed up for it, though I still not sure how it works and how I supposed to contact them in case of an emergency. All I see they charge us something for that support agreement, hope I will never need it.

It can create problems from a different angle, though. Google might lock your account for no reason for a week, without any explanation. If that happens, it's your problem if you lose your whole business after a week of downtime. Since it's Google, you can't even contact support.

This has happened to me a couple of times. Once, my account was locked for a day because their system flagged one of my servers for suspicious traffic. They locked all my servers, databases, and everything else, not just that one server. Another time, they locked a different project for a week. It actually took me a week to find a human who could unlock it; otherwise, it could have been even longer. I still don't know the reason for the lock.

So the main problem is that Google don't care about GCP at all, and threat paid customers in same way as free users (i.e., hostile to both)

This real person doesn't really have any significant advantage.

From my personal experience, when you have a problem the only thing they can do is to call someone and talk on your behalf, and you can do the same from home, btw. The only advantage the banker has in this case is that they have those numbers on fast dial. But keep in mind that even if you called the right department nothing can be resolved immediately and all the following communications are by paper mail, so it takes months to recover your funds.

If you need gRPC, I can recommend https://kreya.app/

Is there any resource to read about the economics of subsea cables? I bet it costs a huge amount of money and time to set it up, and a lot to maintain it. Curious what are the actual numbers. And does it pay off?

The difference is that with communism a natural human desire is punished, while in capitalism it gets rewarded. I mean a desire to do a good for himself, and only himself, ignoring the needs of the others. Maybe we don't like it as the society, but that's the people's nature.

It seems that it's more effective to leverage this natural desire (as in capitalism) rather that punish it (as in communism). The important part is "natural", i.e., people are born with it, as well as animals, and you cannot prevent it. That's not a minority at all. So the only way for communism is to constantly fight it on a great scale, which is possibly with turning into a authoritarian government.

Considering that nowadays "the menu" is just a QR-code link to a web site it's not so much of a big deal.

PS Also consider that the other counties have been able to print the menus regardless the tax fluctuations. It doesn't seem to be a problem.

MongoDB is much easier to setup as a HA cluster

Not necessary Asian btw. As a Russian I can tell that Russians also may use "family name - given name - father name", usually in official documents.

Though it it also may be just "given - family", as well as any other variation informally. So you wouldn't make a mistake with UI