[Gitlab Service Disruption](https://status.gitlab.com/) (1 year ago)
[Gitlab Is Having Issues](https://status.gitlab.com/) (1 year ago)
[Gitlab Is Down (now back up)](https://status.gitlab.com/) (1 year ago)
629 karma · joined July 4, 2017
[Gitlab Service Disruption](https://status.gitlab.com/) (1 year ago)
[Gitlab Is Having Issues](https://status.gitlab.com/) (1 year ago)
[Gitlab Is Down (now back up)](https://status.gitlab.com/) (1 year ago)
I hope somebody will rectify this at some point. Jiff seems like a step in a right direction but the syntax is sometimes weird. I guess I’d wellcome something more predictable
I think that EU needs to keep a strong position to be compelling for many people. Therwise many might start to see it as an irrelevant institution.
We are solid in a gray zone where we have to decide where are priorities are. Fair market vs tech dominance in US is a great example. Another one is carbon neutrality vs strong industry in EU. I’m sure there are so many others.
It is just important to keep that in mind when building your business because we can easily slide from one side of this gray zone to the other.
Kubernetes is probably “use postgres”
I see Kubernetes as one time (mental and time) investment that buys me somehow smoother sailing plus some other benefits.
Of course it is not all rainbows and unicorns. Having a single nginx server for a single /static directory would be my dream instead of MinIO and such.
I think that a website or API backend is the first project for many newcomers to Rust. It would be better for them to have first experience with other frameworks such that they are not let down by Rocket as it might cast a bad light at the whole ecosystem.
Rocket looks tempting because a/ it has a nice website b/ it looks feature complete c/ it is similar to Django/Flask which might make it more familiar d/ other web frameworks don't have particularly appealing documentation.
I think many newcomers think that Rocket is “the web framework” in Rust. And if author goes silent again they will be let down. It casts kinda bad shadow on Rust community but we have better alternatives.
Do you have a source for the reliability claim? There are so many good old transformers deployed around the world. Many of them working for 10s of years without a replacement. I'd be suspicious that a buck converter will have longer MTBF than oil submerged transformer.
Also, I don't see why it is mentioned here but NREL estimates the cost of grid scale inverters (for installations of 100 MW) to be 5-10x more than what was mentioned. [1]
[1] https://www.velocitymicro.com/blog/what-is-psu-efficiency-an...
[2] https://www.electricaleasy.com/2014/04/transformer-losses-an....
At the same voltage, DC will in all usual cases have higher losses than AC. This is basic physic.
Non-constructive critique helps nobody.
Case 1: SPV 12 kWp @ 200V -> Inverter (eff=96.2%) -> 200m of 8 AWG wire -> AC-DC switching power supply (eff=92%)
Case 2: SPV 12 kWp @ 200V -> 200m of 8 AWG wire -> DC-DC buck converter 90%
If first case we get 9.16 kW. In second case we get 7.596 kW. In Case 2 you need the buck converter because the DC voltage will vary with temperature of the cable itself. Voltage loss in this case will be roughly 56V. In both cases I disregarded the effect of MPPT as it will be the same in both cases.
This suggests that when the cables are short enough (probably about 50m) then it might make sense. For anything else we are probably better off with AC networks.
One remark is that an industrial warehouse with rooftop SPV will probably need AC too. This might work for single family houses though.
With AC you can step up to higher voltage with similar efficiencies which will lead to lower transmission losses. I kept the voltage at 200V for simplicity. But going from 200V to 800V will lead to transmission loss of 3.43% instead of 13.73%. This way AC is clear winner.
I have yet to see a good application of microservices. I’m not saying there are none but the companies that can truéy benefit from that are few and fare apart.
From my experience smaller companies usually benefit a lot from simple monolythical architecture. Large companies tend to split problem into multiple products. But each product is still a kinda monolyth.
I have no experience with huge SaaS companies like Netflix. I can easily see why there the situation is quite different.
My horror story from recent days is that I had a 100-ish LOC patch. I had to push an update to 8 repos. That means 8 merge requests, 8 code reviews, deploy changes in correct order such that it does not break anything. The whole thing took 3 days. Coding was done in two hours.
My business is thermodynamics of power plants. Professionals in the industry tend to use convenient units like C, bars, kJ/kg and so on. But the formulas usualy need basic SI units. Using this library not only streamlines the conversion process but also keeps track of the unit itself. So instead of variable turbine_output_gj and turbine_output_mw I can have just turbine_output which is convenient.
It is hard to put a value on that but I believe it has already spared me many trivial mistakes that I had to explain to my clients.