ack3 VS Advent-Of-Code

fyi ack is like this but for perl instead of python https://beyondgrep.com/

If you just need a single shell command you can do :!. Example:

:!ack "stupid_structure->who_wrote_this_crap.oooohhhhh\s+="

(and if you wonder what "ack" means: https://beyondgrep.com/)

Ack is consistent with grep but will sensibly handle the recursive stuff for you.

Scan the file tree containing the website for the links, or part of tje links, for example with ack which is an easy to use, recursive reimplementation of grep.

I've thought about redoing ack in Python but it wasn't any faster than the current Perl.

Ever hear of ack it might be a faster alternative.

No, but thanks for pointing out its existence. Homepage:

https://beyondgrep.com/

(ack comes from ack-grep, a better version of grep, but you can just replace it with grep -r)

I've been a fan of ack for quite some time.  Somehow (and I'm not quite sure how) once or twice it's found stuff in source code that VSCode simply misses (likely I was searching wrong with VSCode).  And there are a few things I've found that make it even more effective in searching Elixir code that I thought I'd share.

Very much agreed. I'm a developer and I honestly prefer ack (https://beyondgrep.com/) myself. But it has the exact same issue. It's not standard.

Part1 and part2

Solution: https://github.com/tymscar/Advent-Of-Code/tree/master/2022/typescript/day02

Thought about doing it in Typescript this year. You can find part1 here and part2 here!

Today was way easier than the past week which is great, because I can relax a bit. I have rushed the code, so its not the greatest, but its here, in Javascript, if you want to see!

Today was insane for me. Basically spent like 10 hours working on it, but I started from scratch in the last hour and got both parts. I made very stupid mistakes such as reversing the values when reading them or writing a 2 instead of a 3. I am tired, but we are almost at the end! Part1 and part2 in Javascript.

Part1 and part2 in Javascript. Beware, code is ugly, didnt have time to clean it up and it also runs in like 3 minutes... :(

Part1 and part2 in Javascript

Today was very enjoyable, albeit a bit easier than expected after what was yesterday, haha. Part1 and part2 in Javascript

I think today was very difficult because of the way the problem was layed out. Most of what you need to do for part2 was explained in part1 for no reason and the example werent exhaustive. I tried doing it with sets, then I also tried bruteforcing it and in the end I ended up doing a more manual approach which is very ugly but I am too tired to refactor rigth now. Part1 and part2 in Javascript.