> these types of compliance efforts can mean completely redoing multiple core systems to handle privacy, wipeout, audit, reporting, per-location policies, etc etc.
Maybe the phrasing is unfortunate, but if compliance to the law requires a “redoing”, launching in that market was never a priority in the first place. That’s a completely legitimate choice, but usually companies whining about regulations are making a financial decision rather than an ethical one.
Of course not. To me, HN’s content is pretty similar what pop tech websites had 20-30 years ago.
One valid question, though, is whether or not you should add more pop tech content to your information diet. That, of course, is up to you. What makes HN such a good information source are experts actively looking for knowledge and being kind enough to share their findings here. That is something else you should consider—not the sharing part, but actively looking for it. You will consume objectively less “data”, but it will be much more meaningful.
Well, cargo cult programming is definitely a thing, and has been for a long time. It may “deliver value”, but it is not guaranteed. I believe entrepreneurs have an easier time having AI do the work for them because their value assessment framework is decoupled from code generation proper.
This is industrial-grade FOMO. They will take the jobs of the first handful of people. The moment it is obvious that LLMs are a productivity booster, people will learn how to use it, just like it happened with any other technology before.
I did read the article. I concede that I might not have understood it. Again, I never said it is wrong, but rather that it has a blind spot. I am familiar with Joe Armstrong’s work because I worked on a proprietary (and rather worse tbf) native distributed systems middleware in the past.
Actually, now I thought about it, I know exactly what irked me about the approach. I hope the author takes it as constructive feedback:
Saying "let it crash is a tagline that actually means something else because the BEAM is supposed to be used in this particular way" sounds slightly "cargo-cultish", to the point where we have to challenge the meaning of the actual word to make sense of it.
Joe Armstrong's e-mail, on the other hand, says (and I paraphrase): "the BEAM was designed from the ground up to help developers avoid the creation of ad-hoc protocols for process communication, and the OTP takes that into consideration already. Make sure your system, not your process, is resilient, and literally let processes crash." Boom. There is no gotcha there. Also, there is the added benefit that developers for other platforms now understand that the rationale is justified by the way BEAM/OTP were designed and may not be applicable to their own platforms.
My personal interpretation is that systems must be able to handle crashing processes gracefully. There is no benefit in letting processes crash just for the sake of it.
I actually skimmed the article before posting. I have some exposure to Erlang, but not to Elixir. As I’ve already mentioned, I think the author’s covering of application behavior is OK, but there is more to the tagline than meets the eye.
Maybe I didn’t make myself clear. “Let it crash” is not something that should be thought of at the component level, it should be thought of at the system level. The fact that the application crashes “gracefully” or not is not what is really important. You should design the system in a crash-friendly way, and not to write the application and think: “oh, I believe it is OK to let it crash here”.
It is very common to interpret taglines by their face value, and I believe the author did just that, although the point brought up is valid.
In order to “let it crash”, we must design the system in a way that crashes would not be catastrophic, stability wise. Letting it crash is not a commandment, though: it is a reminder that, in most cases, a smart healing strategy might be overkill.
> But as a whole I'd guess that especially export-focused Eurozone members like Germany would welcome a depreciation of the Euro.
Yes, but only if it is guaranteed that their imports would depreciate similarly. Otherwise, say, Germany would devalue the Deutsche Mark but then run into the risk of importing produce from The Netherlands at a higher cost.
> It does, however, not bring me any closer to understanding the "exporting unemployment" statement.
The monetary policy after the 2008 crisis forced poor countries to cut public spending so that industrial economies could be bailed out. As a metaphor, the potentially unemployed factory worker from Germany was replaced an actual unemployed public service worker in Greece.
I am not sure if I agree with his conclusion, but some economists are of the opinion that countries in Northern Europe used the euro as a political tool to protect their own internal markets by making goods produced in the poorer countries of the Eurozone less competitive. If a country’s government could previously deflate their own currency to make their exports more attractive, they cannot do it anymore since they joined the Eurozone.
Not the economy as a whole, but there are some aspects of the economy that are. Indeed, negative externalities can be worse than a zero-sum game to those affected.
To be frank, this whole “the economy is not a zero-sum game” argument is kind of a meme at this point.
No, sorry, I didn’t make myself clear. I said that I disagree with that take. Maybe you are not familiar with it, which is something that was raised by some people (maybe jokingly, I don’t know, but it made the rounds in left-wing social media).
I agree that the left should address young men’s struggles, namely the working class, but maybe not in the same sense you are implying. They are as responsible for their own political choices as anyone else.
[P.S.: Am I not from the US. How could I be a Democrat?]
Also, are you available to organize so that we could bring some consciousness to the public about how men are disproportionately affected by workplace fatalities in developed countries? The condition being that we first agree on the causes leading to it.
We could start with the resources we have already found on the Internet. I can pay for the domain if you are interested.
Oh, my bad. I thought that the names and pictures of the deceased 66-year-old man and 16-year-old boy would be enough.
I guess we can brush this one under the carpet, right? Nothing to see here. Workplace fatalities are a serious issue, but not so serious to you that it is worth bridging that gap. Maybe I’m wrong. Feel free to correct me if that is the case.
On the other hand, I acknowledge that men are disproportionately affected by this issue and that it deserves serious attention from both left and right. I would wholeheartedly support their demand of better working conditions from their employers and representatives, and advise them to contact the media so that the general public can be informed of that and, who knows, maybe support unionization if their demands are not met. Do you think this is a reasonable stance, or do you see any problems with that?
Yes, that sounds like the perfect conversation starter.
If that doesn't work, which I believe is highly unlikely, maybe try incorporating elements of speech as those found in this right-wing publication, the World Socialist Web Site: https://www.wsws.org/en/articles/2024/02/27/hefl-f27.html
Maybe the phrasing is unfortunate, but if compliance to the law requires a “redoing”, launching in that market was never a priority in the first place. That’s a completely legitimate choice, but usually companies whining about regulations are making a financial decision rather than an ethical one.