uranusjr

21 ms·

151.
by uranusjr 5y ago
Exactly. Media as well. They are everywhere (which is not a problem) and always keep Chinese interest above everything wherever they go (which is the problem).
152.
by uranusjr 5y ago
This is spot on. The decision is not made not (necessarily) because it benefits the company, but because more middle management actually think it’s “right”. FAANG are practically run by Chinese these days. (I am Taiwanese and hear about thi
153.
by uranusjr 5y ago
It’s more complicated than that. Poetry’s predecessor Poet started at about the same time as PEP 518 (independently), but it jumped head-first to pyproject.toml when the community started using that file. A lot of Python packaging is like t
154.
by uranusjr 5y ago
Yarn got most of its popularity during a time when it was clearly ahead of npm in every way, but saw its share dropped when npm caught up. IMO Poetry came a bit too late; it would have been a tremendous hit in like 2015, but as the timeline
155.
by uranusjr 5y ago
I think it’s just Guido’s Dutch humour not getting across. The toolchain was already recently upgraded to support 3.10, and IIUC can handle 3.999 fine.
156.
by uranusjr 5y ago
There’s a mental mismatch in here. The pull request workflow works on GitHub because 1. every piece of code has a clear owner that is in charge to gate-keep the changes, and 2. if the gatekeepers fail at their job, contributors have a reaso
157.
by uranusjr 5y ago
They differ slightly in semantics; asyncio.run() always creates a new event loop to run the task, while run_until_complete() don’t (unless you call asyncio.create_event_loop() of course). I don’t know if this is the reason behind the decisi
158.
by uranusjr 5y ago
Shirley you realise WinAPI is officially named the Windows API?
159.
by uranusjr 5y ago
Pyston has been around for way longer, and even its post-Dropbox relaunch (v2) predates Cinder’s open sourcing by a lot, and has seen steady development. The only thing you can argue is they cut the v2.2 release in response to Cinder, which
160.
by uranusjr 5y ago
> Can the python packaging story get much worse? Of course it can get much worse, see where Python packaging was ~5 years ago.
161.
by uranusjr 5y ago
> You don't need make from __future__ import annotations as default. You don't need to make async/await keyword. By the same logic unicode_literal and print_function should have never been the default? Yeah I guess you can
162.
by uranusjr 5y ago
> 2.X broke less stuff while still providing new features. By putting off all the cleanups to Python 3. I think I like their current approach better.
163.
by uranusjr 5y ago
It’s very much an “or” situation from a practical standpoint. Maybe not exclusively or, but it’s unrealistic to say one does not significantly affect the other. Python core dev (CPython or otherwise) is already thin on resource for a long t
164.
by uranusjr 6y ago
Aside from the point that the backing technology doesn’t define where a service is “from”, it’s still a clone popped up in China no matter what’s being cloned?
165.
by uranusjr 6y ago
I live in Taiwan. News from Japan usually needs accompanying cultural explanations even here. People from Taiwan, China, and South Korea have difficulties understanding the situation even we’re lifelong neighbours. Yes, Japan is that freaki
166.
by uranusjr 6y ago
It’s like something between Twitter reply and quoted RT, which both shows up for your own followers and notifies the OP you said something about their topic. Before big social networks were popular, this was a very good way to make new frie
167.
by uranusjr 6y ago
It was also hugely nicer than the Sibelius now. In fact I’d even say Dorico is more like Sibelius (around version 3 or so, when the UI peaked IMO) than the current Sibelius.
168.
by uranusjr 6y ago
Alex Birsan’s attack was much more involved and raised issues less recognised by a vast number of communities members. This one is basically typosquatting, a well known issue that Birsan’s manoeuvre did not focus on.
169.
by uranusjr 6y ago
What are the incentives? I honestly can’t tell.
170.
by uranusjr 6y ago
The cross-platform pwsh is actually what inspired me to go on the hunt, and was the first thing I tried. But while it’s good on Windows, using it on POSIX just felt… wrong, somehow. I later discovered uutils/coreutils (a Rust reimpleme
171.
by uranusjr 6y ago
IIRC this was considered out of scope. fromisoformat is defined as the functional inverse of toisoformat, and since the latter never emits Zulu, the former does not parse it. The only “reasonable” fix would be to rename those functions to s
172.
by uranusjr 6y ago
This is pretty cool! I’ve been searching for a nice shell to unify my workflows on Mac, Windows, and Linux (WSL). Choices are few and far between, Elvish is the only thing that has worked out (which is fortunately more than decent for me),
173.
by uranusjr 6y ago
ISO 8601 does not contain timezone information, but offset . Timezone info needs to be specified separately, likely as IANA names. It is a common misconception to time zones though, and in a way demonstrates why it’s best practice to alway
174.
by uranusjr 6y ago
Update: 3.8.8 and 3.9.2 have been released. https://discuss.python.org/t/python-3-9-2-and-3-8-8-are-now-...
175.
by uranusjr 6y ago
Yeah, I’d say not all rules in pyupgrade are universally popular. Fortunately I seldom see it used as a CI checker or pre-commit hook, and much more often used as a one-off transition tool with output manually reviewed instead (more like 2t
176.
by uranusjr 6y ago
Unless the tool does something more than its tagline, pyupgrade[1] offers the same functionality and much more. [1]: https://github.com/asottile/pyupgrade
177.
by uranusjr 6y ago
Although the CPython implementation contains an LL(1) parser (which is being deprecated for a new PEG parser), the grammar contains bits that are not context-free, which involved a pre-parsing step before being fed into the LL(1) parser. Th
178.
by uranusjr 6y ago
> I love SQLAlchemy but its syntax is a huge turnoff. Out of curiosity, which part of the syntax? (Hopefully not all of it.) Personally I hate the declarative part (defining the model), but feel the query syntax is good, especially with
179.
by uranusjr 6y ago
> it's reflective of an attitude where old stuff is hung out to dry even before the officially-committed time horizons have expired. As mentioned in another comment, the “officially-committed time horizon” is imposed by Ubuntu, and
180.
by uranusjr 6y ago
I suspect your “additionally” part is in fact the main reason. Emojis in Japanese phones were transmitted not by font information, but dedicated code points like Unicode. East Asian SMS systems need to implement multi-byte encoding for “rea

More ›