firebacon

13 ms·

61.
by firebacon 8y ago
> I'm not sure what your point is with `env_logger::init` That most of my programs have some global (i.e. "for the runtime of the program") stuff that is setup at the beginning of main. And that some of that might want to
62.
by firebacon 8y ago
Yes, currently doing something similar to that, but I'd much rather have it as a first-citizen feature. Returning result directly from main sounds very interesting! I will have to look into that thx. EDIT: I assume you mean RFC1937? Lo
63.
by firebacon 8y ago
std::process::exit does not call Drop traits (at least the last time I tried -- maybe I am doing it wrong?). So for example, if you're relying on Drop to clean up temporary files in the system, that will not happen. Providing no method
64.
by firebacon 8y ago
Just yesterday our build broke because a cargo update pulled in some dependencies that suddenly required experimental features. I think it was crossbeam via hyper or tokio. Also, while I recognize it's a third party project, the hyper
65.
by firebacon 8y ago
The types of values and legal conversions between them are well defined in C -- the assumption that everything is just a block of bytes and hence may be casted freely between types is explicitly incorrect (and is what may lead to bad/
66.
by firebacon 8y ago
If we are being pedantic, what is going on here is not type coercion. If it were type coercion, we would expect the add function to have either of these two behaviours: - coerce the input arguments to strings, i.e. implicitly accept two
67.
by firebacon 8y ago
The result add(1: Int, "2": String) -> "12": String can be achieved in any language, regardless of how strict the type system is. All your example shows is that in elxir no such `add(int, string)` operation is provide
68.
by firebacon 8y ago
> Does anyone make weakly typed languages anymore? I don't think anybody ever did. The definition of "strong" and "weak" seem to be entirely subjective; and of course everybody considers their favourite language
69.
by firebacon 8y ago
> Were there tools that helped keep all the services running together in a single machine? Traditionally, services on unix system are started and supervised directly by the init process ("init system"). That has been SysV init
70.
by firebacon 8y ago
That is a very interesting counterpoint! I guess I agree with you if the choice has to be between {Google, Amazon} or "only Amazon". But I'm advocating for the third choice, where we continue (or go back) to running our own i
71.
by firebacon 8y ago
Don't think the term "container" is really well-defined. The "container" that docker and others implement is actually a collection of different kernel namespacing features. I assume the one you are referring to are
72.
by firebacon 8y ago
You don't have to prove anything. Nobody is on trial here, I hope :)
73.
by firebacon 8y ago
> Which part of kubernetes is "developed with the intention to eventually get you to use the hosted version"? I believe it's all of it. Why else would they spend money on building and promoting it?
74.
by firebacon 8y ago
Well I agree that the interests are aligned insofar as Google is trying do dethrone AWS which currently has a near-monopoly on cloud. But I'd still rather live in a world where the compute fabric of the internet is not centralized in t
75.
by firebacon 8y ago
Well yes, you can replace Google with like two or three other companies in my comment. At the end of the day I don't like the trend of outsourcing all the interesting bits of technology to a handful of mega corporations. I think it is
76.
by firebacon 8y ago
I agree that running kubernetes ourselves does actually serve our own interests. But I still think it's much more of a slippery slope than alternative solutions (being that some of them are not developed with the intention to eventua
77.
by firebacon 8y ago
Well I am sorry if you felt the wording of my comments was too "aggressive"; personal angle is weird though. Also I think you are trying pretty hard to misunderstand what I am trying to say. Obviously, using google's hosted v
78.
by firebacon 8y ago
I think the kubernetes project is heavily driven by Google marketing, and that they are not doing this out of charity, but because they are trying to get you to use their cloud platform in the long run. They know getting somebody to build t
79.
by firebacon 8y ago
I'm not sure I understand this. You have a product that is split into many different components, and when you deploy this product to a customer site, each component runs on different hosts, so you have a bunch of wiring up of service a
80.
by firebacon 8y ago
No it doesn't. You can not extrapolate from the fact that the hosted version "just works" that kubernetes at scale would also "just work" (kubernetes being the open source product that you run yourself here). Especi
81.
by firebacon 8y ago
How does this relate to my point that you're transitively paying somebody else to do ops for you? Maybe google's pricing model rolls this into the normal VM price? Or maybe it's currently offered at a loss to gain traction? O
82.
by firebacon 8y ago
The difference in simplicity is not in the interface that is presented to you as a user. The difference is that your shell script will have a couple hundred lines of code, while the docker and kubectl commands from above will pull in litera
83.
by firebacon 8y ago
> But the parent's comment is missing the point That was my point. I wanted to point out that while some people have only/first heard about failover in the context of kubernetes, it is not something that is specific to kubern
84.
by firebacon 8y ago
You mean a failover solution? It's hard to give a list here because it is such a large space and it completely depends on your product/application. It is more like a category of use cases than one specific use case. Some ideas for
85.
by firebacon 8y ago
> makes economic sense [...] for our current team. But the reason for that is not that it makes "hard problems go poof at scale". The reason is that you're using a hosted service where somebody else (in this case, Google t
86.
by firebacon 8y ago
Nobody wants to wake up at 1AM because their singly-homed service just went down. Kubernetes might be a fine tool to achieve that, but I want to point out that there are much simpler failover solutions available. Failover is something you
87.
by firebacon 8y ago
When you notice that you spend such significant money (i.e. multiple salaries) on hardware capacity planning that employing a team to operate kubernetes might be cheaper instead. Probably not going to happen unless you run on hundreds to th
88.
by firebacon 8y ago
> because a lot of hard problems at medium scale and above just go poof with K8s. No, they don't? I don't know why anybody would just assume that something as complex as kubernetes would just run flawlessly once you actually tr
89.
by firebacon 8y ago
I think the recommendation is not to use another orchestration service, but to keep the infrastructure simple and not use any orchestration or service discovery at all. Adding service discovery and container orchestration will probably no
90.
Build2, a Cargo-like dependency and build manager for C/C++(build2.org)
157 points by firebacon 8y ago|52 comments

More ›