https://kotlinlang.org/docs/maven.html That’s not true, you can use Maven if you want!
https://kotlinlang.org/docs/maven.html That’s not true, you can use Maven if you want!
If I recall correctly, the desktop right click menu was one of the things they fixed in Plasma 6, actually.
For the window corners thing, meta+left or right should let you move it to somewhere you can grab it.
They recently started bringing it back, so there’s a 5-10 year span where it wasn’t taught.
…or that it was asked at 8AM EST and it’s only been a few hours?
I’m more talking about laptops, you can use it without paying for it on a device you build yourself, albeit with some functionality restricted.
Oh no, the manufacturer of any computer with a windows license paid for it and passed that cost to you. You paid for it.
Imagine paying for Windows. What a waste of money.
Heh. “Guy” has some interesting history. It originally referred to Guy Fawkes, because that was his name. Then it came to mean any person, gender neutral, then it became any man, now gendered, but the neutral definition never went away, so we have both meanings floating around still, but the original meaning, an effigy of Guy Fawkes, died.
(I skipped a few steps in there because they’re not relevant between guy Fawkes and any person)
This is correct. You can also omit the parentheses on the function call in Lua if the only argument is a table or string literal.
I love the Lua one because it’s so true, LuaJIT is magic and Mike Pall is the only one who understands it as its creator.
Actually, EAC has a Proton-compatible build, the devs just have to use it. It’s not a hard switch, they just have to choose to allow Linux compatibility, which most devs (well, really it’s probably an exec level decision) do not.
I really wanted Wayland to work for me. I just bought a new ASUS laptop (and ASUS has a great Linux compatibility track record, mind you!), 7th Gen Ryzen+Radeon, all AMD. I figured, let’s use Wayland on this one.
I installed KDE Neon, updated the kernel (some stuff is broken on the LTS kernel, no big deal, easy fix), switched to the Wayland session, everything was fine…until I opened any chromium-based app. Crashed kwin, killed the session completely, it recovered, but in a new session. Switched to X11, everything works. Maybe if I grabbed a newer mesa from a PPA it would work, but:
And I know, technically KDE could (and afaik, is) implement session management so that doesn’t happen. But to my knowledge, literally 0 WMs/DEs can recover the session after a compositor crash currently, and that’s a big deal.
Try the other UI layouts, like the notebook bar. LO can look pretty close to MS office if you change the settings some.
Uhh, I was referring to the new ones France has been building, not the old ones…
In France. They standardized the designs so each one isn’t a one-off and they trained more people to work in the field.
I think you’re mixing up “You shouldn’t do this” with “you shouldn’t be able to do this”. The former is common in Linux, the latter is not. No one is advocating for the latter.
Do you have any evidence that there’s a pervasive effort from third party repair to mine your privacy for profit? I’d love to see it.
Also, fine, let’s assume they have no way of knowing it’s genuine. Why don’t they release the tool to pair the OEM screens publicly? It’d only work on the real ones, and they have such a tool, so if it’s actually about security, there’s no reason not to.
You know what’s funny? It’s not the independent repair shops stealing your data, it’s the “official” ones. https://www.theverge.com/2021/6/7/22522560/apple-repair-multimillion-iphone-nude-photos-privacy-settlement-pegatron
Those “bootleg” screens often are genuine, but Apple makes features not work unless paired. You can literally swap the screens of two fresh out of the box iPhones and they won’t work. Swap them back, they work fine. Don’t defend their practices, and don’t believe the lies about repair they’ve been feeding you for years.
Cargo is really simple, which is great, but also limiting. Maven is much more complex, but for good reason - there’s use cases, especially around multi-artifact projects and version sharing, where cargo would require either some glue or you run into some interesting edge cases. Usually, Rust isn’t used for the kinds of big, wacky projects with a million dependencies that companies write in Java/Kotlin, so those kinds of use cases are considered more unusual.
Gradle, in my opinion, makes itself complex because it’s all code, is very brittle, and several of its features just don’t work right and require workarounds. When it works, it builds fast and it works well, but getting it to work, and how often you have to get it to work again…not worth it.