kag0

Awe, the script version doesn't have ligatures. Some people think I'm a weirdo but I really like having my keywords in ligatured script and the rest of the code normal.

how to not use them is editor dependent.

but you absolutely don't have to use them.

regular fonts are basically "use this image for 'a', this image for 'e'" etc. ligatures are extra data that says "if you find an 'a' next to an 'e', use this other image in place of the 'a' and 'e' images". but the non-ligature versions of characters are still in the font for use when there is no ligature sequence (just put a space in the middle of any ligature in your editor and you'll still see the independent characters rendered in the font).

As an anecdote in the 90s and 00s "import" cars usually meant Japanese cars, especially ones not available on the US market. This wasn't really a negative connotation, and there was a whole scene for high performance "import tuners". Just interesting to your point that in context "import" implies a specific country.

I would say that the only pruning of the graph which matters is that which is done by your fellows.

An orchard atop a cliff presents an equal challenge to all. Some might have the ability and desire to scale it, some not.

What is the difference between a fence around an orchard and a threat of insurmountable violence if you enter the orchard? Either way it is someone else restricting your freedom, while they retain that same freedom for themselves.

That's an interesting way to look at it, but I take an issue here

> How free you are is then expressed as a graph of all possible actions you may take which are not prohibited by the threat of legitimate violence

It's a good point to think in terms of possible actions you may take. But violence isn't the only thing that can prune that graph.

Say I come across an orchard surrounded by an [unclimbable] fence. I want to eat some fruit in the orchard, but cannot because of the fence. There is no violence I face that prevents my action, and no violence I can level to take the action. Yet my action is prohibited by another, and thus my freedom limited.

It's more of an issue on the end user's side. All the main browsers have had support for ES6 and newer features for years. But that doesn't mean end users are running the latest versions of those browsers. So when you transpile/polyfill a feature, you're aiming to support that small number of users who haven't updated their browser in 5+ years. If you don't care about those people, you have no need for that intermediate step. Or if you want to be really sophisticated, you can look at the user agent for an incoming request and serve a response that's transpiled/polyfilled exactly as much as is needed.

An interesting concept and awesome work!

I searched for high pressure air (HPA) regulator trying to find a description of how one works. I didn't find that, but did find some interesting links on how they're used in scuba, and one guy's homemade gas laser.

Totally unrelated to this cable, but since you mention it...

I've been trying to build web/single page applications using new ES modules and no build tool, so all dependencies are pulled from their creator/CDN rather than bundled locally. Would this set off flags for a no-script user?

I was about to post that exact link, as I just completed the course as a prereq for SAR.

Here's all the content on one page, I found it less intimidating than the 50 slide format https://emilms.fema.gov/is_0100c/groups/133.html

What I'm surprised by is that a decade later we don't have better off-camera raw to jpeg conversion tools (or at least I haven't used any great ones).

It should be possible to feed a bunch of raw files to a program and get back a) the exact same jpeg that the camera would have produced and/or b) an even better jpeg than the camera would have produced, given the significantly greater hardware resources available. Expanding even more, given a relatively stable exposure bracketed burst shot, we should be able to get a very good hdr jpeg from two or three raw photos.

note that I'm talking about doing all of this automatically. of course we can get a great jpeg from a raw with some quick work in lightroom, but that shouldn't be necessary for many images.

> In July 2019, after the release of version 2.13.0 of the Scala 2 compiler, and with Dotty (Scala 3) already in advanced state of development, the authors concluded that the TypeLevel fork had served its purpose. New contributions are best forwarded to the Lightbend's compiler fork.

>> The way I see it, the TypeLevel compiler was very useful for trying out and refining features that have found their way into the mainline compiler afterwards. (by Martin Odersky

As a Scala user (with not much awareness of the big players in the community), I think the fork worked out nicely. I enjoy the features in Scala 2.13 that were stimulated by the fork. With the impending release of Scala 3 it probably made even more sense to discontinue the fork rather than use it to seed more new features.

> BackBlaze is definitely a SaaS company

agreed, but I think s3 is the more realistic comparison than dropbox

A two way handshake/challenge would be the ideal way to solve that.

ie. the patient would scan a qr code (containing a nonce) on the checkpoint, and include that number in the token which was then shown to the checkpoint.

Any reading you can direct me to on people implementing NFTs for authenticity of physical art? I've seen it discussed casually but haven't come across anyone seriously looking at doing it in practice.

The flexibility comment wasn't intended as an insult to people who dislike / don't understand NFTs (or to anyone, maybe just a jab at NFTs themselves).

Anyone involved in NFTs for physical objects (other than say, landmarks or some other abstract concept) has missed the point of NFTs. Which is understandable, since that point requires a bit of mental flexibility to grasp in the first place.

I wish they talked more about how they solved this

> inequality that we didn’t realize before: people with small apartments, young kids, or living alone were hit harder than those living with relatives and enjoying a large house.

they mention

> Giving employees help to set up their home office

but I don't think that really helps those issues they listed

I think you've answered your own question.

People who feel positively about their home life are inclined to maximize it by working from home. People who feel negatively or have little home life are inclined to get out and seek social/private opportunities at or around the office.

Note that feeling negatively or having little home life is meant to encompass a range of situations that don't necessarily mean someone has a bad private life or that they're unhappy with their private life.

I wish this said how many of those hit again also paid again. I find it easy to believe that you could be hit twice in a row despite your best intentions, but hard to believe that you'd need to pay the second time if you had established a backup solution.

Hardly. There are many philosophies that argue that the greatest good lies with how we interact with the other.

And on a purely primal level it's common to prioritize one's offspring over one's self. I think most cultures recognize this intuitively.

From another comment, it looks that mantra will become law in the US

https://cisomag.eccouncil.org/paying-ransom-is-now-illegal-u...

Others have done ballpark figures based on what you've said. And as someone who has lived in San Francisco making even less at times, I agree that you should be able to build up at least several months savings.

Unless: you have some crippling college debt ($20k/semester*8 semesters paid over ? years), or have a persistent medical issue ($10k/yr out of pocket), or another terrible corner case that I haven't had the displeasure of encountering.

The idea sounds fun, but I'm a little skeptical of the author's claims that it'll get to 80 degrees with only a small fire in front of it.

It's quite possible the author and I have different ideas of what a small backpacking fire looks like.

Obviously no company should be storing passwords in a way that the password can be determined from storage.

But the one (unlikely) case where these emails would be permissible is in first time account creation, where the user didn't set their password when the account was created (maybe it was created by an admin). If a one time (hopefully expiring) password is generated, stored securely, and simultaneously sent to the user then some of these are acceptable.

> which verb makes the most sense

I think that's a valid discussion. Each method has specific semantics in the HTTP spec, and consumers of an API (both automated and human) will expect you to follow them.

For example, I expect to be able to retry a PUT request without much concern. But if I'm not able to do that then that's a problem that would have been worth a discussion.

You could check out Scala for

JavaScript Developers https://docs.scala-lang.org/scala3/book/scala-for-javascript...

Python Developers https://docs.scala-lang.org/scala3/book/scala-for-python-dev...

Java Developers https://docs.scala-lang.org/scala3/book/scala-for-java-devs....

for a quick introduction

I agree. But would note that scala 3 is compatible with 2.13 libraries, so long as they don't use scala 2 macros.

I think scala 3 is ready to go for production use, but it did come out yesterday. So waiting a tick would be prudent.

The difference is liability. If something happens due to the bank's app, the bank is liable. If you give your account credentials to some third party and something happens, that's not the bank's problem.

This article has nothing to do with 5G. It only passively mentions that Shanghai has fiber and good 5G coverage.

Given the trick they use to prevent you from using the browser back button, I was expecting it to comment "subject is trying to escape!"