3,569 karma · joined May 14, 2007
> Pithy statements such as “only use exceptions for exceptional cases” or “Let it crash”, while catchy, do not do justice to the complexities that programmers need to deal with when deciding how to define, propagate, handle and reason about errors.
I think the author is on to something here w.r.t. how current programming languages and conventions brush over what good code might need.
Now that I asked ChatGPT, it didn't include this reason - perhaps it's too obvious and no-one has written it down before.
> They're working on something new, and all the office hours I had with them were about that. They're not even in our database of companies as InstallMonetizer but as the new thing. (I'm not sure if I can say the name because it may not be launched yet.) I knew they had some previous product that was called a Windows installer, but I don't think we ever talked about what it did. https://news.ycombinator.com/item?id=5093047
If you don't like this, you use the non-Play Store build instead (which supposedly doesn't include any binary blobs, but I haven't checked).
(Reproducible builds is a cool technique.)
Thanks for bringing up --http2-prior-knowledge as a solution!
I thought we were discussing HTTP/2 but now you seem to be invoking HTTP/3? It's even faster indeed but brings a whole lot of baggage with it. Nice comparison point though: Do you want to add the complexity of HTTP/2 or HTTP/3 in your backend? (I don't.)
EDIT: Based on the HTTP/2 FAQ, pure h2c is not allowed in the standard as it requires you to implement some HTTP/1.1 upgrade functionality: https://http2.github.io/faq/#can-i-implement-http2-without-i...
> But also the complexity of deployment. HTTP/2 is fully encrypted, so you need all your application servers to have a key and certificate, that’s not insurmountable, but is an extra hassle compared to just using HTTP/1.1, unless of course for some reasons you are required to use only encrypted connections even over LAN.
> So unless you are deploying to a single machine, hence don’t have a load balancer, bringing HTTP/2 all the way to the Ruby app server is significantly complexifying your infrastructure for little benefit.
Also, everyone has a smaller active and larger passive vocabulary, so alone it's not a sign of attrition.
A more important issue is that Russia is one of the countries that like to violate the treaties and contracts they have signed.
(I'm not an accountant, but as far as I know, the same VAT deductions for businesses apply whether they buy from an EU country or from a non-EU country, which your example doesn't take into account.)
Yes, in the Suwalki Gap (border between Poland and Lithuania). Until this point, the connections were HVDC including to Sweden and Finland (across the Baltic Sea).
> Will they be buying electricity from Europe or selling electricity to Europe?
They already participate in the EU electricity market (through the HVDC lines), some hours buying cheap power from clean sources, sometimes selling expensive non-renewable power.