Worst part they're too easy to accidentally check in to source control - and they bring user/workstation dependent settings into the work tree, rather than tuck them away in something like $HOME/. config/appname/local.env
Maybe. How does the application unify different environment variables? Those inherited by the shell, those read from .profile, those set in the process that start the application (be that ./run.sh, a nodejs script, systemd etc...).
Yes, it's a single point of failure by design - but has been pretty stable mostly - with this and a previous attack in June being exceptions.
The identity portal is administered by the department for digital services, but hosted at a commercial provider, Vivicta (formerly TietoEvery, formerly Tieto and Every - Consulting companies from Finland and Norway).
> Det har siden kl. 01 mandag 3. august pågått et tjenestenektangrep (DDoS) som rammer ID-porten som driftes hos Digdirs driftspartner Vivicta.
> Since 0100 hours Monday August 31st there's been an ongoing DDoS attack which affects the ID-Portal which is run/hosted by DepDig's (Department of digital services') service provider Vivicta.
(My translation)
Ed: just realized Vivicta is TietoEvery with a haircut and new shoes:
> People that previously have barely any experience in tech, now being hired in AI startups because they are good bullshitters.
I like the symmetry of people being unable to detect "skill" in people who are great at manipulating language and in LLMs who are also great at manipulating language.
I don't know what the author's native language is, but I assume it's something I'd need machine translation for anyway. Having it in good (if not Nobel prize level great) English is much easier - and will probably be easier to find again via search.
Ansel is what Darktable 4.0 could have been if it didn’t die of feature creep .
Between 2020 and 2023, Darktable has suffered massive code additions of peripheral features, often ill-coded, poorly designed and penalizing usability, performance and maintenance. Too many workarounds failed to fix bugs, but layered new problems on top of legacy code : welcome in maintenance nightmare.
I used Ansel for a while, and I agree that Darktable is suffering from feature creep. Ansel right away had some usability improvements. But the amount of regressions introduced was wild. The anger you can read in the messaging was apparently also employed to cut code, and things got flaky. In the end some features I used stopped working in all releases I tried, and I went back to Darktable. Maybe Ansel is stabilizing now, and I should try again.
Look at some of the docs about what changed, reading things like this:
> This is basically admitting that the design is so terrible that it’s verging on unsable without reading the doc. But wait, what are we doing again ? We are copying pictures. We are copying pictures ? So did you pass your picture-copying exam and got your picture-copying degree ? If you didn’t, you should. Watch out, they might turn this into a quizz in a future version and disable the feature if you fail it.
As a software engineer, I understand this, but the tone also deeply bothers me. I want to use tools made by people who enjoy working on it, not by people working on it out of spite and hate for upstream.
Just make a better product. I don't understand the need to constantly shit on darktable.
reply