paulmillr

It's not that complex once you have formulas for computing square roots. I've recently implemented it in TypeScript using bigints for browsers & nodejs. Quite readable & performant. See index.ts file here: https://github.com/paulmillr/noble-ed25519

Wish ristretto folks added the library to their website though.

It's fair to say that this is still a theoretical attack. As authors of this paper mentioned, they don't see a way of turning the "flaw" into a real exploit.

How about a full web application for REST API in Brunch?

Check it out: http://ost.io https://github.com/paulmillr/ostio

Thanks for feedback! We'll adjust some wording. We are always looking for ways to improve the docs / product.

The legality part is interesting. If it's "illegal", but widely used, it makes the regulation wrong, not people, does it?

So this thread disappeared from the top and all pages besides Newest.

But I see post on page 3 from 3 hours ago with 3 upvotes so this should be somewhere on 1-2nd page.

HN mods don't like criticism?

As for maxima — yeah, definitely. Done.

Actually, I tried, just when CoffeeConsole was released.

https://github.com/snookca/CoffeeConsole/issues/2

Back then I failed. It seemed like Chrome didn’t exposed full console and window api to extensions or so. I doubt things have changed since then. But i’ll try anyway.

I had also advocated for improving built-in Safari web inspector, to make it expose reasonable APIs for extensions like this (radar issue #11653556). Unfortunately, without any result.

As i’ve noticed in repository readme, Chrome coffeescript addons cannot manipulate DOM or play nicely (or even reasonably) with window properties. They’re just shortcuts for coffeescript.org, which just compiles coffee down to JS. This seems useless to me, because I want coffeescript as first-class browser citizen.

Yeoman and Brunch have many differences. You can read the small essay on them here:

https://github.com/brunch/brunch/issues/408

Bower support is coming to brunch in the next release.

That's simple: brunch is a project builder.

You put vendor styles / scripts in `vendor`, then you edit your `app` files. No matter what language you want to write, brunch will compile it on `brunch watch` or `brunch build`.

Of course you can make some sophisticated makefiles and connect sophisticated file watchers there (brunch fastly rebuilds project on every small change), but why do this when there's brunch which just works?

here's the even better example app

https://github.com/paulmillr/ostio http://ost.io

backbone + coffee + chaplin + brunch + rest api + nested models / views + collectionviews + controllers (+session controller with GitHub auth) + actually a real-world application

That's what http://brunch.io/ exactly is for.

It's an early version. Maybe, currying would be added in one of upcoming releases.