It makes so many things far easier, having a temporal relation for every record and saves a lot of headaches that would otherwise usually be dealt with on the application level.
1,000 karma · joined April 29, 2015
It makes so many things far easier, having a temporal relation for every record and saves a lot of headaches that would otherwise usually be dealt with on the application level.
Wasn't it just the other way round at Volkswagen? Herbert Diess steered the heavy ship Volkswagen extremely aggressive towards electrification like no other company of of this size with clearly visible results.
He was ousted due to major issues (delays, staffing, quality) with the software department (CARIAD) that is building a completely new software stack to be used for new cars of all Volkswagen brands and replaced with an e-fuel loving petrolhead, the former Porsche CEO Oliver Blume.
Well, that's Mark Rober before bis YouTube fame.
This doesn't carry the risk of tainting the new session with the context of the initiating shell (pwd, env, ...) and doesn't only feel like a full login, but actually provides everything that's part of a login session (systemd and DBus user-sessions, shared session context with other shells of the same user, etc).
The oldest (family-held) one in Germany is "The Coatinc Company":
https://de.wikipedia.org/wiki/The_Coatinc_Company
The oldest non-family owned one is "Staffelter Hof", in operation since 862:
Builds cars to cement the status quo of the most inefficient and destructive mean of transport there is.
Hypes up futuristic potential, yet unrealistic long-distance transport to derail high-speed rail investments and projects.
Works on building his vision of space exploration which will become a huge environmental and technical liability for future generations when following his envisioned scale and goals.
"Comments like this do not read as genuine concern. It is designed to cast doubt on a project before it is even close to release, and the kinds of people liking this are evidence of it being passive aggressive FUD posing as concern. COSMIC will absolutely support a11y on release!"
https://twitter.com/jeremy_soller/status/1576682150836830208
The same goes for the canopies, where a whole other ecosystem lives in it's own, with some species (animals and plants alike) never touching the ground of the forest for their whole existence.
Forest are an incredible carbon sink and removing old growth will dry up the soil and cause outgassing of the captured carbon within a quite short period of time, cause weather induced soil erosion and destroy the former water retention capabilities, leading to more floodings.
The database contains an incredible level of detail which can be used in completely different contexts and I'd say what's rendered is roughly only 1/10th of the data
Since all builds have an mtime of 0 as timestamps are the biggest source of reproducibility issues [2], QML loads outdated cache objects which will then load invalid bytecode at runtime and therefore causing a crash.
Our initial plan was to utilize a hash of the binary [3] which should be IMHO the most straightforward, unlikely to break and future-proof way to solve the problem. The currently suggested implementation's performance could most likely be improved by generating the hash once on startup instead of every time when a QML resource is loaded, but I believe since it's already cached in memory, hashing is not that expensive, binary sizes are usually relatively small and resource loading (of embedded ones) doesn't happen that often, it should be already reasonably fast (real performance test haven't been done yet).
The big challenge will be upstreaming it, once we've proven it to properly work. The current approach has been apparently rejected [4] and was declared to be a downstream issue, which I personally don't agree with, since sooner or later reproducible builds will become the norm and therefore will affect everyone. Current ideas to work around it require individual solutions per distribution/ISV, as this would mean they'd have to come up with domain specific criteria for cache invalidation (as the store path/derivation hash on NixOS) and to maintain a downstream patch for this solution and furthermore wouldn't work for local build processes (e.g. from within an IDE).
Lesson of the day: never use mtimes, they'll bite you in the ass sooner or later!
[1] https://github.com/NixOS/nixpkgs/issues/177720
[2] https://reproducible-builds.org/docs/timestamps/
[3] https://github.com/qt/qtdeclarative/commit/5106afcd76e377a6b...
[4] https://github.com/NixOS/nixpkgs/issues/177720#issuecomment-...
Smells like some weird scroll-jacking implementation or so...
A recommended alternative is Mangrove [1] which allows anonymous cryptographically verified reviews, but I have neither had a closer look yet nor given it a try so far.
https://www.baden-wuerttemberg.de/de/service/presse/pressemi... (German)
[1] https://bugwarrior.readthedocs.io/en/latest/
[2] https://bugwarrior.readthedocs.io/en/latest/services.html
Due to the fact that it is based on (relatively frequently updated) OpenStreetMap data, its data density and depth is really really good and allows for quite obscure POI searches like ping pong tables, barbecue/fire pits, geographical features like valleys, etc.
My employer's org deploys a Microsoft SSO AddOn which re-uses the OS-level identity to auto-login to Microsoft/Office365/Azure and causes me quite some headaches when dealing with my customers' logins, which are usually in separate containers.
I switched to FF profiles for those use-cases for now, but it's far from the container experience in terms of usability and integration.