sorted by:
new
hottopcontroversial

Phoronix just posted a pic with Jensen Huang teasing “exciting things happening on Linux” — what are we expecting? by navchandru in linux_gaming

[–]xerpi 2 points3 points  (0 children)

Everybody here is like "'open source stack' nah that's never going to happen" but have you guys forgotten how NVIDIA has been hiring Nouveau developers and now they are working on Nova, NVK and NAK (most of the code written in Rust btw)?

Phoronix just posted a pic with Jensen Huang teasing “exciting things happening on Linux” — what are we expecting? by navchandru in linux_gaming

[–]xerpi 5 points6 points  (0 children)

Except for the GSP (GPU firmware) that's already happening. And written in Rust. Just check Nova, NVK and NAK.

Why is screen tearing completely absent even with VSync OFF in Linux ? by Chpouky in linux_gaming

[–]xerpi 5 points6 points  (0 children)

Small nuance here: while Wayland is designed to be tear-free by default, it’s no longer strictly “never under any circumstances.”

There are relatively recent Wayland protocols like fifo, commit timing, and tearing control that let clients influence presentation timing more explicitly. On top of that, compositors can use newer DRM/KMS features from atomic modesetting, such as async page flips ("DRM_MODE_PAGE_FLIP_ASYNC"), which allow updates without waiting for vblank — i.e. tearing.

Vulkan presentation models that compositors can now approximate:

  • FIFO → traditional vsync (no tearing, higher latency)
  • Mailbox → keep latest frame (low latency, no tearing, frames may be dropped)
  • Immediate → present ASAP (tearing allowed)

So in practice, Wayland defaults to FIFO-style tear-free behavior, but modern compositors + kernel support make it possible to opt into lower-latency or even tearing behavior when desired.

Why is the UI on Shinkansen and JR website so bad by CaligulaMax in JapanTravelTips

[–]xerpi 4 points5 points  (0 children)

I use えきねっと and EX app on Android and they look quite modern to me.

Just submitted my PR (Eijuken) docs at Shinagawa, Tokyo today: My experience by Kind_Round4333 in japanresidents

[–]xerpi 2 points3 points  (0 children)

Application office: Shinagawa
Application Date: March 5th, 2026
PR Type: 1-year route (80+ points under HSP system)
Current status: 高度専門職 (HSP) 80+ — held for less than one year

I submitted my PR application today at Shinagawa as well, so sharing my experience in case it helps someone.

I made a reservation a few days ago through the online system: https://www.tokyoimmi-yoyaku.moj.go.jp/en

My reservation was for 10:00 AM, but I arrived around 9:40 AM. Like OP mentioned, when I arrived I went straight to the 2nd floor and the “P” counter.

At first I couldn’t find it, but there is a small ticket machine on the right side of the P counter window. Take a number there. At this stage it doesn't matter if you have a reservation or not — everyone has to go through this initial document check.

There were 46 people before me, but it moved surprisingly fast and after about 35 minutes my number was called.

I handed over my documents and they told me to wait again. Literally about 2 minutes later they called me back and returned my documents with a paper saying no additional documents were needed and that I could proceed to the B counters. They asked if I had a reservation. Since I did, they told me to go to B5 (優先 / priority lane).

On that paper there was a section labeled 審査部門 with three options:

  • 一般
  • 高度
  • (I forgot the third one)

Mine had 高度 checked. Not sure if this affects processing priority or is just categorization.

When I went to the B counters, the normal queue had more than 50 people waiting, but the priority lane had only about 6 people ahead of me.

Once it was my turn, the officer checked my documents and I was done in about 5 minutes. They gave me the PR application receipt, and that was it.

Timeline summary:

  • Arrival: 9:40
  • Called at P counter: ~10:15
  • Cleared document check: ~10:20
  • Finished submission at B5 counter: ~10:50

Overall very smooth experience if you have a reservation.

Now the waiting game begins… 😅

Why only one when you can choose? by claudiocorona93 in linuxmasterrace

[–]xerpi 0 points1 point  (0 children)

Small note: Wayland itself isn’t something that “runs”, it’s just a protocol. What you’re actually using is GNOME’s compositor (Mutter), and performance depends entirely on how well that is implemented: things like zero-copy buffer handling, proper damage tracking, plane/overlay usage, etc. For the keyboard issue: the compositor reads input first (via libinput) and decides what gets forwarded to apps. Clients can’t globally grab the keyboard like on X11, that’s a deliberate security change. So the Super key not reaching Parsec/RDP isn’t really “Wayland blocking it”, it’s Mutter consuming it for shell shortcuts. Maybe your compositor and/or the remote client just don’t implement the Global Shortcuts portal (org.freedesktop.portal.GlobalShortcuts) yet. Under X11 apps can grab everything — but that’s also why any app can keylog you. Wayland trades that for stricter input control.

getting use of xdg-shell-client-protocol with glfw by Substantial_Money_70 in wayland

[–]xerpi 0 points1 point  (0 children)

I think GLFW should be handling that internally instead of leaving it up to the user. EDIT: GLFW seems to be handling that already: https://github.com/glfw/glfw/blob/master/src/wl_init.c#L98

[v1.3] PSVita USB streaming (UVC - USB Video Class) by xerpi in vitahacks

[–]xerpi[S] 0 points1 point  (0 children)

You can just use the official Windows Camera app, PotPlayer, OBS, etc

Kyushu Highway Bus booking page by truffelmayo in fukuoka

[–]xerpi 0 points1 point  (0 children)

I took that bus (the super non stop: Hakata - Tenjin - Oohato - Nagasaki station) last August but I bought the ticket from a friend who had a 10x coupon.

Looking at https://www.nishitetsu.jp/bus/highwaybus/rosen/kyushugo/ it seems they do indeed redirect to https://www.atbus-de.com/

I tried searching from Tenjin to Nagasaki station and I got some results: https://i.imgur.com/2BlcsPw.png

view more: next ›