Took me a sec.

TIL this exists

I also like the POSIX “seconds since 1970” standard, but I feel that should only be used in RAM when performing operations (time differences in timers etc.). It irks me when it’s used for serialising to text/JSON/XML/CSV.

I’ve seen bugs where programmers tried to represent date in epoch time in seconds or milliseconds in json. So something like “pay date” would be presented by a timestamp, and would get off-by-one errors because whatever time library the programmer was using would do time zone conversions on a timestamp then truncate the date portion.

If the programmer used ISO 8601 style formatting, I don’t think they would have included the timepart and the bug could have been avoided.

Use dates when you need dates and timestamps when you need timestamps!

Do you use it? When?

Parquet is really used for big data batch data processing. It’s columnar-based file format and is optimized for large, aggregation queries. It’s non-human readable so you need a library like apache arrow to read/write to it.

I would use parquet in the following circumstances (or combination of circumstances):

• The data is very large
• I’m integrating this into an analytical query engine (Presto, etc.)
• I’m transporting data that needs to land in an analytical data warehouse (Snowflake, BigQuery, etc.)
• Consumed by data scientists, machine learning engineers, or other data engineers

Since the data is columnar-based, doing queries like select sum(sales) from revenue is much cheaper and faster if the underlying data is in parquet than csv.

The big advantage of csv is that it’s more portable. csv as a data file format has been around forever, so it is used in a lot of places where parquet can’t be used.

Wow everyone seems to love P3 but I actually liked P4 better. I mean I really enjoyed both, but P4 was a more immersive experience for me. I should reboot my vita and play it again.

I really felt like P4 had deeper connections and relationships between the characters. It felt more real, and that made the tension in the game more exciting. I love every second of it and am still trying to find a game like it.

Don’t get me wrong, P3 was great also. The gameplay was superb and the characters were all great. But P4 still has a special place in my heart.

The autocomplete is nice but I don’t find it a game-changer. The comment about writing tests is on point though, but that’s the only place I found out useful.

They’re asking for TV manufacturers to block a VPN app in the TV. Not to block VPN in general.

Dude, if you’re being obtuse on purpose because you have an ax to grind against Rust, try a different approach. You’re not getting anywhere, clearly by the fact that no one agrees with you.

If you don’t like that Rust has a restricted trademark, then call that out instead of trying to label the software and it’s license as non-free. It’s literally called out in my source that name restrictions ipso facto does not violate freedom 3.

But if you genuinely believe that the implementation of the Rust language and it’s trademark is burdensome to create a fork, and you want people to believe you, then you gotta bring receipts. Remember, the benchmark that we both quoted is that it “effectively hampers you from releasing your changes”. It being “not a piece of cake” doesn’t cut it.

Hint: Google Rust forks since their existence also undermines your claim.

Good luck.

Please read this and try again.

https://www.gnu.org/philosophy/free-sw.en.html#packaging

Rules about how to package a modified version are acceptable, if they don’t substantively limit your freedom to release modified versions, or your freedom to make and use modified versions privately. Thus, it is acceptable for the license to require that you change the name of the modified version, remove a logo, or identify your modifications as yours. As long as these requirements are not so burdensome that they effectively hamper you from releasing your changes, they are acceptable; you’re already making other changes to the program, so you won’t have trouble making a few more.

Password managers support passkeys.

If you are being intentional about its use, then you can get a lot out of it. But for some, maybe even most, YouTube is a distraction.

Yes it can be an issue because the GPS doesn’t know where you are and thinks you are on an aboveground street. Freeway tunnels can have multiple exits too.

I disagree. I think the default option should be what users expect, and users expect “copy” to do exactly that: copy without modifying the text.

I’ve turned off the bot for now.

The first way to use it is with any type annotation: you just use it for documentation.

# int annotation
def add_1_to_number(x: int) -> int:
    return x + 1

# callable annotation
def printer(x: int, func: Callable[[int], int]) -> None:
    results = func(x)
    print(f"Your results: {results}")

These type annotations can help document and make editors parse your code to make suggestions/auto-complete work better.

The second way to use it is by creating a callable. A callable is an abstract base class that requires you to implement the __call__ method. Your new callable can be called like any function.

class Greeter(Callable):

    def __init__(self, greeting: str):
        self.greeting = greeting

    def __call__(self, name: str):
        print(f"{self.greeting}, {name}")


say_hello = Greeter("Hello") # say_hello looks like a function
say_hello("jim")  # Hello, jim

Hah that last page was great. Loved how easy they gave up helping the baka couple.

Haha what a lovely chapter. Kind of fluff, but out of nowhere. I wonder what’s going to happen at graduation? Will the series end?

I’m shocked.

Yep, this is the convention. Unfortunately, I’ve never been able to enforce it. Encouraging good git commit messages is probably the bottom of the things I can coach. I’d be happy if commits were properly squashed/rebased and that we all followed the same PR merge strategy.

Rocky Linux have said that they can rebuild using publicly available sources in UBI containers and cloud images.

https://rockylinux.org/news/keeping-open-source-open/

Though reading the article, I don’t know if SUSE is simply rebuilding or forking. In any case, it’s cool to see SUSE committed to open source principles.