Moreover, I believe you should be able to build your project without expecting npm to host all your dependencies ~forever and being online when you need it.
563 karma · joined February 19, 2014
Moreover, I believe you should be able to build your project without expecting npm to host all your dependencies ~forever and being online when you need it.
What about iOS?
That's totally okay! I love when people share their "works on my machine programs". Just say upfront that it's your personal tool so others won't expect production-grade software.
The code might inspire others, let others fork it (if a license says it's okay), teach code readers about some technique or tool, or just be fun to poke around.
I, for one, learned about pyxhook while reading your code. Thank you!
This. My first thought when I saw the indentation hack was "it can't be serious, production-ready software".
My take on this is as follows.
If you have a simple use case, write your K8s manifests directly.
If you have a complex use case, Helm is often more pain than it's worth. Use alternatives, for example Jsonnet[0] with kubecfg[1]. Or emit manifests from your language of choice. Just don't use Helm.
[0]: https://jsonnet.org/ [1]: https://github.com/kubecfg/kubecfg
> 2. Make a blog post and share on HN
> 3. Let the commenters tell you everything you did wrong and what they would have done instead
It's called Cunningham's Law[0]:
> Cunningham is credited with the idea: "The best way to get the right answer on the Internet is not to ask a question; it's to post the wrong answer." This refers to the observation that people are quicker to correct a wrong answer than to answer a question.
It's more like a consumer loan than a subscription in my eyes.
This way it's easy to write and maintain. Looks okay. Fast feedback cycle during development. No need for build steps. Works in browsers without JavaScript. Works well on desktop and mobile devices.
Highly recommended if suits your needs.
I have a few services on my family server (say, Gitea, Grafana, finance tracking app etc.). I'd like to have a SSO but also limit which users can use which services (e.g. my significant other can use Grafana but no Gitea).
Is integrating above services with Keycloak enough? Or would I need another components? Or maybe I've got it wrong and should reconsider the architecture?
ctrl+l → focus the address bar
[0]: https://nixos.org/guides/building-and-running-docker-images....
Is it actually the case?
The comment you cite says the code won't work on xterm or gnome-terminal.
I've checked with what I had available: XTerm(330) and GNOME Terminal 3.30.1 using VTE 0.54.1. On both terminals the last code sample from the post works perfectly fine as far as I can tell.
What terminal should I use to see improper behavior of the program?
> A perpetual fallback license is a license that allows you to use a specific version of software without an active subscription for it. [0]
There are some details about which version you are eligible for. The spirit is that if you subscribe for ≥ 1 year, you have some version available when you stop paying.
[0]: https://sales.jetbrains.com/hc/en-gb/articles/207240845-What...
On the other hand, one has to be super careful about privacy, security, NDAs.
The landing page looks decent.
All invite codes got used up (or there is an error when using above codes). Or is it a part of a challenge? ;)
I'd like to DM you but there is no such functionality on HN. I'd contact you via other means but there is nothing in your profile :)
[0]: https://steve-yegge.blogspot.com/2008/09/programmings-dirtie...