Hacker Newsnew | past | comments | ask | show | jobs | submit | cromka's commentslogin

Same here, lost my backup 3 times across some 6 years. Gave up and moved on to Kopia.

Problem is upstream project refuses to address it.

Raise it with Fedora/Red Hat.

> care about their design language

Their interior infotainment design language? What is that "care" you speak of in this regard? Ferrari has been abysmal on that front. Just watch some Roma reviews. That car will loose its value rapidly only because of the outrageous ergonomic.


I am not one for conspiracy theories but I notice a pattern... Did you know Chrome now offers to save your passport and other ID data in their keychain? Why, after so many years, do they now offer to save this information that, if leaked or backdoored, will easily bind login information with their owners?

Looks like GNOME has a problem, all of the below pieces of software will need a new maintainer:

"The folliwing is a short list of important modules where I’m roughly the sole active maintainer:

GtkSourceView – foundation for editors across the GTK eco-system

Text Editor – GNOME’s core text editor

Ptyxis – Default terminal on Fedora, Debian, Ubuntu, RHEL/CentOS/Alma/Rocky and others

libspelling – Necessary bridge between GTK and enchant2 for spellcheck

Sysprof – Whole-systems profiler integrating Linux perf, Mesa, GTK, Pango, GLib, WebKit, Mutter, and other statistics collectors

Builder – GNOME’s flagship IDE

template-glib – Templating and small language runtime for a scriptable GObject Introspection syntax

jsonrpc-glib – Provides JSONRPC communication with language servers

libpeas – Plugin library providing C/C++/Rust, Lua, Python, and JavaScript integration

libdex – Futures, Fibers, and io_uring integration

GOM – Data object binding between GObject and SQLite

Manuals – Documentation reader for our development platform

Foundry – Basically Builder as a command-line program and shared library, used by Manuals and a future Builder (hopefully)

d-spy – Introspect D-Bus connections

libpanel – Provides IDE widgetry for complex GTK/libadwaita applications

libmks – Qemu Mouse-Keyboard-Screen implementation with DMA-BUF integration for GTK"


What's also interesting that some recent studies show eating eggs every day actually is harmful, most likely due to the Omega3 to Omega6 ratio.

So here we go again. First it was cholesterol, which was then rebutted, so people (myself included) started eating eggs every day. And now this. You can't win!


As I understand it there's no good evidence that n3:n6 ratio matters, _as long as both are at adequate levels_. Studies showing the ratio to be of concern achieve a "low n3:n6 ratio" by low n3, rather than high n6.

Eggs are believed to lead to adverse outcomes because of: 1. Their high cholesterol content. 2. Their SFA content.

I'm not sure what you mean by cholesterol being rebutted. The only thing like that I'm really aware of is the dietary guidelines de-prioritising dietary cholesterol, but that decision was made because when making DGs, people want to focus on the biggest levers we can pull. Dietary cholesterol _does_ have a negative impact on health, but it also has a threshold effect at around 400mg/d after which it has considerably less impact (unless you're part of the ~20% of the population who are "cholesterol hyper responders").

Because most people eating a SAD are already at that threshold, the decision was made to take dietary cholesterol off the headline recommendations, but if you read the details in the DGs and the meta-analyses that drive them, they still point to lowering dietary cholesterol as a smart health move.

I frequently see this change portrayed as "no longer recommending the lowering of dietary cholesterol" or "admitting they were wrong about dietary cholesterol", but that's not really what happened.


Thanks for the input, I appreciate it.

This is what I was referring to regarding the eggs themselves: https://youtu.be/w_cKTN1l7r4?t=1516


Welcome, always nice to talk about this stuff - nutrition science is a very interesting field because it's such a slippery subject to get right. Every day's a school day and I'm never as right as I think I am!

That take on eggs sounds about right regarding numbers per day and risk. If you look at the ACM risk associated with various food groups in figure 2 from this paper (https://ars.els-cdn.com/content/image/1-s2.0-S00029165220492...) then you can see the ACM risk hitting significance at around 55g/day, which is about 1 large egg.

Dave Asprey is such a wild dude. Who is eating rice for protein? Bizarre straw man!


Well, don’t eat the same things every day.

Like bread? Or olive oil? Or Avocado? Or nuts?


This is very obvious.

What part of your document editor needs to be backed by a relational database?

Why use an MVT system if you don't need the Model part of it?


https://github.com/suitenumerique/docs/blob/main/src/backend...

I see, in your broad and experienced mind, document editors don't have users, permissions, and the whole document management itself, comments on lines/threads, reactions on comments

Seriously, theyre all as cookie cutter perfect usecase for Django as you can get, but I guess you haven't actually thought about the domain and just wanted to take a dumb on other devs with intern-to-junior level insights


You don't necessarily need that to get these things...

Obviously, you don't need the model abstraction for any software, ever. It is just more or less suited for a domain.

And in this case, as would be obvious from thinking about it, the only part it's not suited for is the live syncing of the text edit on the frontend, which is one one small part of the whole.


Storing the text documents themselves in a relational database is itself a terrible idea.

It's not a bad idea, generally. it depends on the implementation. If you're updating it multiple times per second, then yes, it's a bad idea.

Now go check if they're doing it or you're just suggesting from the dunning kruger symptom.


*Intel Foundry

You license them, not source from the US.

It seems like that was true for the Volvo-manufactured engines in the currently operating versions, but the new versions that are being sold now (currently in the news for a deal with Colombia) use a new US-manufactured model.

Oh, didn't know that. It changes s few things indeed.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: