There used to be boxed ice cream with blueberry and egg yolk flavor. Loved it as a kid, got discontinued by the ice cream truck that had it. No replacement found. I probably won't even like it since I have forgotten the taste at this point.
BehindTheBarrier
joined 1 year ago
It's probably more common that scientific notation is used. So 3.2 *10^4 or simply 3.2e4. From the little physics I had, you often used kilometers instead of something like megameters. Or used just lightyears when you got on a big enough scale.
I got a Peugeot 208. It's small, and ok in all aspects except the software. Typical bad car UI. It works with cabled Android Auto, so for long drives that's more than fine. But touch screen is still old, and the app/site hasn't let me log in for a few weeks now... So I can't remote start heating.
But it's a great car that I bought used, for driving to and from work. Looks good, yellow color, parking sensors and rear camera for my blind ass. But is also probably not available in America for all I know, I live in Europe.
Already been explained a few times, but GPU encoders are hardware with fixed options, with some leeway in presets and such. They are specialized to handle a set of profiles.
They use methods which work well in the specialized hardware. They do not have the memory that a software encoder can use for example to comb through a large amount of frames, but they can specialize the encoding flow and hardware to the calculations. Hardware encoded can not do everything software encoders do, nor can they be as thorough because of constraints.
Even the decoders are like that, for example my player will crash trying to hardware decode AV1 encoded with super resolution frames, frames that have a lower resolution that are supposed to be upscale by the decoder. (a feature in AV1, that hardware decoder profiles do not support, afaik.)
Our company did a thing like this, focusing on the manager and above. They got password and authenticator codes out of them and admin access to the slack...
Good method to have users learn about critical thinking.
I stopped auto updating the 3rd time my god damn app was force closed when using it. Either update for the app itself or damn webview. Been many years since then, so not sure if things changed but man it was frustrating having things just go poof in the middle of something.
I do think the idea is pretty neat, although it's pretty close to returning structured data like json.
A slight disclaimer that these people are smarter than me, and know better about what we are talking about, so I may be wrong here on some assumptions. But I do get a bit of feeling they are trying to solve a trivial problem, at least in their use case. Ultimately there are only so many lecturers, and so many man lectures at a given time. The total data amount wouldn't be so much, and you can easily group by and sort on client side to achieve the original table which is show on a per lecturer basis. A little redundancy is in my opinion preferred over a query that returns 3 tables that then needs additional complicated work. I also find arguments about overlapping names to not be something the database should be handling, it falls on the data owners/manager instead. Academia is a wild west at times, but either this table is presentation only or a link to lecturer or lecture. And in the latter case, you'll already throw in the ids so they can be used in an URL to some other site.
While this can have significant less bandwidth, it also risks falling as soon as more data is introduced, as you're putting the large join operations on the client when you can get free optimizations from the SQL engine you use. I know not having duplicate data could be a thing for something where I work, where essentially we have hourly breakdowns but fetch at least the entire day for a single set of parameters. So that means 24x data for a surprisingly high amount of columns. When we only need 2 of them on the hourly level! But in this case, the data doesn't strictly need many joins as it has a lot of the information itself, along with there being too much data to join on the client side anyways for this to feel ideal. I feel you'll increase the complexity a bit too much as well. A big advantage of sql is how easy it is to understand what you are getting.
Its somewhat of a solved problem, if the performance becomes a problem, since we can return nested data anyways. So we can already today technically return a row where the hour(I think, never tried a date before) and value columns have arrays instead of a single value. We just haven't done it because it is not a big enough problem yet.
Completely agree with that, we have the same issue in C# where I work. Just waiting for the day I get to push and update to our shared code style (editorconfig) to force that.
I don't disagree that this is hard to read, but I feel it's worth mentioning python has a pretty acceptable style guide. The problem is, it's far less common in python to bundle parameters into some holding object. So here you have massive function that has to accept a lot all at once. In use it's probably not as bad looking however.
And at least, it actually explains all the damn parameters. It's a lot nicer than seeing functions parameters you don't understand, and all you have is the name. This is not limited to python either
I think the key fault lies in that most companies are publicly traded stock companies.
It challenges what corporations are at the heart. A company owned through stocks is controlled by those stock holders, and exist to make the stock holders money. It's expected for the stock to be worth it by growing, not paying out dividends. (but that is also another layer)
But that's not why a company should exist, it should turn a profit but ultimately it's about being a source of income to its workers. But stocks go against that, since stocks seek to extract money to the non-working owners. Well paid workers is rather contrary to the goal of the stock owners, as long as you can keep going.
The advantage of stock companies were getting investment to start and grow, but it forever shackles the company bar some rich maniac buys the whole thing for his own crazed ideas.
Private companies aren't guaranteed to be good either, but if they are set up right they at least aren't just a funnel of money for the people at the top.
Its because so much money can be gotten out of the perpetual invest, grow, squeeze and sell that things are as they are today. You're not a worthy company if you just increase your cash flow in line with inflation.
The need to grow also comes back as enshitification, planned obsolescence (or just made as cheap as possible), high focus on consumable products or subscriptions to ensure a steady flow of income. Making a product lasting for life? One and done, you'll grow until the market is saturated and then collapse because the cash flow simply won't be there.
Its especially noticeable when the economy takes a hit, all things go from being good investment objects to being something that needs to turn profit. So all the future profit is dropped, tons of layoffs, and rapidly increasing subscription costs. All to counter the reduced demand. Take streaming, the market fragmented, interest rates spiked so holding debt is bad, consumers have less money to spend easily. So the big ones take steps, more ads, crack down on sharing, layoffs, reduced selection and cancelation of various shows and projects. And then stock holders can be happy they once again have a good year and good growth of profit despite turbulent times.
Edit: By contrast a private company is not beholden to any requirement to cancerous growth. It too will be hurt by not having steady cash flow, but they don't need to grow until they are so big that they need constant growth to stay alive. But a private company can be steady for years without problem.
It's just the sum. Monitors have 8bit per color, making for 24bit per pixel, giving the millions mentioned. 16bit is actually 4bit per color and then another 4 for a single of those colors. But this has downsides as explained in the article when going form higher bit depth to lower.
HDR is 10bit per color, and upwards for extreme uses. So it's sorta true they are 24 or 30 bit, but usually this isn't how they are described. They normally talk about the bit depth of the individual color.
Reminds me of folding cardboard boxes. If you are taking a flat piece and make a box of it, are you folding a box or unfolding the cardboard. Or both. And when you do the reverse, you do the same, do you not?