coolreader18

And also it's been confined to Switzerland for at least a couple years now; committing US federal crimes isn't a new circumstance for it.

In any case, it's still UB under the language guidelines, it's just not exploited yet.

I'm on a campus with these robots and over winter break, with the first big snow, a friend of mine was bored and apparently spent parts of his days just going around and helping the Starships that got caught in the snow.

Hey I'm also on venlafaxine! It's worked very well for me as well, though I don't think I can really speak to the topic of the OP since I started taking it when I was relatively young. I haven't noticed.. much? I guess?

Not sure if they edited the comment after you commented, but that is a bitfield now, at least

Oh, it's updated in the article now.

Might be biased/stereotypical, but Rust's cargo does dependencies really well. It's as easy as npm to add new dependencies, but there aren't thousands needed to do anything, and if you take a look at your Cargo.lock/`cargo tree` you can really get to know each of them and what they do or why they're pulled in. I'm still bloat-wary, maybe as a leftover from doing webdev, but with less transitive dependencies in the first place you can actually go through and prune things that aren't needed, or open PRs to transitive deps to prune from their trees or update deps to the latest version to deduplicate your tree. (If there are multiple semver-incompatible versions in a dep tree, they just both get compiled in - for most apps though, you should be able to get the number of duplicates to 0 or almost that.)

IIRC it involves qemu on aarch64

I think given these lines in the article (and the fact that she mentions OpenRC):

I have been an Alpine user for almost a decade and it's one of my favorite linux distributions.

This talk is intended to show how green the grass is on the other side and how Alpine can benefit from these basic ideas.

She's probably familiar with it.

Yep, one of the main things I did with nim for the month or 2 I was really into it was write a duktape wrapper[0] (in retrospect, I should have made the name a pun related to wrapping with tape...). It was pretty interesting given the stack-based nature of almost every duktape operation.

[0] https://github.com/coolreader18/duk

I guess I could've just opened discord, but I went looking for an example of what had changed: https://i.redd.it/l6sluq2o8hy61.png

Mods, could this be substituted?

I was able to guess that it was the Mario game (but I was unsure since this is HN not gamefaqs), but I'd think there are probably other acronyms that people here might jump to - I think the acronym should probably be expanded in the title.

Because ideally your JSON schema validator would turn it into a type that mirrors the structure of the data. "Parse, don't validate"[0]

[0] https://lexi-lambda.github.io/blog/2019/11/05/parse-don-t-va...

I mean I think in terms of maintainer resources Linux is one of the projects with the least to worry about, there are always companies who are willing to have a team work on stuff.

It's funny, wasm3 was just on the front page with a tail-call based interpreter model and now this is. Now I wanna do some stuff with tail calls :)

I though that was what the article was talking about as well, but I think it's actually the other way around - merge the last feature branch (the one that depends on the others) into the second to last, and keep collapsing down until you've got a PR targeting master with all the changes. That way, each individual changeset can be reviewed more easily, but the whole thing is still one "unit" that will be merged into master at once. (I think that's the gist.)

Wow, 90+ reviews with the "hashtag"/slogan Free Mohammed.

By that logic and reasoning Joe Biden and his crime bill and Bill Clinton who signed it into law are much bigger and effective racists

Well, sure.

I mean git projects aren't generally given a (YYYY) marker, since they're expected to be continuously updated - no reason it couldn't be updated tomorrow if someone finds something new, and it's not like the url is pinned to the specific current commit. I think it should probably just not have a (YYYY), even though it is prose.

Nah, I just didn't think it was necessary to put the full url since it was in the same thread. Idk.

Almost like this is something she's experienced before, and this is a preemptive attempt to stop it from happening.

Edit: for example, hn/item?id=26847629. "oh you probably have no idea how to do this, right? let me walk you through it"

It's funny, for at least the first example, original pronunciation just sounds like Hagrid from the Harry Potter movies, which is especially interesting considering that's intended to be a less formal/"lower class" accent. Reminds me of something I heard once that the modern american accent is actually closer to the british accent at the time of the revolutionary war, and it's the british accent that's changed more since then. No idea if that's actually true, but it was really interesting when I heard it.

Yep, I thought I recognized at least one of them from 1041uuu: https://1041uuu.tumblr.com/post/104751238713

Maybe there's a bundler/webpack plugin that supports deno's import system, so it just fetches whatever http urls/analyzes the import maps and turns it into a normal web bundle.

Maybe the intent is for it to be read as "If you're using pytorch and numpy, it's _very_ likely you're making this mistake", but the effect is still that the headline is clickbait

I feel like the first character of this title should be lowercased, URLs traditionally are and I thought it said "LSP" instead of "ISP"

the interface is what matters, and the implementation is secondary.

But that's kind-of the point IMO - if we take a free-market approach to this, copying (or sort of "standardizing" onto) an API allows for more innovation, since it's not a prohibitive up-front cost to switching the implementation. We don't copyright (or I guess patent, and I know they're different) the user interface of a fridge. Any fridge can have 2 doors and a slide-out freezer, but it's the actual implementation that would matter to a user - how energy-efficient it is, how cold it can get, extra conveniences (maybe akin to API extensions) like a water/ice dispenser that still can be "copied"/used by other fridges. And I'm sure that maybe those "interfaces" were patented originally, but it seems absurd now that they're so commonplace to restrict who can implement them.

This is sorta similar to rustpython_wasm[0] - I haven't been super focused on it recently, but I'd love to eventually have something as in-depth and well-designed as this. Currently it has all the necessary APIs (I think) to communicate however you want between JS and Python, but I'd like to have some sort of JSProxy object in Python so accessing JS APIs can look like it does in JS. Currently, you have to do something like:

    import browser
    from browser import window

    document = window.get_prop('document')
    document_body = document.get_prop('body')
    document_body.set_prop('textContent', browser.jsstr('hi'))

Hah, I did something sorta similar in my freshman year of high school - I noticed that emails sent to the whole school were sent to mailing lists (in gmail's terminology - not sure what this kind of address is in actual email standards) called "allYYYY.student.school.org", where YYYY is the graduation year of a grade and student.school.org is the domain all our student emails were at. I hadn't seen that kind of email address/mailing list address before, so I wondered whether it was just a legit email address as well. It turned out it was (it was for a google group in the domain also called "allYYYY" IIRC) so when I sent an email with subject line "Hello" and body "?" to allYYYY(at)student.school.org to see if it would give me a mailer daemon response, that got sent to all ~800 people in my grade, some of whom promptly started replying to all. Eventually a couple kids started sending edgy memes, so I was called into my dean's office and asked to forward them the whole thread so that they would know they weren't missing out on anything "dangerous" (I think the main one they were concerned about was a picture of someone shooting a gun with the caption "I would literally die if a guy did this to me"). Then they locked down the capabilities on the google group, so no more unapproved email campaigns :(