We never wore sunscreen as kids because we didn't burn. I probably have had three sunburns in my life. Learned once I became an adult that that wasn't sound logic...
7,488 karma · joined November 1, 2019
We never wore sunscreen as kids because we didn't burn. I probably have had three sunburns in my life. Learned once I became an adult that that wasn't sound logic...
I sympathized with them when they said this a handful of months ago, but then I saw this [0] page that shows how it's been shot for years prior (which tracks with my memory).
I feel for the GH engineers that have to deal with this, especially the SREs. I also don't hate the downtime right now, as I'll make a cup of coffee and do something else. I will say though, I did have a hotfix a week or so ago during the Actions outage, which really was a pain.
You're right that getting angry and ranting isn't the right reaction here, but I do no give them the LLM load excuse. I don't give them an out for having awful uptime during work hours for a product we pay quite a bit for as an org.
It's a shame I had to go to HN to check if I was the only one instead of relying on their status page that they link.
I'd like to get back to having a desktop email and calendar client over using a browser all the time.
I find the performance to size ratio of these models to be way more interesting, selfishly because it makes me bullish on what I'll be able to run on a machine I own over the next few years. The progress is just incredible.
Why do we assume that Mistral is a "good guy" protecting themselves? I'm not sure they necessarily are. Could just be trying to grab any ground they can.
I mean, maybe they are the "good guy", but I don't think we know either way.
I explained to him how the EC2 instances would assume the role that already had the permission and it took so long to convince him.
Needless to say, we had to explain lots of basic security and networking concepts to him, which he wouldn't believe until given live demos of basic things like public versus private IP addresses in AWS.
Alibaba, Google, Moonshot, Thinking Machines, etc are not releasing their models for free because they love to. They want to grab market share. I'll take it.
I still will not use a hosted Meta product, but damn this model looks solid.
Now, I don't know how MIT -> AGPL re-licensing specifics work, but still.
This is a man who's spent a significant portion of every day for the last 15 years on GitHub.
I'd love to know what the most common root causes for these outages are.
Selfishly of course so I can make sure there are more episodes of Oxide and Friends for years to come. Adam annd Bryan's ability to reference thirty year old simpsons episodes is unmatched.
If my e-reader had a bad battery after years of use, I should be able to replace that battery myself without issue (personal skill allowing). I purchased it. Why wouldn't you be able to? I haven't yet found reason for this in consumer devices, except because they want you to send it in or buy a new one from the manufacturer.
Every time we see something like this, it doesn't get enough eyes or care from those who use these platforms. Sony takes your movies away, Xbox requires you be online, Amazon updating your books automatically without asking you, etc. My favorite that I repeat constantly is all of the BS that BMW has done over the years: heated seats subscription, proprietary bolt heads, ads in the infotainment. If you buy a BMW at this point, I'm sorry, but you had alternatives and I don't feel bad. The scary part is when enough people accept it that everyone else in the industry follows suit and then the outliers are the ones that respect you.
If I purchased a physical disc, I'm not even asking for the source code (which I'd love), I'm just asking that I can run the damn software I bought, but you can't even do that now. Viva open source and right to repair. Make the educated choice when purchasing software and hardware, to your benefit, where appropriate. Of course, the proprietary system is what you need/want sometimes, but I bet most of us don't most of the time.
Half the reason it's a bummer is because I've seen coworkers who don't know when a regular expression is very suboptimal performance wise, but the LLM has no problem spitting it out. Part of really understanding regular expressions is knowing when to not use them.
The one that sticks in my head is when I was debugging some code that I was suspicious was causing our high memory consumption on a simple API service just to find out the regular expression was being used to strip a potential "data" front of a base64 encoded file (apparently someone thought we should do that instead of rejecting the payload). The regular expression scanned an entire base64 string that was up to 50 MB for the raw file, so about 66MB base64 encoded. I'll tell you what, replacing it with a loop over the first handful of characters solved all the problems. It should've never been a regular expression. If you see regular expressions as an archaic language that solve string problems, and now the magic box can make them for you, you're in for hell.