I also understand why it’s not something common outside of Japan. Selling your family name in exchange for (maybe) keeping your business alive is distasteful at best.
9,841 karma · joined July 2, 2011
All views are my own, etc.
* Homepage: https://assil.me
* Github: https://github.com/aksiksi
* Twitter: https://twitter.com/aksiksi
[ my public key: https://keybase.io/aksiksi; my proof: https://keybase.io/aksiksi/sigs/PhsFUqf4TTQdHrQvnrRhLU4bgilyPjSZjo5DQFHM9QU ]
I also understand why it’s not something common outside of Japan. Selling your family name in exchange for (maybe) keeping your business alive is distasteful at best.
Also, it’s probably fast enough for apps to be deployed in something like a staging environment for integration tests to run against them. Production deploy/release can then happen using a tagged version that gets compiled using vanilla GCC/Clang.
So I don’t see how Rust is at a huge disadvantage here when Fil-C is typically not going to be enforcing safety in production. I suppose the testing/fuzzing story becomes all the more important because you need to exercise runtime behavior for Fil-C to detect unsafe faults.
Don’t get me wrong: I think Fil-C is a smart idea and an excellent way to introduce memory safety to existing C codebases. But I don’t get this whole (usually implied) idea that Fil-C somehow makes Rust look bad or renders it obsolete.
mmap is a bit of an outlier because it is not possible to implement a fully featured safe wrapper (MAP_SHARED) in Rust. So I would be curious to see what safety guarantees Fil-C claims to provide for mmap.
The UN argument boils down to Spain lobbying the UN early on (post-WW2) at a time when Morocco and other North African and West Asian states either did not exist yet or did not have the ability to represent themselves well at the UN.
But applying this logic universally would change the world map, not to mention that this justification ignores the fact that the concept of a nation state is relatively new as a norm.
Regardless, I and many others will continue to ridicule Spain’s paradoxical position on Gibraltar. Hopefully a just resolution is realized for all parties at some point in the future.
As an aside, I have always found it ironic how Spain continuously whines about Gibraltar while doing the exact same thing to Morocco. At the very least, Spain was smart/lucky enough to lobby the UN early on to not include Ceuta and Melilla in the decolonization list.
Or repeatedly elect ex-Irgun and Lehi terrorist leaders into the highest positions of government.
Or just Winston Churchill the hell out of it and be proud of your past crimes.
etc etc
It’s kind of like our industry - the higher comp is a big reason behind how the US attracts talent from all over the world.
It’s only the same if you consider natural resources and human labor to be equivalent. To me, that sounds quite reductive.
Now think about the data you could collect and the decisions you could make based on this data to ensure a better future for all in this country; in fact, this is a stated goal of the survey that you either didn’t know about or are willfully ignoring.
On the flip side, think about the repercussions of tainting this data and basically wasting such a valuable chance that won’t come around again for another 10 years.
The alternative is to water down the census questions, which also leads you down the same path (i.e. manure as data).
I personally trust OSINT sources more than NGOs these days. I would wager that the security forces numbers are higher. I would also wager that the majority of the deaths were CIA and Mossad backed insurgents operating in the context of a wider, legitimate, civilian-led protest movement.
> As many as 30,000 people could have been killed in the streets of Iran on Jan. 8 and 9 alone, two senior officials of the country’s Ministry of Health told TIME—indicating a dramatic surge in the death toll.
https://time.com/7357635/more-than-30000-killed-in-iran-say-...
Imagine infiltrating the Iranian surveillance camera network and being unable to produce footage of 30k people massacred across two days.
I do not like Iran because of its actions in Syria and Yemen, but even with my bias, I could hear the bullshit Western elitist consent manufacturing engine starting up from miles away.
You would think the traffic and surveillance cams hacked by the Israelis would’ve shown the extent of this bloodbath.
https://apnews.com/article/iran-war-security-cameras-surveil...
Keep in mind that the elite class couldn’t give two shits what the peasant class thinks. In fact, having us believe in false conspiracies helps distract the masses from the true conspiracies :)
It’s like how Israeli lobbying orgs state that “claiming Zionist orgs control the media is antisemitism”, and then the solution is literally “we should use our contacts & supporters in the media to stop this kind of rhetoric”. Beautiful.
In fact, I believe Samsung is the only company on the planet that can design & build a state of the art smartphone from scratch - silicon/fabrication, SoC, battery, baseband, camera sensor, memory, and display.
What other high tech vertically integrated producers exist in this group?
I maintain one of the competitors listed in that README (compose2nix), so I am a bit biased haha.
For now, I prefer the ability to interop with Compose.
But my question was around readability: were you able to understand what the snippet I shared is doing?
Re: build-time checks - but systemd hasn’t done it, and I am also unsure where exactly this verification would even take place given systemd’s configuration model. Unless you’re talking about some kind of language server or IDE integration.
Compare it to the alternative of using plain systemd (including command(s) required to enable units).
Also, consider what build-time validation you get prior to starting the unit/timer. Hint: zero.
a) It is way nicer and you get decent validation at build time
b) A LLM can port units over if the need arises; it’s a very light abstraction around systemd syntax
c) I personally don’t see how I would ever move to another distro :)