747 karma · joined March 21, 2023
You keep compatibility with C, can tap into its ecosystem, but you are no longer stuck with outdated tooling
D gives you faster iteration, clearer diagnostics, and a generally smoother experience, even if it doesn't go as far as Rust in terms of safety
I wish more languages would follow this strategy, ImportC is great, let's you port things one step at a time, if required/needed
Let's be honest: who wants to write or generate C bindings? And who wants to risk porting robust/tested/maintained C code incorrectly?
De-risk yourself from Microsoft
While "journalists" were busy bootlicking a laggy 720p Android only xCloud beta, Stadia was already delivering flawless 4K@60FPS in a web browser
They killed the only platform that actually worked just to protect Microsoft
This will be a textbook case study in how a legacy monopoly kills innovation to protect its own mediocrity
Microsoft won't survive the century, they are a dinosaur on borrowed time that has already lost the war in mobile, AI, and robotics
They don't create,, they just buy marrket share to suffocate the competition and ruin every product they touch
Even their cloud dominance is about to end, as they are already losing their grip on the European market to antitrust and sovereign alternatives
If you don't use systemd, i hate you, you should use systemd, and i'll force systemd on you
If you don't use wayland, i hate you, you should use wayland, and i'll force wayland on you
If you don't use gnome, i hate you, you should use gnome, and i'll force gnome on you
See the pattern?
Fun
The Apple/Google OS duopoly exists by design, they view bootloader unlocking and sideloading as threats because they break that control
They want to be able to define and/or revoke your existence in the system
No escape, because no alternative
Meanwhile, users pay a premium to pretend they're not using Google
Fascinating delusion
Whoever gives US Big Tech access to their digital infrastructure is a foreign spy and should be jailed
No, memory safety is not security, Rust's memory guarantees eliminate some issues, but they also create a dangerous overconfidence, devs treat the compiler as a security audit and skip the hard work of threat modeling
A vigilant C programmer who manually validates everything and use available tools at its disposal is less risky than a complacent Rust programmer who blindly trust the language
Comment in question:
It's ironic to watch the contradictions unfold
On one hand, nobody actually knows what's happening in Iran, yet everyone has a rock solid opinion, complete with intricate details, as if they'd just left a classified briefing
On the other hand, those same confident voices all want the same thing: a leader who'll privatize Iran's oil for Western companies, align with US policy, open markets to Western finance, and prioritize defense contracts over local development
Funny how that works
Some random farmer from Ohio is obsessed with Iran for some reason
Instead of building a true portable binary format with system access, we got a JavaScript VM from TEMU:
- Reference Types
- Exception Handling
- GC
Makes GC'd languages compile better, not system programming
Meanwhile, the actually needed capabilities remain blocked forever:
- Memory: Still can't mmap, still can't allocate outside linear memory
- Networking: Still needs JS interop bullshit
- Device: Still need JS interop bullshit and still sandboxed behind browser security model
The Result: WASM isn't a serious systems target, it's a compilation artifact for managed languages that could've just targeted JS directly
The US wants a regime change, that's a fact, Trump has been very vocal on the matter, and the NSA has the tools to do what ever it pleases on the internet (e.g., PRISM)
Not just protests, it's to prevent foreign interference (like CIA) from fueling civil unrest and spreading AI deepfakes, as seen in Myanmar and Brazil
https://www.amnesty.org/en/latest/news/2022/09/myanmar-faceb...
Well done Europeans, catering to Trump
Gaming is pure B2C: hit driven, capital intensive, and unforgiving
The entire price crisis stems from anticipation of that prospect
Why do we still have to recompile the whole program everytime we make a change, the only project i am aware of who wants to tackle this is Zig with binary patching, and that's imo where we should focus our effort on..
C3 does look interesting tho, the idea of ABI compatibility with C is pretty ingenious, you get to tap into C's ecosystem for free
https://www.sandiegouniontribune.com/2013/06/13/us-whites-fa...
Ironically, that prospect is approaching with each passing year
More importantly, this highlights a pattern of selective scrutiny:
- When Western companies (like Tesla) source batteries from the same regions (or use batteries from BYD or CATL), human rights concerns rarely drive mainstream criticism or policy actions
- When industries dominated by Western monopolies (eg: Big Tech's app stores or cloud services) face human rights allegations (like labor abuses in global supply chains or censorship complicity)= the backlash is often muted or just silenced
- But when a non Western competitor like BYD gains traction, human rights rhetoric suddenly intensifies, even without evidence matching the severity of claims against established Western companies
It's geopolitically convenient criticism, FUD against what threatens a western monopolistic ecosystem
You know this is a psyop when they can't resist mentioning Microsoft's product
Centenarians i know are all on a plant based diet
Insects? why bother