nerdwaller

I chose to not use either after trying both. Nether solves understanding `setup.py` (they are just indirections on it). Of the two, poetry seemed more comprehensive and stable across releases. There’s a small cognitive load of knowing a couple of Twine commands if you don’t use either.

I just use reader mode on iOS or Firefox, otherwise I think you can disable JavaScript on NYT.

For strictly Bitcoin a colleague showed me OpenDime[0] which is pretty cool. To get the secret key the device is physically altered.

Otherwise I have a few hardware wallets around but haven’t used them much as I didn’t like that some required a Chrome app or other less than ideal, from my perspective, setups.

[0] https://opendime.com/

This is just a data gathering link for Mozilla to validate some ideas for added revenue sources, they are also doing a VPN one.

Clicking the button brings you to a survey where they seem to indicate the intent is to be ad free:

> You clicked a button to possibly subscribe to Firefox Ad-Free Internet for $4.99

I'm not a lawyer, but I would consider revisiting your icon[0]. It looks identical to Patreon's[1] with a period/full-stop. On a technical note, this looks pretty cool and may have helped me hold off on ditching my mac products if I knew about it sooner!

[0] https://pock.dev/assets/img/brand/pock_logo_w.png

[1] https://c5.patreon.com/external/logo/guidelines/icon_color_v...

For those interested in MTB, guerrilla gravity is designed and, as far as I know, built in Colorado. The reviews of their bikes (even aluminum frames) are resoundingly positive. Considering the price points they’re not one to overlook.

https://ridegg.com/

It looks like they’re closer to what you’d use in `jq` (or loosely similar to Xpath if that’s familiar): https://www.postgresql.org/docs/devel/functions-json.html#FU...

Can you expand on why/where Guido was wrong beyond why he cites where he (and the core team) made mistakes in the linked talk? I'd disagree about the "need", as the fundamental changes (meaning non-package renaming changes) were pretty important for the increasingly international economy we are in.

I think this is mostly due to the 1.x guarantee that anything old will compile on anything new. I don’t know if Python or others formalized the same guarantee, but I don’t remember any issues 2.2 - 2.15.x (of course 2-3 is infamous). However 3.3+ (when I joined the py3 crew from py2) I don’t recall any either.

My experience with Go has been equally pleasant (though it does require more boilerplate for commonly accepted reasons in the community), but in no way unique.

Perhaps my wording is incorrect, but you’re 100% capturing what I was trying to get at. Thanks for the clarification!

> She thinks that some bugs in the standard library will never be fixed.

This is actually an interesting paradox to be in, and one that Linus Torvalds recently commented on. His focus, like Guido’s, is the user and even fixing a bug can break the user.

https://lkml.org/lkml/2018/8/3/621

It’ll be interesting to see how Go (Rust, and other new languages) evolve and if they can avoid some level of package decay when they reach the age of Python, Java, etc.

Another useful feature of 3.7+ (also available as a backport by the same name) I’ve not seen mentioned is: ContextVars

The gist is you get a single interface for any type of threadlocal storage that also works with coroutines (asyncio). I use it pretty consistently for context logging of long running processes in our systems. However it has implications on other concurrency paradigms usages as well.

https://docs.python.org/3/library/contextvars.html

Thank you for the correction! I’ve not used Py2 in 6 or so years.

You can use `typing.ClassVar[<datatype>]`

Guido had a good retrospective on the shift, while the change was hard and painful, it needed to happen for the language to be easier to work with longer term.

If you're interested it's worth a watch: https://www.youtube.com/watch?v=Oiw23yfqQy8

A funky thing about the Enum class is you may also want the `@enum.unique` decorator in most cases, which enforces the enum/value pair being unique. I found the documentation a little misleading until I found that [0].

[0] https://docs.python.org/3/library/enum.html#enum.unique

Extending `object` was necessary until 2.7 when it became the default and old style classes were removed entirely in 3. So I think while the GP comment recently learned they don’t need to extend `object` anymore, they are/were familiar with new style vs old style classes.

There’s a pretty vocal group that favors GitLab, I campaigned for it internally at a few companies as well - having so much of the tooling in once place is pretty nice. It’s obvious that GitLab is making quick improvements consistently.

The project boards are better than most others, the CI is phenomenal, and I have noticed the review process is being worked on.

Keep up the good work, we need options in the space!

Unfortunately the perception was earned a few years ago created not by running “more openly” but real user experience and breaking people of that experience over several months is a long uphill battle for GitLab. I’m involved with a large group of Python developers that echos the same feeling, even though generally speaking many of us find GitLab (performance and reliability aside) a better and more comprehensive product.

I’d guess this was a consequence of a strategy decision that went against the plan (probably an expectation mismatch with users). I think the large part of the problem is the public GitLab instance is (was?) the beta environment, so a lot of issues popped up constantly while people were evaluating the options. In our group we are all volunteers, so when downtime impacts the little time we can dedicate (push code, review, deploy) it’s a fairly big deal.

Our python group (pyslackers.com) runs in the open as much as we can, so for us we went where the exposure and ease to be involved is (Github), even though from a raw feature perspective we liked what we had on GitLab when it worked.

Ironically at the bottom of the Popular Mechanics article is “Source: CNN”

You seem to assume that jquery isn’t already cached by the client. Given the widespread usage, while granted may be shrinking, the “bundle” may never be downloaded again; Assuming that’s the case, the download is moot, and more favorable, verses the SPA with some cache busting mechanism (that may release once per week or once per hour).

I believe this was post acquisition: An old company was on BitBucket (which we called internally “shitbucket” because of the frequent 500s) until we went on-prem to control our updates and mitigate bugs actually impacting us (I think this was “stash”). It was amazing how an “enterprise” system was so unreliable and companies still paid for it.

This is my thought as well, adding that it feels like way less boilerplate due to the integration with the underlying framework

I’ve been waiting to see Spotify follow Netflix and create their own label, instead of just curated playlists. They’ll otherwise always be at the whim of renegotiations. (Not entirely relevant to the post, but seems like it’s an avenue for them to go to break a little from other players).

You may have just made my day! Link for those interested: https://m.ign.com/articles/2018/11/14/ea-announces-command-c...

Helium Mix Optimal!

The original Red Alert was such a phenomenal video game.

Definitely a good point, though really depends on where how that Monero trade happens. If it’s ever traded/redeemed on an exchange, that privacy mostly disappears.

I’d argue (generally) no, because literally every transaction is in the ledger. Then there are two ways to get value back out:

1. At some point you want to get fiat back out, thus associating your identity to transactions. While there are some exchanges that are less stringent on verification requirements, the tie is pretty simple to see via the surveilled central banking system in most countries that tends to maintain the strict-ish verifications.

2. Exchange for goods. Unless this is off-chain, it’s again pairing a physical good back out somehow in an exchange of things.

To clarify for JWT invalidation, you don’t have to store the whole token. Instead just store the jti or some other identifying field that can be checked.