Hacker Newsnew | past | comments | ask | show | jobs | submit | shae's commentslogin

For source code diffs where a tree sitter grammar exists, difftastic is the best choice by far. It's better than you think it is.

https://github.com/Wilfred/difftastic

No really, if you haven't tried it, it's better than you think it is.

https://www.scannedinavian.com/tools-built-on-tree-sitters-c...

(I know, already mentioned later in comments by leeoniya, still deserves a top level comment!)


I've read lots about content defined chunking and recently heard about monoidal hashing. I haven't tried it yet, but monoidal hashing reads like it would be all around better, does anyone know why or why not?


At the 2018(?) ICFP, I sat between John Wiegley and Conal Elliot. They talked about expressing and solving a programming problem in category theory, and then mapping the solution into whatever programming language their employer was using. From what they said, they were having great success producing efficient and effective solutions following this process.

I decided to look for other cases where this process worked.

I found several, but one off the top of my head is high dimensional analysis, where t-SNE was doing okay, and a group decided to start with CT and try to build something better, and produced UMAP, which is much better.

In short, this does work, and you can find much better solutions this way.

(random link https://stats.stackexchange.com/questions/402668/intuitive-e... )


> you can find much better solutions this way

... because mappings map nicely to functions


I suspect the H pattern they mean is where the gear shift is on the steering column, not on the floor. I long ago owned a 1945 Dodge truck with that shifting setup.


Nope, but I appreciate the effort. I threw the H-pattern reference in there without thinking about it too much mostly to differentiate the reference from situations where you're shifting but it's not with a lever.

(I've been stuck on planes for 20 hours with little sleep, so ignore it if it doesn't make too much sense lol)


When you finish the game you get the credits for who created it.

There's also a threejs reference in a hard to reach area.


I put my trust in someone on a case by case basis, unless they're going to cheat someone. Then I don't trust them.


What if we train them and they leave?

What if you don't and they stay?


Yup. It's highly abusive behavior.


The easiest and fastest way to get everything installed is ghcup https://www.haskell.org/ghcup/

As for being successful, there are several nice books, and several active forums. I've gotten good answers on the Libera IRC network #haskell channel, and on the Haskell matrix channel #haskell:matrix.org

If you want to get started without installing anything, there's the exercism track: https://exercism.org/tracks/haskell

I've heard good things about Brent Yorgey's Haskell course ( https://www.cis.upenn.edu/~cis1940/spring13/lectures.html ) but haven't tried it myself.


Appreciate the resources!


I'd say this many sensors in a wireless package can do many things.

My first project would be exercise monitoring. You can measure heart rate, blood oxygen levels, and body temperature in one place.

I would then add something fun like comparing beats per minute of the music to heart rate.

I like the creators' suggestion of using the shape of the ear canal for authentication, I bet that's harder to steal off a video recording than fingerprints or a retinal pattern.

I'd also use this for voiceless speech, as the creators suggest.

I could think of more, but I won't be able to afford the dev kit, sadly.


I'd love to buy this, but I can't afford 2500 euro for a personal fun project.

I have previously purchased and written[1] about the Tympan.org open source hardware hearing aid[2], but it's about $300 which I can reasonably purchase.

If this comes down in price, I'd love to build some neat things with this hardware.

[1] https://www.scannedinavian.com/open-source-hardware-hearing-... [2] https://shop.tympan.org/collections/all


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: