codegladiator

Hardly making a dent here !

It's not your server.

Anti-virus softwares are the Anti-vaxers of digital world. Falsely believing they are in the correct group and benefiting the society.

> list.max(Math.ordering)

Isn't it very hard to "not think about it" when required to not think about it ?

Why people never bargain for branded products and mall shops ?

> that they unconsciously do listen

subconsciously ?

same as https://www.websequencediagrams.com/ ?

Question, should I go to office tomorrow? First case just reported a few hours ago.

Thanks but majority of the target audience is in SEA. Also we considered moving to DO only once they had their k8s offering ready.

I might have missed it in the search, but seems Hetzner is probably still working on it. Nobody here like to deploy k8s although the tools to do that are super sexy these days.

I used to get 18k monthly bill on AWS, moved everything to DO and now it costs me 8k a month. Billing is so much easier to understand now as well. It was k8s to k8s cluster transfer, so migration wasn't very painful.

Depends on the features and quality of the thing.

I used to think I would never pay for an IDE, but then intellij changed my mind.

> Citizens of a democratic nation have one job to do.

And they are doing their job. Voting was never a job.

It works for me with NoScripts blocking the two js requests it tried to make.

3NF or more is good. Else its poor. Number of tables does not matter.

> don’t adhere to any specification, let alone OAS

OAS is not a specification to adhere. It is a specification to describe.

> OAS now have GraphQL APIs instead — or even JSONAPI

OAS is orthogonal to GraphQL/JSONAPI. With OAS you describe what the API is which could be JSONAPI or some custom API adhering no standard.

Only by repeating it frequently over span of months.

I think you are just agreeing with what I said.

> Plus gui's for what exactly

GUI is a huge separate feature request and not "criticism" per say.

> but the effort can be disproportionate

Hence the different beast.

Like I said, I just cannot justify any reason apart from the convenience of using gui to develop that.

> you just don't have the will to do

Sure, will to do, is one thing. Consider I request the curl dev to make a gui for it. would you find it unreasonable because everyone is okay with cli ?

I just cannot justify any reason apart from the convenience of using gui to develop that.

> separate out the code from the cli to a library usable by both is also a bunch of work

The time and amount of work is in my opinion not just about the amount of work, because if that was the case why develop even the cli and opensource it ?

Make a GUI is just a different beast compared to CLI.

> just don't have necessary time or will to code

Or the intention to begin with, which is the situation OP points out as non useful negative criticism.

But yeah, I don't see "request for gui" as a criticism for a cli application. More like a feature request.

> Its Microsoft's "responsibility" to "clean up after their mess". No; We're beyond fighting about who should take responsibility.

I feel opposite. It is definitely MS's responsibility, but they don't care because they are not going to be pawned. Its the poor users who MS suggested to use corp as their AD domain without buying that domain in the first place.

Every time any corp fks up, the people have to pay for it (maybe by getting hacked, or being saved by state) and corps don't care.

> Its too generic

Right, and who chose it ? This domain is like example.com except it ain't because people don't mistake it for being meaningful, MS advised people to use it explicitly.

At what point can one say the lookalike is actually one's image ?

Phew, yes my bad

I think discovered is exactly the right word.

Sort of like India was discovered by Columbus, of course people were living in India before.

> where the savasana in the end of the sessions

fun fact, savasana translates to "Corpse pose" or dead man position in english.

> how do you devour a whale? One bite at a time.

Missed a step. You gotta kill it first.

Don't do it. Find someone else, who is at least as much or more enthusiastic about starting a company to work on a product.

Building a product is hard, building a company is harder. There will be lots of ups and downs, so what you don't want is to end up "try to convince to continue working on it" them again every 4-6 months.

Find someone who will convince you.

I think you are right.

At some point system 1 will need to talk to system 3 to validate the message (unless system 1 and 3 have an already shared secret or public key)

> a signature from system 2

That's why they are talking about signature from system 3 along with the payload.

So even if they trust system 2, they can be sure system 2 has not tampered with the message generated by system 3.

Innocent until proven guilty. Never innocent once proven guilty.