You're just skipping the app and handing it directly to the ad company.
489 karma · joined June 11, 2014
You're just skipping the app and handing it directly to the ad company.
Neat project!
https://doc.rust-lang.org/cargo/getting-started/installation...
I do like this idea though and think I have an application for it.
Unless you're a PaaS company with a large SRE or Ops team off the bat you likely own't have the resources to maintain a k8s cluster. It's a great piece of tech but it's quite complex and has a decent amount of overhead. So unless you happen to have an expert already on your team or your already have a bunch of services it's probably not worth the effort.
import pdb; pdb.set_trace()
is totally a thing. And ipdb is even better.I would move the download buttons up to the top though. I missed them my first few times.
kubectl config set-context your-context --namespace some-namespaceI imagine the other models are also pretty good.
It does.
Kubernetes is a great piece of tech but it is pretty complicated and does add a fair amount of overhead on top of whatever operational concerns you application already has. If you don't have anyone that knows how to build and manage a cluster going to production with it would be extremely risky IMO.
I would recommend trying GKE, Google's managed k8s service, in staging/dev before even considering it as a serious path forward. If you are married to AWS or just don't want to use GCP then kops would be your best bet. I have friends working with EKS, AWS' managed k8s service, and it doesn't sound anywhere near as ready as GKE or as flexible as doing it yourself, frankly it sounds like a real pain. I haven't used k8s on Azure but I have heard that it's pretty good.
I also don't generally recommend deploying a new application as decomposed services either. Unless you have done this a bunch of time it will probably save you a bunch of time to just do it as a monolith and deploy it to standard cloud VM's or on-prem servers. Also be aware that Docker and by extension k8s are not the best way to run stateful applications. It can be done but it is definitely more work to get a k8s based DB working the same way as a non-k8s DB in terms of data retention. I imagine a complex application will need some kind of data store so even if you go with k8s you may still end up with non-k8s instances for you data.
k8s is great but it's overhead con easily outweigh it's benefits if you don't have a someone who can manage it. Start simple if you can and work from there.
If you're in the 10% yeah it can be a pain in the butt. However it's not impossible or even particularly difficult to migrate to something else.
This isn't Obsessive Compulsive Disorder it's being thorough or knowledgable. No need to further the misuse of this term here.
My last company was in an office park in the middle of no where and I don't drive. There were no stores within walking distance either. So if I felt like having a snack or something to drink that wasn't water I'd be SOL. So it was nice that we had snacks and drinks available and made working in such a remote spot much more tolerable.
I would love to be running Linux on it but the IT department in most places I've heard of won't let you replace OSX. Places that also offer Windows laptops for devs won't let you put Ubuntu on it either.
So I use my MBP with it's stupid emoji bar and an escape button that can crash at work and my System76 laptop at home/everywhere else.
I believe identifiers in those languages have to be ascii characters but I'm not 100% sure. Go however allows any valid unicode character for variable names. The rest of the language is in English though.
Valid Go w/ variable in Japanese: https://goplay.space/#whU6ErYq_wR
My father has an email account solely because an Android phone makes you get one. He definitely doesn't know the password and I wouldn't be surprised if he didn't know the address either. However he is very comfortable taking pictures and attaching them to text messages.
He can easily save a contact in his phone on his own. I or my brothers would have to help him set up a bookmark in a browser. Now my father may be somewhat of a Luddite but keeping the barrier really low for family members who aren't texh savvy is a good idea for this.
And as far as quality I can almost guarantee my grandma doesn't care what is in the pictures or how blurry they are. She is going to care that I am sending her something. That's the important part not HD images.
Great idea
IMO this is actually a really good decision given the purpose of the service. A lot of my older family members that I will likely invite to my new account (great idea btw) are familiar with sending pictures through SMS and don't really use any other messaging apps or many apps at all, if their phone even supports apps. Believe it or not many older people and some younger people still rock low powered phones with little or no data plan. However most if not all phones made within the last decade can send SMS messages and more than likely are on a plan with free texting.
Why should I need to download another app that is a glorified REST client when SMS does the job perfectly well?
> Good luck getting users to adopt your software, though, regardless of how privacy-conscious they say they are.
It would probably be difficult mostly because we have trained users that an app isn't useful unless you can sync it to all your devices. We are always going on about how much better things are once you can connect them to everything else on the planet. We've sold users on the idea that they need to be connected all them time and we need to know everything that they do so we can "improve their experience" which for most things means "show you ads."
I'm not knocking webapps in general. I make them all the time. Some of my favorite things are webapps. I'm writing this comment on a webapp. I just also believe that not everything needs to be a webapp and have a constant connection to some server telling it about everything I'm doing.