pjmlp

Joined 16 years ago

Karma
133,704
Submissions
77,919
Member since
Dec 12
Currently working on distributed systems, with managed languages, alongside AI coding agents.
View on Hacker News

Recent submissions

Comment · 1 hour ago
I started coding with Timex 2068, developed for embedded in a past life, thus I fail to see how complicated doing a simple cross compiler in C happens to be.

I also have developed C and C++ native libraries for Tcl, Python, .NET, Java JVM/ART (JNI), Node.js.

Comment · 1 hour ago
Because Rust, C++ don't have a GC, while Swift does have a GC (RC is a GC algorithm) it was designed to be compatible with Objective-C runtime, thus C.
Comment · 1 hour ago
Comment · 1 hour ago
Comment · 1 hour ago
> There is no COM whatsoever, no IPC, no IDL, nothing, dunno where do you get that from.

I get that from knowing my way around OS X, naturally it isn't Windows COM, rather shares many of the same ideas,

https://developer.apple.com/library/archive/documentation/De...

https://developer.apple.com/library/archive/documentation/De...

> I just find it funny to claim that C++ was even partially to blame for Be's demise, when Mac OS X since its first public release actually embraced C++ for a much more delicate component.

I think that those that use such argument tend to be on anti-C++ crowd, they forget that NeXTSTEP even had Objective-C++ as well.

Comment · 1 hour ago
As 70s child, I used a few from that list, naturally as nerd the goal was eventually to get the databank one.
Comment · 10 hours ago
I think it is more a skill issue than anything else.

Yes, marshaling has a visible impact, hence why one should think how to actually make it happen, not much different from using FFI in any other programming language, there is always an impact over staying in the same programming language.

Compilation being harder, only if the developer is not acquainted with C, which seems to be something harder to learn nowadays.

Signal handling is a mess even in pure C, especially since all UNIX implementations added threading support.

Comment · 10 hours ago
Each one should know what is their role, protecting their jobs from late stage capitalism, instead of celebrating it.
Comment · 10 hours ago
A bit more of skepticism and less celebration of our gloomy future, I guess.
Comment · 11 hours ago
Kind of, you will note that it is based on COM, exactly to prevent ABI issues.

Which is what Windows has been doing since C++ replaced C for most of the systems programming stuff, around Vista timeframe.

Comment · 11 hours ago
Yes, Be GUI is heavily multithreaded, so core dumps were kind of common, and stuff like Swing.invokeLater(closure) only came later in Swing, after existing for a while as community library, after folks having the same issues in Java GUI applications.

Note that on Android they took an hammer solution, programming patters to invoke such code on main thread, have as outcome that there are either lint compile errors, or platform killing the application, for those flows not verifiable at compile time.

Comment · 14 hours ago
Comment · 15 hours ago
Prototype based inheritance is another matter.

Original VB was definitely OOP, especially since VB 4, when VBX was replaced by COM.

Comment · 15 hours ago
I thought C was a cross platform language.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton