pepoluan's comments

On: Ruby vs. Python comes down to the for loop (2021)

[pepoluan]

Have you ever seen algorithms written as "pseudo code"?

Why do you think they do that?

Answer: To make algorithms easier to understand for other humans.

Python more closely resemble pseudo-code compared to Ruby.

Hence Python is more aligned toward "built for humans" than Ruby.

On: Ruby vs. Python comes down to the for loop (2021)

[pepoluan]

This is why you should use type hints and some kind of type checking.

sorted_list: list = my_list.sort()

will raise a red flag with a type checker.

On: JavaScript Bloat in 2024

[pepoluan]

Will using HTMX save a lot?

On: Python datetime pitfalls, and what libraries are (...

[pepoluan]

As long as it is now deprecated then it's no longer ironic.

On: Python datetime pitfalls, and what libraries are (...

[pepoluan]

The problem with Unix Epoch is that it began in 1970.

There are applications where you need dates before 1970 and that starts to get hairy.

[zokier → pepoluan]

Bigger problem of 1970 epoch is that the 1970-1972 period was confusing time for UTC; having the epoch at 1972 would be arguably much cleaner

Fun excerpt from Wikipedia:

> As an intermediate step at the end of 1971, there was a final irregular jump of exactly 0.107758 TAI seconds, making the total of all the small time steps and frequency shifts in UTC or TAI during 1958–1971 exactly ten seconds, so that 1 January 1972 00:00:00 UTC was 1 January 1972 00:00:10 TAI exactly, and a whole number of seconds thereafter. At the same time, the tick rate of UTC was changed to exactly match TAI.

I'll leave it as exercise to the reader to think of all the implications of whatever timesteps and tickrate shifts that happened pre-1972.

[magicalhippo → pepoluan]

Signed integers exist. What is hairy about using them?

On: Ask HN: Which Python type checker should I use?

[pepoluan]

PyCharm professional understands Django natively. Maybe try that? PyCharm also has its own type-checker that's a lot less fussy than mypy.

On: Ask HN: Which Python type checker should I use?

[pepoluan]

Well the guys at astral has no plans in the near future to create a static type checker.

Ruff is great, though. I now stop using flake8+black+isort and have gone all-in with Ruff.

On: Ask HN: Which Python type checker should I use?

[pepoluan]

Use lots of typing.Protocol and you get all the goodness of duck-typing.

On: Ask HN: Which Python type checker should I use?

[pepoluan]

I maintain aiosmtpd using PyCharm and... That's it.

Playing around with Ruff nowadays.

mypy was proposed early during aiosmtpd development but we decided it's not worth the headache.

On: Ask HN: Which Python type checker should I use?

[pepoluan]

I just use the built-in one in PyCharm.

It serves my need, which is to ensure I haven't done mistakes in specifying parameters to functions.

I have no desire making Python to be statically-typed.