sundbry

Very neat. Looks like something similar to a lightweight Onyx. Can it handle async event handlers in this version?

Evolution depends on the competitive aspect of genetic groups as a means of specification. You can say resisting specification is somehow a morally superior position, but really, it is just a sentimental one. Specification will happen regardless and merging will also happen. When there is enough competition for resources, usually only one species wins out. Being apathetic about becoming a dead branch in the tree of evolution is probably going to have that exact outcome.

50,000 engineers just to run a bank? I don't think so.

Not if there's a cell tower every 100 yards putting out 30dB more power than your phone. The inverse square law also doesn't apply when you have phased arrays doing beamforming if you're directly in the path.

Probably because in your corporate/controlled environment you're supposed to use the company DNS for a good reason.

You're not the only one. I remember spending a good two days on it this year for a page where the user puts in their credentials for external integrations.

In Soviet California, forest fire prevent you!

Is it really so difficult for engineers to create a task to process a Kafka topic? It takes one day to write a program to consume from a topic of events and push to an API like Amplitude, and you have total flexibility in how you push to those integrations.

Why would you use postgres for an event professing system? This seems like an inefficient architecture.

That's total bullshit. https://www.law.cornell.edu/uscode/text/8/1325

51 pounds?

Glimpse sounds like a great name. If it brings new development into the project it can't hurt. I have no problem with the GIMP name, as a frequent user, but some times things need new names to evolve.

You'd only need to put the NS records in for each domain.

Yeah, why even let the Nazis have IP addresses? In fact, if we took away their computers, pens, and papers, surely that would make them less likely to lash out violently.

Hiroshima "Little Boy" was the first to land at only 15kt, but Nagasaki had the H bomb.

That's where aluminum 'chemtrails' come into play, to create HE radio channels. https://geopolitics.co/2015/04/03/chemtrail-pilot-blows-the-...

Emojis.

An efficient immutable vector can be concatenated much faster without any reallocation of either array; one would probably outperform .push for bigger arrays in this case.

You should handle it in the most immediate context which can do something productive with it- if there's nothing you can do but swallow it, you should probably let it continue to pass up the stack. If you can handle it and log a warning and return something else, you should handle it there.

For example, if you're writing an HTTP handler for an API, you should catch any exceptions at that point in your handler and return a 500 with an appropriate response to the client, since returning 500 is something productive we can do (vs letting it pass and crashing the server).

This is about message passing at an abstract level, which is what Alan Kay imagined with Smalltalk. You are the one missing the point....

When you are dealing with external systems, such as a third party API, the message passing paradigm is what you are dealing with. There is no static typing for someone else's API (even if you are using their SDK).

The reason we haven't replaced human-engineered computer programs with "HAL do this for me" instructions is because the devil is always in the details...

Perhaps the continuous executive push for cheaper international labor is having an impact on their core competence. Who could have known.

It's called regulatory capture and forget that if Facebook, which grew to the size it is at because in part of A/B testing, gets to now lobby for rules to make it more difficult for newcomers to do it. We used to have anti-trust legislation in the United States (we still do, but hardly use it). Special regulations for the behemoth corporations is standard jurisprudence.

That's in fact not the stated purpose of the government at all. It is not a utilitarian construct.

There are two separate meanings of the term server.

1) An application which runs on a network and services clients 2) A dedicated computer which runs server applications.

He could easily have exfiltrated the data without ever leaving the premises. All he would have to do is is walk into a lab room with an unsecured terminal to upload the files, or used his phone to upload the drive, there aren't hundreds of ways to pass the data off once it's on a thumb drive.

In the end, I don't think you actually answered your original question?

I'd say do what you will, and if you reject their code, they'll probably be fine living on in a fork of your project. Personally, I wouldn't mind using code from someone I disagreed with, because in the end, our common interest in a piece of software might be one thing that brings two opposing parties together, rather than divides them apart.

We had to get out of the bay area this weekend. It was just too much to handle, waking up wheezing and with headaches all day long. I wouldn't be surprised if we see elevated rates of lung cancer in Northern California in the years to come.