hju22_-3

Could you elaborate on the reasons for considering moving away from NixOS? :) I like it in principle, but my main issue is that if you filter out the package activity from the repository, the actual core contribution is low. At least in comparison, and if you filter out the ones with a few one off commits, the actual primary contributors are just a handful so to speak. I worry that, since there are so few who truly understands the internals, if something happens to them, things may go more awry than expected ... or something like that. It's been a few years since I last checked the project. There's also that, at the time, pull requests were growing much faster than being closed or merged, not sure if that's still the case? So very curious to hear. :)

Yes. Because you say that as if Linux doesn't require the same or longer the second you dare use it as an average user and want to change the defaults. Or just use it in general.

> The handful of popular DEs [0] are going to be much more polished and functional for like 99% of tasks, and nonexistent [1] for the other 1%.

Lol! You should try being a comedian.

You make a very compelling argument. I've been thinking of at least trying it out before, but have been leaning towards it more and more over the years. A couple of questions though, if I could bother you with them?

How is remoting performance e.g. via VNC/RDP or particularly via Moonlight+Sunshine (intended for gaming and such)?

And how programmable is the configuration of Qubes? I like the idea of NixOS for example, but given how comparatively little activity there is in the actual nix rather than the packages, and across so few developers, I worry what would happen if someone got hit by a bus or something. But I still like programmatically configuring computers over manual monkey patches, because I have the memory of a gold fish. :p

It does: https://fossil-scm.org/home/doc/tip/www/shunning.wiki.

Those two pipe dreams sound really cool! Do you have a website or something to lurk you via if you eventuality get around to those? I find it difficult to keep up, as it were, using form histories and other social media platforms.

If you are going to quote a dictionary, please first ensure you are quoting it properly and without misrepresenting the contents and b) that in cases wherein a definition has multiple potential meanings it lists the different uses from common to uncommon.

As per the actual 1828 Noah Webster's dictionary, which you can find here https://archive.org/details/noah-websters-1828-dictionary-el..., on page 7828, the definition of "Milk" is:

MILK, n. 1. A white fluid or liquor, secreted by certain glands in female animals, and drawn from the breasts for the nourishment of their young.NWAD MILK.2 2. The white juice of certain plants.NWAD MILK.3 3. Emulsion made by bruising seeds.NWAD MILK.4

And, just in case the commonality of milk being milk from a cow, see also the other shorthand definitions noted on pages 987 and 988 of the table of contents.

MILKEN, a. Consisting of milk. [Not used.] MILKER, n. One that milks. MILK-FEVER, n. A fever which accompanies the first flowing of milk in females after childbirth. MILK-HEDGE, n. A shrub growing on the Coromandel coast, containing a milky juice. MILKINESS, n. Qualities like those of milk; softness. MILK-LIVERED, a. Cowardly; timorous. MILKMAID, n. A woman that milks or is employed in the dairy. MILKMAN, n. A man that sells milk or carries milk to market. MILKPAIL, n. A pail which receives the milk drawn from cows. MILKPAN, n. A pan in which milk is set. MILKPORRIDGE, MILKPOTTAGE, n. A species of food composed of milk or milk and water, boiled with meal or flour. MILKSCORE, n. An account of milk sold or purchased in small quantities, scored or marked. MILKSOP, n. A soft, effeminate, feeble-minded man. MILK-THISTLE, n. A plant of the genus Carduus. MILKTOOTH, n. The fore tooth of a foal, which is cast within two or three years. MILK-TREFOIL, n. A plant, the cytisus. MILK-VETCH, n. A plant of the genus Astragalus. MILK-WORT, n. A plant of the genus Euphorbia; spurge. MILK-WEED, n. A plant, the Asclepias Syriaca. MILKWHITE, a. White as milk. MILKWOMAN, n. A woman that sells milk. MILKY, a. Made of milk.

Specifically note the commonality of milk dash thing when it refers to plants. Not that it's particularly relevant, aside from the actual commonly used definition of milk already provides an example of milk being commonly understood as milk. As an additional example, look to the definition of mentioning almond milk on page 2134. Specifically note that it says milk of almonds, and not just milk.

AMYGDALATE, a. [L. amygdalus, an almond.] Made of almonds. AMYGDALATE, n. An emulsion made of almonds; milk of almonds.

As you can see, I care way to much about milk.

To the letter of the word? Perhaps. To the spirit? Hmm.

Strange then that you reject critique elsewhere. Accessibility is not just a checkbox, it's to consider and test the actual use of it.

Or perhaps you shouldn't get defensive of critique on your "design vision" such that you just write them off entirely like it has no value? You might like driving in the opposite lane, but rules say otherwise, and best practice can be likened to it because it's been decided on or landed that way due to multiple people being involved in the process of deciding those rules. Just as with best practices. There are best practices in design too, you know.

Anyhow. Depending on the viewport your panels do get in the way, it's 1/3 of the screen on mine for example. If you're going to hide the panels, hide them properly. That you show them at the top and bottom automatically, fine, though they could be smaller on mobile. However, you could at least consider the UX of using it on smaller viewports. If I want to scroll up a little bit while reading, they pop into view, making me have to scroll down to hide them again. Meaning I have to scroll higher up than intended, so I have enough space to scroll down. Another common user pattern is to slowly continually scroll too, and a tiny jitter upwards causes them to reappear, but requires comparatively massive downwards scrolling to hide again. Your site is not the only one to do this, but it's just bad design. Vision or no, and it's no justification, just an excuse. And then, what about left handed people? It's easier to accidentally click into the message box field, which opens up the keyboard and you'll have to close it. Pair this with it taking up the majority of thumb space for scrolling, given its size, and, well. Is it unreasonable for people to tell you it's aggravating? No. And this is without considering, and doing the minimum for, people who may suffer with controlling devices for whatever reason. Not by "bending over backwards" as some would have it, but at least taking such into consideration.

It's fine to have a vision of your intended or wanted design, but it's also important to be willing to reflect on how your vision may not necessarily be good design, depending on how one judges it, rather than just deflecting critique.

> There's much to criticize about the dev, but there's really no way to make it significantly easier.

Not banning people that want to buy a flashing kit instead of making one would be a start.

I for one would learn nothing, and wanting privacy shouldn't require an arbitrary skill when unnecessary like in this case. Not even mentioning that buying the parts is prohibitively expensive compared to some finished kits I've seen.

That sounds fascinating. Do you have public facing configuration you would be willing to share? :)

As a small note against Syncthing, despite how much praise it gets, it's conflict resolution sucks. Enough so that it is easier to nuke it and set it up again instead. If you never have conflicts, it works fine though, but I find that rather unrealistic.

Number 2 is so unusual I would immediately flag the company as a scam. How is asking for money a reasonable approach? There are alternative ways, easier too depending on country, and all you'd be doing is selecting for desperation while also spreading bad rumors from all the people who nope out when they see such malpractice.

_Try_ to? Are you serious? We're not taking ambiguity due to phrasing, we're talking straight up not mentioning it on either the front page, on the show all page or even on the page the components button takes you to. Not even on this forum thread. There's barely any text on the front page to change and there are even multiple places you can mention React. You could mention it in the title, e.g. "Open source _React_ UI kit for modern document apps" or you could add it to the second paragraph, e.g. "React components ready to drop into user-facing flows, agents, or internal tools." Not to mention the components page. And given what you use to make the website, how does it take this long to update something this trivial when you are going out of your way to promote it, replying to comments and your other services by proxy?

Also, add either user interactive loading of components or lazy load the demos, the amount of demos murder performance on phones.

You can use SSH keys and GitHub deploy keys to approximate this. Can't speak for the security of it, but I have never set up GitHub with access to every repo. Not sure if there exists approximate functionality in other git forges though.

> Everything just works and it has for some years now.

Strange then, that so many people and particularly those who haven't spent years or decades fighting their OS or desktop environment, seem to disagree.

Every time a linux user says "everything just works" there's a massive gotcha. Remove the terminal and try to use a linux system, setting everything up, while properly roleplaying those who haven't spent years to get used to linux's many weird choices and you'll perhaps understand.

I could imagine a person having or doing all of these over time, people do have many interests, but a cursory glance does give an impression of AI. The Instagram account uses a lot of it at least, and the top domain was likely made in conjunction with AI, given the style.

Kind of fascinating, though it could still be a person doing this using AI as opposed to an entirely generated persona. Thanks for bringing it up.

Where do you see that SteamOS Holo is GPL3? A package is not required to be GPL, and most of SteamOS is a customized arch installation, there's no guarantee that SteamOS itself is GPL. And which repo are you talking about, I don't see it on their gitlab for SteamOS Holo?

Ah, I see. Thanks for checking. I'm considering doing a similar run at home, so was curious if there were any options that thin. 0.9mm should be plenty to work with. :)

What kind of fiber cables? If you have a link, I'd appreciate it. I can only find ones at 0.5mm.

Err, no, it's actually really easy. Just give them a choice in the matter first. You do realize you're arguing for toying with people's futures based merely on effectively unproven methods because you just feel like doing it? Futures that have inherent value because the people being toyed with are inherently valuable too. But no, it's totally fine to not be held accountable for your actions. I mean, what's the real damage done here? Think about how expensive it'd be, or, or, how long it'd take if not! That surely justifies just going to town on people, right? :/

That's essentially what you're arguing. Perhaps not what you intended, but it is what it becomes given the context, and more importantly, the people involved that you disregard so callously.

If it's so darned expensive to do, have you considered that you have the free will and intellectual sophistication required to just . . . not do it? If it'd be so expensive to recuperate a group of people, either your methods have too high a probability of requiring it or your method is just perhaps not ready yet if the potential end result are that disastrously bad. Either way, it points towards going back to the drawing board instead of to town.

But if it's oh so difficult to get these studies done, you know what you can do? You can do it over longer periods of time, just like you bemoan, because that larger time scale will stop you from ruining other people for your own curiosity of will x work in y. You could give people the choice to join the study, you could have smaller cohorts every time and refine the process as you go, you could keep each cohort limited to a year or two to avoid long-term damage, and you could test in different age ranges to get more data.

The list goes on and on and on. Almost like studies on people require larger caution than just testing to see what works without any precautions and going from there. When learning about the scientific method, the idea that people are, you know, people and not test subjects is pushed constantly. Because certain people sadly need that reinforced to avoid being callous researchers. It's oh so easy to forget the numbers you toy with are real lives with real value regardless of what is done with those lives.

We trade immediate results and dubiously better efficiency for larger time spans exactly so that we can ensure the people in them remain protected. Giving people choice in the matter, and letting guardians weigh the value proposition (like other studies have done successfully) by giving them the prerequisite information required to make those decisions, allows for a higher likelyhood of avoiding disasterous effects on those very same people. It's not "generational inconvenience" when lives are affected for multitudes of years; it's callous impatience. It's not "no change ever," is respect for the people involved in attempting those changes and respect for the potential ramifications of those changes. It's borderline evil to disregard people because you, and I do mean you here, don't have the patience to ensure people's safety because, oh no, it'll take a while, or cost a lot if you're held accountable.

Rather, it's okay that things take time, it's wanted that we don't make haste. Because haste makes waste. Because we don't need immediate results. Because we're not working with machines, we're working with the single most valuable thing we have on this earth; a human life. Have some compassion for those people, and you'll find that change doesn't take so long after all.

The notice about having "access" to the backgrounds is sticky, and takes up one third of the screen on mobile with no way to remove it . . . Why?

Remember IcedTea Web? Oh boy, I still have environments that use it.

I must concur, very tasteful.

Oh, neat. Didn't expect to see IronCalc here for some reason, have been considering it for a side-project. Thanks for the hard work. :)

Yes, because it isn't. What version they pump out has nothing to do with viability. It still lacks much of the feature set and functionally of Photoshop, enough so that it's just not a valid comparison, let alone a valid alternative. Like, I've seen people comparing Krita as the better alternative to GIMP, which isn't even designed to fill the same need. But the fact that those comparisons have even occurred should tell you enough about the state of GIMP.

Wat.

Maybe read up on what having an "inner voice" or not actually does first? Before making, frankly, weird and unfounded takes on the subject.

Then why make a product whose purpose it is to convey written technical information to users of that language, if it's also a language that you need assistance in to communicate properly with?

I hate how things are just silent removed. Thanks for taking up the pitchfork, looking forward to your solution's progress.

I tested the Japanese app, in in a bit of a hurry, but here are things I noticed.

- 1 time when matching pairs, two different sounds played. Not the automated and presumably yours, but two different sounding sounds. E and another one I think it was.

- One run the male voice played when I clicked on the Japanese symbols to the left when matching pairs. All the other times it played together with the automated voice.

- The error log empties itself despite not leaving the current run, so you can't see what you did wrong. Not sure if it's page specific, but if so it ties into this next point.

- When matching one symbol to four different sounds, the page transition is too abrupt. This is also a thing on the other pages. I'd say better UX here is to give feedback that you did it right, and let the user choose to continue. A score too, if you'd like to "gamify" it.

- The options for modifying runs doesn't work. I was interested in seeing the other tasks, but even when only enabling the task or tasks I wanted, I kept only getting match the pairs and match the symbol to the sound.