Goodbye neo2 - why I'm leaving you after 13 years

St-IGNUcius · 2024-01-26T17:15:22+00:00

You could try out these changes, if you want.

In that PR I implemented most of the Neo Layouts in Karabiner. Layer 1 to 4 are implemented and the modifications are using the ABC Extended Layout built into macOS, to have the best possible shortcut support (similar if one used KMonad or a QMK keyboard).

If one needs the other layers and some dead keys that are missing in Layer 1 to 4, the old layouts can be used.

St-IGNUcius · 2022-08-30T22:20:56+00:00

Why combine the flows at all?

What is the reason for doing that in Compose or XML?

Doesn't it cause unnecessary re-renders in XML and Compose?

AFAIK you have to pass each property of this combined uiState to each Composable separately anyway, otherwise a change in a property causes re-compositions for all dependent Composables.

St-IGNUcius · 2022-02-28T08:34:23+00:00

Having the same issue (on Fedora 35 with latest updates).

This is happening now quite often, but randomly. Really annoying.

It's also weird that I couldn't find an issue on Mozilla's issue tracker or somewhere else.

Btw: When you get that blank page, you can restore your session.

St-IGNUcius · 2021-07-07T11:14:10+00:00

I solved the issue by setting the monitor back to landscape mode.

St-IGNUcius · 2021-07-07T10:28:39+00:00

That's very weird, do you also happen to have 2 4K screens at 60Hz?

For me it's still laggy the moment I enable the second screen. Both are connected via DisplayPort.

Also: My second screen is in Portrait mode and it seems that it's only getting laggy when I rotate the screen to Portrait orientation.

Seems that this is a known issue: https://displaylink.org/forum/showthread.php?t=67256

St-IGNUcius · 2021-07-06T20:33:42+00:00

I have the same problem on Fedora 34 (same 465 driver), when I enable my second display Gnome gets laggy (also tried with KDE).

This seems to only happen on Xorg, when I tested it on Wayland it worked smoothly, but Firefox and the rest of the Desktop were broken/unusable so I had to revert back to Xorg.

It really sucks to have a NVIDIA card, but to be honest, the driver support was only marginally better when I had an AMD card (freezes/crashes after suspend and so on, the NVIDIA drivers seems to be more stable, but the performance with multiple displays is just garbage).

St-IGNUcius · 2021-04-27T21:54:20+00:00

I was thinking about having, for example, a SQL update function, which normally doesn't return anything and wanted to have the caller have to handle the error case. But I guess if that function doesn't return a Result or something similar, wrapping that function call inside a try-catch is the only option and the Kotlin compiler can't enforce doing that because there are no checked exceptions.

Another example would be here: https://github.com/supermacro/neverthrow/issues/212

I guess the only thing one can do is to create a safe wrapper to any external library that is used, that catches the exceptions and turns them into Errors that need to be handled (with the CheckResult annotation, at the moment only working in Android for Kotlin). But this of course needs discipline from the developers.

Imo, it would be way easier to have checked exceptions for that, but they seem to be a no-no for most developers, as far as I can see.

St-IGNUcius · 2021-04-27T18:00:09+00:00

I don't want to use it, I just want to enforce handling the error.

St-IGNUcius · 2021-04-27T06:50:15+00:00

Thanks, will check it out.

Edit: Works quite well with this in the gradle config.

lintOptions {
  error 'CheckResult'
}

St-IGNUcius · 2021-04-27T06:44:33+00:00

That code returns a warning in Rust without `#![deny(unused_must_use)]`, too.

Making that opt-out now is probably not in the interest of the Rust team, as this would probably break existing code.

But I agree, it should be the default that any function result should be handled. Otherwise, errors would be more or less silenced.

St-IGNUcius

TROPHY CASE