vsmhn

RSS feeds are actually used quite a lot in the podcasting industry. And indeed, nothing guarantees that you won't get ads in those podcasts, because ad insertion is done server-side in a lot of cases, so the media URL in the RSS feed will be served with ads in it.

Sweet childhood :D! So much nostalgia was tied to this game, that beginning the pandemic I thought I should have a go at creating a virtual pet game for Garmin touchscreen smart watches. It's nowhere close to the actual Tamagotchi games, but it was a nice project.

Garmin Connect IQ: https://apps.garmin.com/en-US/apps/f5fc24e2-7cea-4585-8878-a...

Github: https://github.com/vladmunteanu/monky

I was really tempted to buy a new Mac but there are still lots of gotchas my colleagues had to solve, so I decided to wait. Pushing ARM64 to developer machines still seems like a rushed decision imo, and it definitely shifted resources into building and supporting ARM64, resources that Apple doesn't necessarily pay for. At the end of the day, for me it matters how fast I can do a certain task and how much spare time I have left after I finish it.

Docker example: https://docs.docker.com/desktop/troubleshoot/known-issues/ See the "Known issues for Mac with Apple silicon" tab.

Judging from your fourth row, it seems to be that "Apple made me give up a project today" is the correct headline, since M1 is apparently the issue.

I still wonder why we don't see wide spread standardized battery packs placed in standardized housings, that could be swapped faster at existing gas stations with minimal infrastructure. Ideally, swapping would take relatively the same as filling a tank of gas and would be done by an automatic system. I've seen some videos of NIO doing this, but I'm pretty sure there's no standardized solution for the European market.

I think this model could work if car owners don't own those replaceable battery packs, but they just pay for the energy inside them instead. I guess it would be easier to install 1 automatic ramp in a gas station that services a client in < 5 minutes than to build charging stations that service clients in hours.

LE: not referring to the whole battery capacity, these packs could offer ~100km range depending on the vehicle.

NamedTuple works great for a lot of cases, but not always. For example, when dealing with attribute defaults for mutable collections. Dataclasses have a `default_factory` that is used in these occasions.

> I write code in order to express myself, and I consider what I code an artifact, rather than just something useful to get things done. I would say that what I write is useful just as a side effect, but my first goal is to make something that is, in some way, beautiful. In essence, I would rather be remembered as a bad artist than a good programmer.

This entered my list of favorite quotes! For this, if not for your huge contribution to OSS, grazie!

Also on HN: https://www.sciencemag.org/news/2020/03/who-launches-global-...

Testing will be randomized apparently.

Precisely my thought :).

Also, what about the builtin array module? https://docs.python.org/3.7/library/array.html

trollius is no longer maintained

I'm not sure I understand the question, are you interested in comparing tornado and aiohttp?

Does it support HTTP/2?

I understand your point, and I'll try to update the README with that information. However, this client tries to follow Tornado's ways, whereas aioh2 works on Python's asyncio.

It's still WIP, so feedback like yours helps a lot, thanks!

Why Python 2 and not Python 3?

Short answer is: because Python 3 already benefits from a better, more complete client: aioh2 (https://github.com/decentfox/aioh2) that works with Python's asyncio.

th2c is mostly intended for Tornado backends, trying to keep a similar interface and compatibility with Request / Response objects.

It was initially developed in order to be able to communicate with APNS from a python 2.7 environment.

Well, Python 3 already has a similar library that deals with this stuff, such as https://github.com/decentfox/aioh2.

Also, this is mostly intended for Tornado backends, offering compatibility with Tornado's request / response objects.

Happy to hear that, keep up the good work!