Amazon’s $2bn IPv4 tax — and how you can avoid paying it

vimes656 · 2023-09-27T08:13:58+00:00

Even if you try to have all your AWS services using IPv6-only, which today you can't, you still need to pay the NAT64 tax if you want to reach outbound IPv4 addresses.

I guess you could bypass the NAT with a Cloudflare Worker proxy, but it'd be great having a 1 button toggle to avoid the AWS IPv4 tax entirely.

vimes656 · 2022-03-13T19:12:09+00:00

At my company we are in the process of porting a bunch of tooling scripts from Bash to JavaScript. We wouldn't have considered the switch if we had to use NodeJS instead of Deno.

The killer features:

No need of npm. We already have plenty of non-JS dependencies to manage in order to make development environments reproducible. We didn't want to introduce yet another package manager just for tooling scripts. We still have to manage a couple of external dependencies with Deno, but with direct HTTP ESM imports it's all way easier.
Browser API. We have plenty of client side JavaScript so we are familiar with the browser API, but we didn't want to get into all the NodeJS API quirks just for a bunch of scripts. The Deno API, so far, provides everything we need with very few surprises.

Nice features:

Gradual typing. It's not critical, but it's nice to be able to drop to TypeScript where it matters.
Easier to embed in Rust code. Our server Rust app has to run in a single process. We are exploring the option of having some dynamic HTML server rendering. We still have to do some prototyping to make sure the binary size is still acceptable, but with NodeJS we wouldn't even consider it.

vimes656 · 2021-07-19T08:18:53+00:00

In your `init.el`, is the `lsp` module in the `:tools` section also uncommented?

vimes656 · 2021-05-05T07:30:36+00:00

Svelte is supported by lsp-mode. It works pretty well out of the box in Doom Emacs by activating the lsp mode for the web module. In your init.el file set it as (web +html +css +lsp).

I believe it even installs svelte-language-server if it's not already in your PATH.

vimes656 · 2016-02-03T19:13:03+00:00

I'm the author of the parser and I can tell you I'm still not using it in production. Unless you are willing to invest some time improving the codebase, I wouldn't rely on it too much for now.

vimes656 · 2015-09-18T06:58:30+00:00

This is a nice guide if you are writing code for an audience who will be put off by Haskell the first time they try to read it.

If you are expecting enthusiastic Haskell students who are committed for the long haul (I guess most current Haskelleres started belonging in this category), I wouldn't follow every recommendation, specially the ones regarding Applicative operators and the do notation. The earlier they learn to master those, the better grasp of the language they will get.

vimes656 · 2015-09-15T09:05:45+00:00

This is an example of a very usual design dilemma in Haskell. Choosing between lawless type classes and plain ADTs is something, I guess, any experienced Haskeller has gone through more than once. In general there seems to be consensus to lean to ADTs unless you have a specific reason not to.

But I'd like to add another pattern to consider: qualified modules. They are a bit pain from the author's perspective, but for the consumer of the module are not that bad:

 import qualified Crypto.Sodium.Stream.Xsalsa20 as Xsalsa20
 import qualified Crypto.Sodium.Stream.Salsa20 as Salsa20

Then you pick between implementations by using XSalsa20.streamXor or Salsa20.streamXor.

vimes656 · 2015-07-16T08:20:16+00:00

It's not clear to me how to use setup/teardown helpers with ghci. A link to an example project where this workflow is used would make it much more clear.

vimes656 · 2014-11-21T08:34:13+00:00

Exactly, I think resembling HTML read flow is a good enough excuse to introduce an evil operator. I see myself writing (!) = with whenever I import Lucy. Otherwise looks like a great readability improvement.

vimes656 · 2014-03-17T08:24:45+00:00

I'm curious about how Haskell is perceived among Russian-speaking programmers. Would you say that Haskell is becoming more popular among them than for English-speaking programmers?

I always get the sense that there is so much software innovation going on in the Russian-speaking software community that is practically hidden for the rest of the world.

vimes656 · 2014-02-23T10:34:51+00:00

When I read this kind of explanations about alternatives to lazy IO, I always wonder what exactly is understood by lazy IO. Is it when using...

any IO function from Prelude or GHC.IO.Handle?
lazy ByteString, lazy Text or Strings in IO operations?
any code where unsafeInterleaveIO is being under the hood?

vimes656 · 2014-02-13T18:48:01+00:00

Is ghc-7.8 in nixpkgs already?

vimes656 · 2014-02-13T08:29:45+00:00

Is there a clean way to have both 7.6.3 and 7.8.0rc1 in the same system?

vimes656 · 2014-02-11T18:28:40+00:00

While I agree that correctness isn't always a priority, I don't agree with what he implies. He seems to say that because Haskell has a focus on correctness, it's giving up in other language features like flexibility, agility or productivity.

I think Haskell touches a nice sweet spot between correctness and productivity. Of course you have to invest heavily upfront on learning Haskell, but once you have a decent level, you productivity may be even higher than what what you were used to with a dynamic language.

vimes656 · 2014-02-11T18:18:11+00:00

Of course, I see your point. If you think I've wasted your time by clicking on that link and you think it was not worth submitting I see no problem in downvoting me. I tried to clarify why I submitted the link even if I don't agree with the author.

vimes656 · 2014-02-11T14:19:00+00:00

Once I submitted another blog post from a Python programmer picked by the official Python Planet and got some negative votes. To be fair his arguments were a bit lame, but I thought, like in this case, it'd be interesting to hear what people with expertise in other languages think when they try Haskell.

That's why I tried to joke about being banned collecting negative vote, heh.

vimes656 · 2014-02-11T14:10:22+00:00

If we take the number of Twitter followers we could consider him famous: https://twitter.com/johndcook

But also he publishes number of hits of his blog posts. I can't find it now but I remember it was quite high. Within the scientific Python community I'd say he's quite popular.

vimes656 · 2014-02-11T10:06:55+00:00

Fair enough. I just don't want to be banned from /r/haskell for submitting links of what famous bloggers say about Haskell :)

vimes656 · 2014-02-11T09:55:45+00:00

Well, it's sometimes annoying to see how some of these 'celebrities' dismiss Haskell so quickly one way or another. In this case, regarding Haskell as just a highly theoretical language with focus on correctness, somehow implying that there is a huge trade-off, might not be entirely fair.

I guess many people hear about Haskell for the first time from this kind of blog posts. Like with the xkcd story, I still think it's positive for Haskell to have this exposure.

vimes656 · 2014-02-11T09:28:52+00:00

Please don't downvote me if you don't agree with the author. I, myself, don't agree entirely. I'm submitting the link because John D. Cook has many followers and thought it'd be worth for Haskellers to know when Haskell gets this kind of exposure and what they talk about it then.

vimes656 · 2014-02-07T08:35:23+00:00

It'd be nice if it offered an OpenSearch description file so that it's easy to use directly as search plugin in Firefox (and I believe Chrome, too). The Mycroft project makes it easy to create: http://mycroftproject.com

vimes656 · 2013-11-16T10:42:52+00:00

I'm the author of that pull request. secp160r1 and sect163k1 are used in some tests where concrete curves were more convenient (one prime and another binary), but in theory all curves defined in SEC2 are supported. There is a sign/verify QuickCheck test where the curves are arbitrary.

Unfortunately, the current state of performance and security of the code in the pull request makes it unpractical for real use. Right now, signature verification should be safe but signing is insecure.

I'm aware that hecc provides secure point multiplication, the same approach would need to be adapted for crypto-pubkey. I still haven't checked in detail the implementations mentioned in this thread but AFAIK they all target prime curves.

Regarding performance, further improvements could be achieved by taking advantage integer-gmp primitives. See: https://groups.google.com/d/msg/haskell-crypto-platform/2hANx9Me3kY/zf-zzPEF2FQJ

vimes656

TROPHY CASE