HN user

anonova

886 karma
Posts0
Comments201
View on HN
No posts found.

Can confirm that this started happening today.

Log in to use old Reddit

To keep Reddit safe, accounts are required to access old Reddit. Log in, or continue without an account on reddit.com.

I don't participate in Reddit conversions and only use old.reddit.com to browse some specific subreddits as a guest.

An officially supported Rust SDK should be a high priority, IMO. The de facto AWS library Rusoto (https://github.com/rusoto/rusoto) went into maintenance mode is in need of maintainers (https://github.com/rusoto/rusoto/issues/1651).

Microsoft has an Azure SDK under their organization (https://github.com/Azure/azure-sdk-for-rust), but oddly, it's marked as "unofficial". It looks like Google doesn't have one for GCP, but there is a community-built one: https://github.com/Byron/google-apis-rs

Given all these companies are part of the Rust Foundation (https://foundation.rust-lang.org/members/), maybe I just expect more.

I find it absolutely frustrating that Rust packaging/crates.io doesn't support namespaces. The arguments I've read are always theoretical/what ifs, but I've yet to be convinced the current situation is better than the practical benefits of namespaces.

I was looking for a small image processing library (as opposed to libMagickWand) and came across libvips [1]. I found it absolutely bizarre that the public API in a C library was full of variadic functions to support optional arguments. The last argument to most function calls is required to be NULL to denote the end of the argument list, e.g., https://libvips.github.io/libvips/API/current/using-from-c.h... (vips_image_new_from_file, vips_invert, etc.).

[1] https://libvips.github.io/libvips/

I was under the impression that it wasn't for performance but for distribution, i.e., to optimize for app size. Instead of having a fat binary crosscompiled for different architectures, Apple uses the bitcode to compile and distribute per architecture. It's part of the "app thinning" process.

Yes, this is ones of my problems with Julia. It seems to be optimized for long runs and REPL/notebook usage.

Take, for example, a simple program that creates a line plot (https://docs.juliaplots.org/latest/tutorial/):

    using Plots
    x = 1:10
    y = rand(10)
    plot(x, y)
After installing the package, the first run has to precompile(?), and subsequent runs use the package cache. But ~25 s to create a simple plot is incredibly slow and frustrating to work with.
    $ julia --version
    julia version 1.1.1
    $ time julia plot.jl
    julia plot.jl  73.71s user 4.45s system 110% cpu 1:11.04 total
    $ time julia plot.jl
    julia plot.jl  24.41s user 0.39s system 100% cpu 24.633 total
    $ time julia plot.jl
    julia plot.jl  23.38s user 0.36s system 100% cpu 23.519 total

To enable static checking with srb, add this line (called a sigil) to the top of your Ruby file:

# typed: true

Isn't this called a directive/pragma? A sigil is a symbol on a name.

Either way, I'm excited to see this finally out after seeing the past presentations on it.