revelation

Don't take this too serious. If it would stop driving bans for diesels, this government would also consider rainbow unicorns for every school kid.

(Hello downvotes? If you are not in tune with German politics: this is the same government that is in contempt of court for failing to enforce effective measurements to stop excessive pollution levels. This is not at all a sincere suggestion.)

They are complaining about "toxic content directed at children". We are talking about the worlds biggest ice cream manufacturer, they own brands like Lipton who make billions from sugar water with ads like these Muppet animations targeted at children gulping it straight from the bottle:

https://www.youtube.com/watch?v=O8n-BF5lrnQ

Once those kids are fat teenagers, they own Axe of course, infamous peddlers of archaic gender role pushing crap like this:

https://www.youtube.com/watch?v=IpPJjgIfRkI

So yeah, the first step on making responsible ads for the internet is banning these particular vermins at Unilever.

Actually, they are. Arguably it's the cryptominer fools that the part manufacturers want nothing to do with, because chances are you ramp up manufacturing now (so 3-6 months until you actually see higher supply) and by then they are on to the next coin fad.

This isn't even a UK case. What do they care if Sweden wants to drop it?

A basic lack of fundamental understanding has caused the author to quickly fall into an expertly laid trap by marketers that seek to equate 48 volt systems with some sort of "green, hybrid, clean" spirit, leading to such bizarre statements like "The advantages of the new 48-volt systems are considerable. They offer fuel economy improvements of up to 15 percent"

Of course it's all about saving a few dollars on copper.

Eh, not for WebGL it won't. Nobody even implements DX other than high-powered desktop GPUs.

Will it live on? Sure, we will still have games and Xboxes. But if you're going to pick a standard that can work on mobile and desktop, there is no contender other than Vulkan.

Today, APIs don't keep working for a month because someone thought replacing careful design with a bad emulation of SQL is the new hotness. They call it GraphQL.

This is a bit of a rambling mess, but to just make one point: the winner has been chosen. Android is implementing Vulkan, and so Vulkan it will be.

Not Nature, reviewers.

Your mistake is in assuming that someone is trying to solve some scholarly distinction between who matches the dictionary definition of either term better.

No. It's a tax construct, and that is the only criteria we should use to measure it.

For power management and sequencing chips. Like a BIOS would.

There are no interesting drivers there.

The poorest inhabitants in London don't live in the kind of home where they can install a wood stove. They rent and likely have central heating.

If it is so trivial, what is the big deal with "Single Page Applications"? Seems like plenty of pain there in the HTML and CSS world..

Meanwhile, there have never been anything but Single Page Applications in the native world.

And sure, Qt is now more than 20 years old, it's from a time strongly rooted in "widget" based UI systems that have somewhat fallen out of favor. That is what QML is for, which similarly to WPF that started this trend, allows for GPU accelerated vector composition of anything you could ever want, with sane provided defaults so not every project is reinventing grids.

It answers the question: you can't just look at gross native memory usage and conclude the Java app is 100x less efficient, that value simply doesn't tell you a lot. Server VMs are commonly configured to use gigabytes of RAM from the get-go, and when the initial VM heap is full, Java will not make small adjustments but instead grab a big chunk, and when that is no longer needed, it is often reluctant to release that additional memory.

I have no doubt that a Rust app will generally be more memory-efficient, but ultimately for server applications that is really not something a lot of people care about because of the incredibly low cost of "just buying more".

Java has its own heap so the memory usage, certainly for a server VM, doesn't necessarily correspond to actual application memory use.

(Also, of course, your main server uses "up to" 5 GiB? That's fucking great. Until it goes beyond 64 GiB, who even cares. Work on something that has a worthwhile monetary return..)

Teaching students and teaching in general is time not spent writing that paper that gets you your PhD / postdoc job / tenure. Eliminate as early as possible to make sure 1) the load from incompetent students does not potentiate and 2) to spend more time with & recognize the ambitious students that you can recruit for free work on your PhD / postdoc / tenure paper or as TAs if your department is rich.

Also, in Germany, university is free and publicly funded. There is only a small incentive for universities to pass as many students as possible and almost none for the immediate professors and doctoral candidates that do the teaching. Alongside with the public funding comes the implicit understanding that not everyone, for whatever reason, is meant for a college degree and so 40-50% of certainly engineering related students will drop out. No biggie, you are not 150k in debt, just do an apprenticeship.

Talk about the software companies..

I mean, it was pretty clear the music industry would continue in one form or another. There is some form of value add.

But science publishers? These guys haven't made an honest buck in decades now. Their business is entirely due to inertia and regulatory capture. The short to medium term goal of all stakeholders is their entire elimination.

Yet every run still has many thousands of RNG invocations for that particular metric. To be off by a few percent, safe to say that RNG would fail any randomness test.

They probably turned it off after an increase in support requests when people inevitably at one point don't have the "wallet" around. Of course they don't care for other sites support load enough to look at their 50 entries long list of special cases and think "are we doing this wrong".

I don't think that data is likely to be kept, raw or otherwise, on anything other than a very small rolling window, if even that. What the author of this article missed is the boot full of server racks that have the storage and processing abilities to even consider storing the raw data from a multitude of cameras, LIDAR and associated sensor systems.

For development, sure, in test fleets, sure, but production cars won't bother with that.

No one is asking for historical location data, but merely what the car recorded as your input and other driving parameters before, during, after a crash. Where exactly is the privacy interest in that?

You believe this elementary fact in their own rules escaped the FAAs lawyers?

So they admit the offence? This is a guilty plea.

It's a DSP firmware turned into silicon. If you look at for example the VP8 decoder registers for a Rockchip VPU here:

https://patchwork.kernel.org/patch/8118991/

You can see it's quite specific to the primitives the codec needs. If you want general purpose, we now have Vulkan for that.

(And this one is reasonably low-level. On some like the Raspberry Pi, you throw bitstream over the wall to a coprocessor which gives you YUV back)

yocto and buildroot have that market truly locked down because there are a lot of requirements beyond just size.

Something like OpenWRT or buildroot can fit into 8 MiB easy. These people have an actual reason to make small "containers" because flash is a big part of the BoM cost and adds up when you are shipping many thousands.

I understand it is about containers. But no disk space of the world is worth your container app crashing because someone wanted to save a few megabytes by ditching glibc or otherwise just pushing more work into each and every individual container. It's Java Enterprise all over, who cares it's always allocating tens of GiB of RAM, you have to get to the point of buying a lot of it before it makes an hour of an engineers time worthwhile.

What is the obsession with smaller images? If you are running out of disk space before CPU, RAM, IOPS, network, well there is a cheap fix for that.

The first thing, certainly on Android, is to forget the idea that there is one framebuffer ;)

The current interface is DRM (drivers/gpu/drm) and there specifically, atomic modesetting:

https://lwn.net/Articles/653071/