sensible | Maintain media-queries where they belong ; in the SASS/SCSS | Style Language library

I'm learning that Golang channels are actually slower than many alternatives provided by the language. Of course, they are really easy to grasp but because they are a high level structure, they come with some overhead.

Reading some articles about it, I found someone benchmarking the channels here. He basically says that the channels can transfer 10 MB/s, which of course must be dependant on his hardware. He then says something that I haven't completely understood:

If you just want to move data quickly using channels then moving it 1 byte at a time is not sensible. What you really do with a channel is move ownership of the data, in which case the data rate can be effectively infinite, depending on the size of data block you transfer.

I've seen this "move ownership of data" in several places but I haven't seen a solid example illustrating how to do it instead of moving the data itself.

I wanted to see an example in order to understand this best practice.

I've done a fair bit of searching here and elsewhere, but haven't found a clear answer...

I have two apps which will share considerable functionality and access the same cloud data, but are still quite distinct. A similar public example that comes to mind is Uber: one app for the driver, one app for the rider. They apps share a lot of core functionality. I think it does not makes sense to have one monolithic app that presents two significantly different UXs and sets of functionality based on the type of user... Or does it?? What are the main advantages/disadvantages to this approach?

I'm not totally sure, but to me it seems more sensible to have two separate apps which import a "core" library that contains the elements common to both apps (some data models, some UI widgets, etc.). How does one build the two apps in such a situation? Can I build both from a single Flutter project, or do I need separate projects for each app?

1. If building from a single project, how does one configure it to build two different apps? (Using flavors doesn't seem appropriate for this; I am already building multiple flavors for each app: DEV/TEST/PROD)
2. If building from separate projects, it seems that it should be simple to have an additional (third) separate project for the core library, which can be built/saved to a private GitHub repo. I have read that putting the core library in a separate repo can be problematic/inconvenient due to how pub caches packages. Is this still true? Is it as simple as specifying separate folders in the single repo for the three different projects? Are there other things to consider with this configuration?

In a heatmap, how could I create a three-color gradient, with blue for negative values, red for positive values and white for zero, such that with many zero values, much of the heatmap would be white (and not light red as with the default gradient).

When displaying some SVG icons within an SVG of a fixed width, they should be clipped to the width of that SVG container.

In all sensible browsers this works fine but in IE11 the icons extend beyond the width of the container.

Is there any workaround to counter this behaviour?

Today i upgraded my account to Colab pro. Although it prints the ram as:

I have an (X,Y,Z) numpy array that describes every point inside a box. I would like to do a 3D plot of this data where the colour of the point at [x,y,z] is the value of that point in the array I have so far tried something along the lines of:

I'm making a request to my server with AlamoFire, and I have a setup something like this, where "self.error" is a String variable.

Here's the layout I'm trying to achieve:

I have two tables:

Object stores static data, with PK Object.Id

ObjectStatus stores transient data, and is mapped 1:1 with Object so it has a FK ObjectId on Object.Id.

Given the FK is enforced unique and is the only sensible way to uniquely identify a record in ObjectStatus, is it sensible to make ObjectId the PK as well as a FK?