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

Most of the times that "move fast, break thing" is more like "move fast, do stupid things".


A very stupid metric, or very useful if you want to know who just wait for emails instead of doing long strands of deep work, with notifications off or not visible.


The binary size is not really important in this case, llama.cpp should not be that far from this, what's matter as we all know is how much gpu memory we need.


Reminder:

Always reflect on who you are associating yourself with, in a cult, company owned group, non-democratic group, activity that marks you as "one of them",etc... you cease to be an individual and become just the fuel behind someone else's agenda and values (neither of which you can control).

Be an individual.



> Crossfit (done properly) is leagues better for your overall health than weightlifting, running, bicycling, you name it.

Says who? Links, please.


My own experience doing all three.


N=1, as someone would say. I asked because if there are real and evident health benefits i expect it to be documented somewhere.

And considering that crossfit isn't anything substantially different that things available in other disciplines (weightlifting, etc...), i don't expect it to be substantially different even in the outcomes.


I would be VERY interested in a VERY detailed description of how they, as a software company, handled this hardware project.


Nice project.

As an aside, I genuinely wonder under which circumstances a CDN will be useful for a static website nowadays. I have a static website that has been on the HN homepage a few times and got picked up by the Chrome mobile recommendations and a nginx/https with slightly tweaked configuration never had a problem handling the traffic even on the smallest DO droplet.

Edit: Thanks for these replies.


The CDN makes the site load faster by caching the content on edge nodes close to the client. It’s not for taking load off the origin, but purely for network latency.


And by caching it you will reduce traffic to origin.


Certainly, but for static pages the traffic to the origin is not a primary concern except for really large amounts of traffic.


What I like about static sites is that you can serve the site in its entirety from a CDN. So you can literally just CNAME www.yoursite.com to yoursite.gitlab.io (or w/e static site host you use). This dramatically cuts down on latency worldwide. It also removes your web server as a single point of failure for short-term outages.


> you can literally just CNAME www.yoursite.com to yoursite.gitlab.io

After so many years I still can't really understand how easily people hand over almost complete control over their site to someone else, just because everyone else does. It's like handing over your e-mail account passwords when LinkedIn started. Yes, CloudFlare, Google and others are helping you, but there is a price to pay that might not be immediately visible.


It seems pretty different from a password because you're not giving control of your domain: if they broke their contract, you could take it back at any time.

That's the other odd part about this complaint: you're trusting a company like GitLab not to break their terms of service, which is a potential factor to consider but also one where they'd have severe negative outcomes to their business if they went rogue. Since you're already trusting a number of other parties, why is this one so much scarier?


> It seems pretty different from a password because you're not giving control of your domain: if they broke their contract, you could take it back at any time.

You are giving them everything they'd need to obtain a DV certificate for your domain, though. You can stop them from using it at any time just by changing the DNS records, but you'd need to wait at least two years (825 days for maximum TLS certificate duration) before you could be certain any certificates they had been issued before that point had expired.


How would you do it without trusting a third party?


You can get some nasty cold starts though. Here's a domain I have that doesn't get any traffic (literally zero):

https://imgur.com/a/dVPQYKC

The first hit is brutal. I won't say the CDN since I'm not an expert, but it doesn't take long to go cold (minutes) and once it's cold even the cached hits are 400ms.

Is 400ms really a dramatic reduction in latency?


The technical reason to use a CDN with aws s3 is so that you can have a custom domain name with https. s3 will do http custom domains, but to get https you proxy it. In this case, you can think of Cloudfront as the proxy.


In all honesty an excuse my french, if they manage not to turn all this in a shìtshow of epic proportions for their customers it would be quite an achievement I think.


Nice project!


Dear friends at Google, since I guess many of you will read this, I have a question for you. Is there any internal discussions going on about what you should do with all the money you are earning once your basic needs are covered and you find yourself with money that could be invested in interesting projects?


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

Search: