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

GOAT?!


this is gold!


someone forgot to put in the Call to action


awesome


nice!


- 4 hours, "this is a very simple exercise"

- 6 hours


What is the limitation on this? AWS lambda has 250M code size limit, 3G memory limit, 512M temp storage limit, how about this?


How big is your Kubernetes cluster?


I have a similar story. I submitted a ticket to increase my GPU quota. Then my account was suspended, because CSR think the account is committing fraud. At that moment, I have a valid payment method and have been using GCP for a couple of weeks. Only after I prepaid $200 and uploaded a bunch of documents including credit card pictures and ID pictures, my account was restored.

You heard me right, I prepaid them so that my account can be restored.

I miss AWS sometimes...


Honestly, if your not big enough to setup invoicing an option to always prepay wouldn't be so bad. If it reduces risks if interrupts.


at 10 years birthday of app engine and 10 years birthday of python3


I like to remind people that Python 3 was already more than a year old when Apple announced the first iPad. I'm not sure anyone should be getting a cookie for 'working on' Py3 support more than nine years later. Though I do understand that GAE has supported Py 3 for a while in its more configurable service.


True, though I have to say it only got usable around 3.4 (which still is 4y.o. at this point)


What did 3.4 give you that 2.7 already had? I have found bundled pip and asyncio useful, but I was using Py3 from 3.2, successfully. It didn't suddenly become usable at 3.4 for me.


I think what happened was that 3.2 was the first "real" release, when a lot of .0 bugs were shaken out; the 'u' prefix was added back around that time too, iirc.

This resulted in more developers actually porting their libraries, an effort that had been basically non-existent before. The result was that the 3.4 ecosystem actually got mature enough that Real Work could get done, and more end-users started moving.

IIRC 3.3 also had some big performance problems that were sorted in 3.4, but I cannot remember the details.

Personally, I did very little with 3.2 but actually built Real Stuff only with 3.4.


Yeah, pip. You could install it manually, but to be honest, pip and virtualenv are fundamental today (I mean, before containers, but still)


To be fair: PEP 3333 that addresses WSGI support with Python 3 Unicode was initially drafted in September 2010. I would consider that to be the first day we can write a web server in Python 3.


any frontend eng from EKS, you should look at the chrome console.

""" Warning: It looks like you're using a minified copy of the development build of React. When deploying React apps to production, make sure to use the production build which skips development warnings and is faster. See https://fb.me/react-minification for more details. """


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

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

Search: