HNHacker News
TopNewBestAskShowJobs

arghwhat

9,034 karma · joined January 12, 2017

no.
submissionscomments
arghwhat··on IKEA ditches Zigbee for Thread going all in on Matter smart homes
A border router does not provide internet connectivity.

A border router is used to bridge e.g. Thread networks onto a regular IP network so that your non-Thread smartphone can talk to it, and so Matter devices on different network types can link up directly if you want a Thread switch to control a WiFi light for example.

Matter devices use link-local IPv6 addresses and cannot route packets onto the internet even if they wanted to.

arghwhat··on IKEA ditches Zigbee for Thread going all in on Matter smart homes
They both enforce certification for products, just that one is enforced through trademark and copyright law and the other cryptography.

In both cases can ignore certifications and have a working product. I run uncertified, open source Matter things myself.

It's not like HDCP in that HDCP is a technology no end-user wants, but something certain content creators want.

arghwhat··on IKEA ditches Zigbee for Thread going all in on Matter smart homes
To be clear, this is the same organization that developed Zigbee, which requires paid certification - without, you're not allowed to say the product supports Zigbee or to use the Zigbee logo.

You can connect devices without this, it just shows a warning during commissioning that the device is not certified. No impact whatsoever.

arghwhat··on IKEA ditches Zigbee for Thread going all in on Matter smart homes
Matter doesn't need internet access, it's an entirely local protocol even when you integrate to other vendor ecosystems.

Now, something like Google Home might decide to go online to talk to a Google Home Hub device, which is where Google wants to initiate all Matter communication from, but that's a Google thing, not a Matter thing.

arghwhat··on AV1@Scale: Film Grain Synthesis, The Awakening
Anything with a pattern is by definition not noise, and the comment was that noise had signal. If you remove all noise, no signal or pattern is lost by definition.

However, the issue is that lossy compression removes various types of minute detail, smoothing surfaces to reduce the amount of data that has to be stored, be it noise "grain" or skin pores, according to compression settings. Storing the original noise as it was would basically make any compression impossible.

arghwhat··on AV1@Scale: Film Grain Synthesis, The Awakening
Definitely, but that's a result of compressing (with any algorithm) past a bitrate that would allow detail to be retained with high frequency details including noise being the first to go, not the result of noise having signal as was stated and more importantly unrelated to film grain synthesis which is about adding something new on the output side.
arghwhat··on AV1@Scale: Film Grain Synthesis, The Awakening
The noise does not contain a signal, does not dance over it, and is not detail. It is purely random fluctuations that are added to a signal.

If you have a few static frames and average them, you improve SNR by retaining the unchanged signal and having the purely random noise cancel itself out. Retaining noise itself is not useful.

I suspect the effect you might be seeing is either just an aesthetic preference for the original grain behavior, or that you are comparing low bandwidth content with heavy compression artifacts like smoothing/low pass filtering (not storing fine detail saves significant bandwidth) to high bandwidth versions that maintain full detail, entirely unrelated to the grain overlaid on top.

arghwhat··on Boeing uses potatoes to test wi-fi (2012)
At that point you probably have direct satellite-to-phone 7g connectivity...
arghwhat··on Boeing uses potatoes to test wi-fi (2012)
The tricky part isn't getting signal strength in the cabin, it's managing a cabin full of devices trying to talk using a technology that only allows one radio to talk at any given time.

You need many very low power base stations at spaced out channels to make this work. Nowadays WiFi 7 provides some nice anti-congestion and channel optimization features as well, but back then, one slow device was all it took to render wifi useless.

arghwhat··on SpaceX Starship 36 Anomaly
> Whatever you build, it would land on the moon perhaps once, and never again.

But it would also never land on Mars, so it would be a waste to build it for that. Build it for what it will actually spend its life doing.

Not saying SpaceX won't go to Mars, but if/when they do it will likely be several rocket generations later and possibly with specialized rockets, with a significant portion of it being one-time-use as you ain't returning.

arghwhat··on KiCad and Wayland Support
> That's all well and fine, no one is forcing you to build or use software this way. But there are domains where this is the predominant UX design and it's proven to be robust for decades.

Nothing about it is robust, it just exists. It has been around for decades, sure, but it also has not been common or popular for at least a decade or two now. It primarily exists in old applications still rocking their original, unchanged UI.

I have sympathy for existing applications, but I strongly believe it would be entirely inappropriate for a new application to be written with such UI - it was never a good idea, nor did it ever work well. It was just an idea that we have moved on from.

> It seems crazy to me that there's so much feedback

Not specific ot Wayland, but there is always absurd amounts of "feedback" to any high profile projects, which unfortunately means that most of it is useless noise, hit-and-run tantrums over the mildest inconvenience, and "ideas for solutions" by people who spent less than 5 minutes trying to understand the problem. This in turn means that it can sometimes be harder than it should be for good feedback to make it through.

arghwhat··on KiCad and Wayland Support
> Where did your [...] go?

That statement is both still there in its entirely unchanged form, and still entirely true - quoting the comment as it appears on my screen right now, long after any edit window closed:

> but it's easy for others to read this and conflate "problems with application's Wayland support" as "problems with Wayland"

arghwhat··on From SDR to 'Fake HDR': Mario Kart World on Switch 2
> It should use its additional color palette available in HDR to look better, and the additional brightness to make make effects pop as you describe.

It could, but that's different than shouldn't. There could be good reasons for it, such as not wanting the primary gameplay to lie outside a color palette available to people playing on their TV in sRGB or in the common complete shit HDR modes that lie about their capabilities.

It would be neat if more was used, but nothing about being HDR means that you should, or that it's even a good idea, to rely on the maximum capabilities.

> I haven’t turned it back to SDR mode but I’m legitimately considering it. Because I suspect the game looks better that way.

To be honest, without a TV with proper HDR, SDR mode will often look much better. The problem is that TVs are often quite awful when it comes to color volume, specular lighting and calibration. The SDR mode is often very untrue to the content, but stretches things within the TV capabilities to make it bright and vivid to look nice. The HDR mode on the other hand has to give up the charade, and in particular SDR tonemapped content, which if the TV didn't lie would have looked identical to SDR mode, looks really awful.

A favorite of mine is to switch Apple TV's between SDR and (tone-mapped) HDR mode and see how different the main menu and YouTube app looks. I have yet to find a TV where UI doesn't look muted and bland in HDR.

arghwhat··on KiCad and Wayland Support
What in the world are you on about?

Editing a comment for clarification is not bad faith. It avoids misunderstanding and helps those reading it, even if some have already read an earlier version of it. It makes it sound as if you consider comments a battle, with changes being cheating or foul play, which... Is just wrong.

Nothing about my comment was bad faith or disengenious, nor did I say that I agreed with KiCad developers. I just said that, and will stand by, that it is erroneous to read their claims of e.g. performance issues when using their wayland platform code as being an issue with Wayland. If you write new code that is slow, you don't start by blaming your CPU, then your compiler, then your OS, and Wayland is generally known to perform better than X11 by virtue of being designed by people also working on the GPU driver stack.

arghwhat··on KiCad and Wayland Support
The Wayland developers also include major toolkit authors, and a bunch of them contribute far and wide.

But, to most users, switching to Wayland just means that everything got smoother, and easier ot use, with everything working. Even X11 applications will work just fine. Even if Wayland has an omission that is greatly upsetting to an individual, the X11 mode of the app will usually work exactly like it always have without leaving the Wayland server. Anyone using extremes like "unusable" (or "perfect"!) is not providing meaningful information and can safely be ignored.

arghwhat··on KiCad and Wayland Support
> Reopen window, and reposition it where the user last placed it

Under Wayland, this is not the responsibility of the application, but the responsibility of the display server. You tag the window using the new toplevel tag protocol, and the display server will remember things like user position, size, always-on-top settings, and similar.

> Normally that requires windows knowing where they are in absolute coordinate space on the display. From what it sounds like, that's not possible in wayland?

It is neither possible to know where a window is nor to place it. That is purely up to the server, and under Wayland the goal is to tell the display server what it needs to know to create the UX the user would want - with a recurring focus on respecting user preference over having applications enforce the developer's preference.

But, it's important to note why it's made the display server's reponsibility: because the alternative was already broken under X11. Take a multi-window app that wants to open an old-fashioned "tool" menu. The application wants to place it to the left of the main window, which seems simple - until you realize it's not.

If the window opens fullscreen, the window would end up off-screen or on a different screen - okay, so we check if we're fullscreen and overlap the window instead. If the window opens near a screen edge or on a small screen, it might be too close to the edge - okay, so we also check if the left side of the main window is near a screen edge. Simple enough so far.

But then you run a tiling window manager (i3, awesomewm) and all new normal windows become tiles that pop up after predetermined rules, and random floating windows will be an error. Or you run PaperWM or Niri where the screen has an infinite horizontal size and so checking if a window is near an edge is always incorrect as the edge moves as needed. Or you run a VR window manager (we have those now!) so windows have not just X and Y, but also Z, pan, tilt and roll that the application does not know how to manage. Or you have a display server running on one of the OLED monitors that fold in and out like a recent CES lenovo laptop. Or...

Applications trying to micromanage their windows are effectively re-implementing a window manager that is always going to be making very heavy and wrong assumptions about the current window management paradigm and end-user preference. Instead of porting already broken duct-tape from X11, Wayland works on protocols that describe the intent properly - for example, by describing that an auxillary window is associated with the parent and should default to a placement to the left of it, rather than manually moving it.

(My personal opinion, unrelated to any project, is that traditional multi-window is a very fragile legacy design paradigm that doesn't make any sense, and that keeping operations to a main window and only using windows for isolated tasks - e.g., different workspace, file selectors, etc. - gives much better and more stable UX. Splash screens also no longer belong in a world of multi-tasking - just open the main window immediately, and if the app needs additional time to prepare, show the "splash" in the main window and transition later. That way, the user can multi-task and place the window instead of being interrupted by an application thinking they should cover up the center of the screen and randomly glitch windows in an out of existence.)

</walloftext>

arghwhat··on KiCad and Wayland Support
1. Display servers are highly security sensitive and cannot be shipped in good faith unless they are well maintained. The only high-profile X server still around, xorg, is entirely unmaintained outside its Xwayland support, and no one is willing to step up.

Volunteers own their own life and time within it and have no obligation to pick up arbitrary projects and tasks. The primary way to make people do something no one volunteers for is to hire them and pay them for it, but no one is interested in that either.

(One person did famously, and very vocally, volunteer and do a lot of work, but unfortunately almost all of it had to be reverted recently after it was found to break everything.)

2. Wayland and X does, for and enduser, coexist through Xwayland. You just no longer run a "native" X11 display server that controls hardware directly. Most Wayland servers afford Xwayland some slight additional controls for just the X11 windows, allowing applications to work seamlessly, so everything is fine.

And no, the "most" qualifier is no issue at all as applications relying on such control also only worked with some X11 window managers.

arghwhat··on KiCad and Wayland Support
> Depends on what you're calling properties of the window, wayland does of course have a number of things like that but not all of them are the same as X11 used to be.

Well, technically Wayland has no such thing as properties. It only has requests and events on objects, and no protocol behave like an arbitrary key value store the same way X11 atoms do.

You can't ask Wayland how big your window is or should be for example, you decide how big it is right now when you submit a graphics buffer in a requests, and the Wayland server will tell you in an event if it would like it to be a different size (say, because someone dragged a server side decoration or because the window became fullscreen).

A key difference between Wayland and X11 is that Wayland is very explicit in how functionality is defined and added.

arghwhat··on KiCad and Wayland Support
A window (surface in Wayland speak) is just an object in the Wayland protocol, and a Wayland client can have as many as it likes - it will just never see anything outside its windows. If these are normal windows (top-levels), it won't even know where the windows are relative to each other - it just receives (surface-relative) input when focused, none when not.

Note that Wayland objects including surfaces does not have "properties", just requests and events. You create a surface object, create an xdg_toplevel role object to make it into a moral window, and send requests to attach and commit buffers with content, to request fullscreen, etc. In turn you get events if the display server would like you to change state, when it's a good time to start painting, etc.

It's not like X11 where a window is an arbitrary key value store that you write stuff to and cross your fingers in order to get particular behaviors.

arghwhat··on KiCad and Wayland Support
That's why there was a protocol released to do just that, by having the client set a unique tag when it creates its windows so the display server can recognize when a window has come back.

Wayland in general is all about leaving stuff up to the display server, with the display server representing the current user and their current window management preferences.

arghwhat··on KiCad and Wayland Support
No, having bugs in home-grown platform specific code is not at all related to whether or not the platform is "weird".

Platform integrations are a lot of code, which you might have bugs in, and why people tend to use toolkits that do the work and abstract it away for you. Even if platforms look like they're providing similar high-level features, they will look nothing alike underneath. If you roll it yourself and have bugs in your code, that's fine but not the platforms fault.

arghwhat··on KiCad and Wayland Support
Again, not how Wayland protocol maturity works. All released protocols are versioned, and do not break existing clients. Servers offer a maximum version number for their protocols, and clients can request any version up until that maximum version. If they request an older version, the server will behave in accordance to the older specification.

A staging protocol may end up being replaced and slowly deprecated, or have more breaking changes in new versions than you would find in a stable protocol, but a client using a particular protocol can rest assured that a server offering the protocol will adhere to the same version of the protocol contract the application was written against.

arghwhat··on KiCad and Wayland Support
It's actually a lot more difficult than that.

Working with existing applications as is requires a ditect mapping, and any restrictions or asynchronous prompts would break any existing assumptions in platform agnostic code, so it wouldn't solve things completely.

If you make something possible to do something with a permission or configuration, app developers just tell users to accept or configure to not ask, and then we're worse off than if there was no permission at all: the security is bypassed and only the inconvenience remains.

It takes a surprising amount of thought and work to do this in any meaningful way, and it cannot be done in a way that isn't somewhat disruptive.

arghwhat··on KiCad and Wayland Support
> Window restoration was not recently released, it was put in as experimental and it'll probably be another 5 years before it's available on stable distros as a non-experimental flag protocol.

That's not how Wayland protocol maturity works. Protocols of interest are picked up immediately and graduate to stable after wide adoption. The naming was also changed to "staging" instead of "unstable" to clarify this.

(Case in point, linux-dmabuf was only recently stabilized, and many protocols in mainstream use are not "stable").

> The issues have been looked into and they are purely Wayland bugs.

Bugs reproducible only with their Wayland platform code ≠ Bugs in Wayland.

> If things work on Windows, macOS and X11 without any platform specific ifdefs, the problem is Wayland ;)

Not at all how things work, no. :)

arghwhat··on KiCad and Wayland Support
> So we have two opposite claims. One from the developers of kicad in this write-up with examples and one from you above.

You have the organizations maintaining entire Linux distributions with countless applications they support giving their vote of confidence based on their experiences.

You have the organizations backing and developing Wayland.

You have all the developers of Xorg ditching it and working on Wayland instead (the person vocally claiming to pick up the slack recently had almost all their work reverted when it was found to have been completely broken).

That's a lot of people voting with their time (and in some cases, money) on Wayland and its capabilities. So no it's not my claim that Wayland works vs. KiCad devs, it's the claim of everyone that actually have skin in the display server game.

(They will also agree that some features are missing, but things like focus, graphical glitches and performance are not Wayland issues, just application bugs.)

arghwhat··on KiCad and Wayland Support
The historic reason is that all inputs and window manager state outside your very own window is kept secret, and "stealing" input strictly disallowed.

The idea is to avoid clickjacking, eavesdropping, phishing-esque windows, you name it, all which only works when an application has freedom to find other windows, place itself and steal focus and input. Even just stealing a cursor at a bad time might lead an in-progress password input to end up somewhere unintended.

It was a good intention, and it's hard to figure out where to draw the line between convenience and capability and secure design. It's absolutely impossible to ask, as everyone will demand everything, claiming even the smallest feature is the foundation of all modern computing.

Some of these things are now coming in ways that still aim to keep explicit behavior and decent control, but enable the needed usecases. Cursor warp, session restoration, picture-in-picture, etc.

arghwhat··on KiCad and Wayland Support
A significant portion of the problems listed, e.g. performance, "unpredictable focus", glitches, freezes, etc., will generally be purely KiCad bugs.

Others are feature requests that there were recently released protocols for e.g. window restoration and cursor warping, but with adoption needing to pick up.

Nothing negative towards KiCad team as they and the community sort things out, but it's easy for others to read this and conflate "problems with application's Wayland support" as "problems with Wayland". It's a new platform for them, and support for a new platform will always have some growing pains.

Xwayland is also under continued development, and these distribution are not dropping X11 support through Xwayland, just native X11 sessions.

arghwhat··on Major sugar substitute found to impair brain blood vessel cell function
> I am not aware of any evidence in favor of this idea. It seems more likely that the only purpose of the bitter taste is to make you spit the food before swallowing it.

That would not explain why the stomach delays opening in response to bitter in the mouth, similar to preparing for protein digestion on glutamate detection.

But of course, we don't exactly have a spec sheet to work with here, so all we can do is theorize on why a particular trait might have evolved...

arghwhat··on Major sugar substitute found to impair brain blood vessel cell function
> Eating food in order to have energy to do things is not "disturbing"

It most certainly is. It disrupts several processes, requires significant energy and resource expenditure, spikes various hormones that may or may not be able to develop intolerances. Significant impact to the gut, pancreas, brain (e.g., reward systems).

Not all of the effects are as high profile as full on diabetes, but its most certainly very disruptive.

Even the most healthy things are disruptive and stressful. Exercise is also incredibly disruptive, causing significant continuous injury and a panic-like reaction trying to keep your body from falling apart at the seams den eject your heart through the nearest chest opening.

Living is the act of balancing on a knife's edge with every force in nature trying to knock you over. You live not because of nature, but in spite of it.

arghwhat··on Major sugar substitute found to impair brain blood vessel cell function
> it seems impossible for any artificial sweetener to be completely safe, unless it is consumed only sporadically, not regularly.

This also holds for non-artificial sweetener, or in fact any substance entering our body.

Disturbing a process expecting a large influx of carbohydrates vs. disturbing the body with an actual high influx of carbohydrates, disturbing the body by neither consuming nor triggering carbohydrate processes, ...

Drinking bitter fluids - say, coffee - trigger early toxicity warnings that prepare your body for emergency oral bowel evacuation, as "bitter" is the taste of various substances evolution associated with food poisoning. What other mechanisms might that trigger? That's a lot of "crying wolf" for many people.

← PreviousPage 10 of 34Next →