HN user

chrisohara

232 karma

https://github.com/chriso https://linkedin.com/in/chris6f

Posts16
Comments54
View on HN

Io in zig is for “things that can block execution”. Things that could semantically cause a yield of any kind. Allocation is not one of those things.

The allocator may yield to the OS when requesting or releasing memory (e.g. sbrk, mmap, munmap)?

Sherlock (sherlockscore.com) | Full-stack (Rails/React) | REMOTE | Full-time | $90k – $150k

Sherlock is changing the way SaaS businesses understand and operationalize their product engagement data. Built by a team of SaaS veterans, we are the only product engagement scoring application on the market today. We have found success with our early customers and are ready to expand the team to accelerate our growth. We offer a competitive salary and benefits and are excited to build out the team further.

Email chris@^ or apply here: https://angel.co/sherlock-4/jobs/488709-full-stack-engineer

I think it's referring to the fact that certain details (traffic, DNS requests, timestamps, IP addresses) are logged. Ideally you want a service that does not log anything, that's why "Yes" is red.

Tagging would be the next addition. I added the ability to search for keys by prefix quite efficiently, so provided one stored keys like "requests:server1", "requests:server2", one could easily run the following

    requests = 0
    for key in gauged.keys('requests:'):
        requests += gauged.aggregate(key, Gauged.SUM, start=-Gauged.WEEK)

It's pretty negligible in the scheme of things. I was abusing PHP reflection a while back to add decorator support (https://github.com/chriso/Request) and used this pattern to reduce the cost:

    switch (count($args)) {
        case 0: $method(); break;
        case 1: $method($args[0]); break;
        case 2: $method($args[0], $args[1]); break;
        //etc
        default: call_user_func_array($method, $args); break;
    }

Why are people so scared of void*? Are there any VM's that don't resort to some form of pointer tagging when implementing dynamic typing?

It's a project created and maintained entirely in my free time. I provide free support when someone needs help and I fix bugs when someone files an issue. I've written documentation and a guide in the project's Github wiki. This is all done outside of full-time work. Forgive me if I don't spend more time improving the website and uptime when it's an endeavour that brings me no income whatsoever. You're the type of person that makes me hate open-source sometimes.

Of course it has a backend, but so do the Firebase apps that this entire thread is talking about. Referring to a JS app as "client-side" doesn't imply that there's no backend logic.

My point is that you can't just de-obfuscate a primarily client-side JS app and replace the Firebase (or whatever) endpoints. Proprietary obfuscation is more than just variable name munging and minification..

as I said above, de-obfuscating a large javascript app that's been obfuscated/minified by proprietary tools is virtually impossible to decode. Try running some of google's code - gmail, docs, take your pick - through your beautifier ;)

How are they not picking it up as spam? The same affiliate link from multiple accounts... The description also looks like a snippet of one the product reviews on Amazon

Dart won't be supported ubiquitously any time soon (if ever) which is why there'll always be a Dart->JS compiler. Why not just stick with vanilla JS or Harmony/ES6? I'd benchmark some bigger apps but they don't exist yet