jogu

Requests generally provides a simpler interface and absorbs some of the complexities if you were trying to use the stdlib directly e.g. pooling, redirects, retries, proxies, etc. It also smooths over some of the differences in the stdlib across Python versions, though that's less of an issue as of late as older versions are being deprecated.

No, this requests: https://github.com/psf/requests

The first thing on the page is:

> C64 OS has one goal. Make a Commodore 64 feel fast and useful in today’s modern world.

So I guess whatever "useful in today's modern world" means. What does this new OS allow me to accomplish on a C64?

> For me and my friends, "let's play contra" doesn't take longer than maybe 10 seconds from intention to the start screen.

But how would they know you have Contra and think to play it? The presence of a physical cartridge or recognizable console sparks the spontaneity. I think Analogue's consoles do this in a way that RetroPi does not.

> The Analogue OS doesn't say if it supports TV output or controllers

To be clear, I'm not talking exclusively about Analogue OS or the Analogue Pocket, but their other existing products the Mega Sg and Super Nt.

> And TBH if that format is best for you, why not just spend your money on a real console instead? It'll definitely be cheaper and will ALWAYS boot faster than anything else you can buy.

Unfortunately this isn't the case. Especially given the recent retro gaming boom inflating prices. You also have to consider that retro consoles are borderline unusable on modern TVs (even if they have composite input) and you'll need to purchase a quality upscaler (or hardware mod), which can run anywhere from $80 to $500 depending on what you get. If you don't mind having a CRT you can go that route too, but nice CRTs are also quite expensive. Then if you're interested in playing ROMs that's unlockable via a jailbreak on the Super Nt vs paying $80 - $200 for a flash cartridge.

So here's what I want:

1) Play on a modern TV via HDMI

2) Play original cartridges directly

3) Native support for original controller hardware

4) Support for additional accessories that worked on original hardware

5) The option to play ROMs if a particular game is inaccessible physically

The Super Nt/Mega Sg provide all of these things at a much cheaper price than trying to get the equivalent on original hardware.

> I guess my main argument is, I could make a RetroPi in a few hours with every emulator, and every rom, and meet all of the marketing criteria with better settings. Including better compatibility.

> Assuming they're trying to advertise to my market, why would I pay 50x the cost for an inferior product? Why wouldn't they start from where emulation enthusiasts currently are instead of way behind?

If you're happy with RetroPi then Analogue's products simply aren't for you.

Being able to use my original controllers, accessories, cartridges directly (not just dumping the rom) is important to me. Having a big Street Fighter II cartridge sticking out, two controllers right there, and simply pushing the power button to immediately get into that game is important to me. It strikes up conversations and leads to impromptu gameplay in a way that a RetroPi or something similar likely doesn't.

Yes, it's quite interesting seeing all the negative feedback. To be honest, I don't quite understand it.

I've purchased both the Super Nt and Mega Sg and have been extremely pleased with them. They're extremely high quality and strike a great balance between providing an authentic experience for the console while being reasonable to use with a modern TV. And to be blunt, aren't even an unreasonable price when compared to the alternatives for making the original hardware usable with similar fidelity and features.

I own a DE10-NANO, the development kit powering the MiSTER project, as well as both the Super Nt and Mega Sg.

I agree that there's a lot in common, but I think the two projects target vastly different audiences.

The MiSTER project has a broader scope, and aims to preserve legacy hardware, including games, but also older computer hardware. It's much more geared towards hobbyists or tinkerers as you'll have to buy various hardware extensions to have the right setup for the console you're actually interested in playing. That being said, the MiSTER project never aims to truly be a "replacement" for any of the consoles it supports. Things like reading the console's native media or native controllers aren't really goals of the project.

Analogue's consoles on the other hand are meant to be drop in replacements for the original hardware, just re-imagined for today. They have the original controller ports, cartridge slots, support for original expansion hardware, etc. They're highly polished, and targeted at solving a specific use-case. The biggest problem the Analogue consoles solve is hooking up to modern TVs. I see them as an alternative to purchasing a CRT, upscalers, or modding original hardware, all of which can quickly ring up a bill equal to or more expensive than one of Analogue's consoles.

While not sponsored exactly, the UK has made some targeted changes to visa policies that make it easier for people in Honk Kong to relocate to the UK.

The PPA landscape certainly has changed and things weren't nearly as centralized as they are now.

I don't think the AUR is necessarily more secure but in general the nature of how the AUR works does perhaps give some slight advantage. The suggested approach to the AUR is to download and inspect the PKGBUILD so you know how/what the package is doing opposed to a PPA typically being a precompiled binary. AUR helpers will also typically show recent comments, etc. so if a package was compromised or had issues you'd probably know as you're pulling it down.

Really though the AUR just tends to be more convenient and complete than finding random PPAs in my experience.

Came here to say this. This will be especially interesting if there's better support for GPU virtualization to allow a Windows VM to leverage the card without passing the entire card through.

They did, and this is the continuation of that work. The bulk of the work wasn't on the base distribution, but on surrounding libraries e.g. proton. They felt Arch was a better base and moved off of Debian is all.

PPAs work great until they don't, because it's just some random guy building the packages half of the time.

The last time I seriously tried to use Ubuntu was probably 8-10 years ago and I ran into a lot of trouble trying to get up to date graphics drivers via PPAs. I also remember being tired of having to go find a random PPA for every piece of software I wanted. Most of the time I would just find some random blog that provided a "PPA for up-to-date package X" and ultimately felt like what I was doing wasn't really any better than downloading random MSIs like you would on Windows.

With Arch though you get the AUR which quite literally has every piece of software you could ever want and is at least managed and maintained in a central place so you're not just adding random PPAs for everything.

> Yet <づ> and <ず> are phonetically indistinct but entered differently; the input scheme is really not based upon phonetics but on structure.

Not sure what what your point is here. ず＆づ may or may not be phonetically indistinct based on region.

> I think you might confuse the words “phonetic” and “phonemic” here.

I mean phonetic more in the layman sense e.g. relates to the sounds, not the most technical linguistic definition. To be blunt, the linguistic definition is silly anyways since literally no natural language will ever strictly meet it.

> It really is neither phonetic nor phonemic.

I guess my original point was that just because you can type certain kana in different ways that may not be strictly phonetic they make sense as simplifications based on the structures you mention, and they make typing easier.

This does not mean you cannot type using inputs that correspond to more strictly phonetic romanizations e.g. hepburn.

I could see how one might come away with this opinion but if you reflect on the nature of video games the fact of the matter is they're inherently proprietary software. Given that video games are more art than function, I think I'm okay with that too.

If we accept that video games are proprietary, whether or not they target a native Linux runtime (which no standard exists) or a Valve blessed windows emulation runtime hardly matters. We as users have no power to build these applications for a desired runtime and it's unreasonable to expect publishers to work against an undefined moving target. History has already proven that this tends to be a worse experience in the long term for Linux users and even more recently native builds can be worse than Proton builds.

I don't think it's fair to say it isn't entered phonetically. Fundamentally typing in Japanese is grounded in providing the phonetics of a word which can then be converted to more precise characters.

As for Romaji based input, certainly there are some liberties taken based on the logical structure of kana that have been to applied to typing for convenience, but for the most part the Romaji has been chosen for phonetic reasons.

It's also worth noting that from an English perspective the sound you associate with <ti> might be different from the sound a Japanese person might associate with it. Just because the usage isn't strictly the English phonetics, doesn't mean the symbols aren't being used phonetically.

I've been studying Japanese for about 10 years now and think these systems are actually rather intuitive if you know the language. Digital input methods aside, most of the complexity comes from the writing system itself and just comes with the territory.

Why is <n> vs <nn> depending on context silly?

Context is required to disambiguate ん vs an initial consonant of the な行. There's not really another choice unless you want to make <n> exclusively used for one or the other, which also isn't great.

<l> is also not unused, it's a prefix for the smaller version of characters e.g. <le> => ぇ or <ltu> => っ

> There's also the fact that this can't compete with the Switch due to the simple fact that games are optimized to run at a stable framerate by the developers or subcontracted companies for the Switch

I have a pretty extensive Switch library and can definitely say that performance of ports is really hit or miss.

This is also missing that PC games are already designed with a broad range of hardware in mind and nearly every game for PC has extensive settings to control graphical quality vs performance.

Sure, maybe a device like this might have performance issues but I don't think the Switch completely trumps this in terms delivering playable experiences.

Yes, look into retroarch netplay. They have a rollback netplay implementation that works great from my experience.

Neo: TWEWY is made and published by Square Enix. Why would this imply they had talks with Nintendo?

Purchasing older models on the second hand market is generally a decent option if you're looking to get a better price to performance ratio.

You're looking for an EF to EOS R mount adapter. I think the general consensus on adapters is overall positive, but you will be making some slight concessions in autofocus performance and image quality pending the specific adapter/lens combo. It really comes down to what kind of photographer you are and how important super fast autofocus is.

> I have to say that mirrorless is just superior

I think for the most part I'd agree with you, there's definitely a lot of upsides in mirrorless systems, especially in terms of flexibility. I will say though that the screens in mirrorless EVFs are often lackluster in comparison to optical view finders in my opinion. In particular frame rate of the EVF is problematic for me.

Great to see the KDE development community being so active. I think it has really been showing in the end product. Over the past 2-3 years KDE has easily become my favorite environment, even over macOS or Windows as of late. For the most part things just work, all the default apps are solid. In particular Dolphin is hands down the best file manager out there. Kudos to the KDE devs.

I've never noticed or been bothered by this. Typically when I want to edit a URL it's almost always deleting or replacing a substring in the URL. To do that I just single click + drag which highlights only the selected text instead of everything.

> Japan's rent-a-family industry was completely fake

That's really not what that article is claiming. It's claiming that a particular individual has lied about the industry and made it seem stranger than it actually is and the western media has sensationalized that even further.

There absolutely are rental services for boyfriends, girlfriends, mothers, fathers, etc. in Japan, they're just not as bizarre as some of these articles would lead you to believe.

For now that's the case, but since the introduction of GateKeeper Apple is slowly but surely trending the default configurations to make it more and more difficult to run software source outside of their own app store.

I believe the defaults now extend to software sourced outside of the app store must still be notarized by Apple. This impacts developers more than consumers I would guess, but certainly requires more effort from developers to create and distribute software.

I think the definition has always been a bit gray, even more so in recent years but I don't think it's about the hardware present in the device. For example, Sony made a push to classify the PS2 as a computer by providing a BASIC interpreter and later a distribution of Linux to evade some tax laws in Europe.

I think if I were to answer this question now it would be based on the expectation of the end consumer to be expected to, or have the ability to program the device for general purpose tasks.

Things like game consoles, phones, smart appliances, etc. all start to blur that line but I think it comes down to the consumer's expectations.

I'm in the USA and get Japanese results when I search for things in Japanese. Google has settings for both region and search result language, I would try setting those.

It's one of the readings of the Japanese character 軽, which means light (as in not heavy). That would be my guess, but I can't say for certain.