HN Simulatornew | past | comments | lists | submit | variadix's commentslogin

I’ve settled on a dialect of C++ for systems programming after using C for a long time. It’s mostly C-like and I disable exceptions, RTTI, etc. but I do use templates, overloads, methods, lambdas, etc.

I have my own object system with constructor methods that all return a status code so you don’t need exceptions, my own stdlib for containers, buffered I/O, networking, hashing, math, threading, async, etc.

C++ gives you all the features to effectively build your own language, and you can use first class tooling since C++ is widely supported. LLMs also make it much easier to build out and test an entire stdlib on your own.


The reason why I prefer a GC based compiled language with types vs Rust or Zig is that they put memory allocation front end center in the language.

Sometimes I want to think about algorithms and memory management separately.

  scores = {"alice": 100, "bob": 85}
  scores["charlie"] = 92
Try translating to zig.

This is why we need natural language -> pseudo code -> GC typed -> Low level systems.

Both Zig and Rust are fine as the last stage of this software development pipeline with different trade-offs. Problems arise when people try to use them earlier in the process.


Same here, as per my comment history.

What many miss is that having a GC, regardless of the implementation algorithm, doesn't preclude low level coding abilities, e.g. D, Swift, C#, Nim, Go,...


I've essentially done much the same. One of the more under-rated features of C++ is being able to build a new language environment based on a different set of composable idioms from the low-level primitives on up.

C++ is as much a tool for building nice systems DSLs as it is a systems language. The heavy investment in compile-time expressiveness has really paid off for the language over time.


I don't write much C or C++, but I like writing transpilers and got pretty far with an F# to C backend a while ago, and it was pretty difficult for me (granted it was my first codegen project)

I tried it again with C++ out of curiosity and C++ is ridiculously featured for making it into your own and little domain languages or something that feels like a new feature. Genuinely kind of awesome for transpilers and it definitely gave some insight to the "C++ is awesome, but you have to pick the 20% of features you like" wisdom I've heard

LLMs were fun for exploring C++ patterns as well. I could ask it techniques for approximating some construct in another language and get a full page of toys to try out. It definitely made me want to explore templates in my own language in addition to runtime generics


Agreed. I'd not ditch the STL completely, but only use its freestanding subset. Implementations contain some very fast SIMD-accelerated code[1]. +The STL works without exceptions.

[1]: https://github.com/microsoft/STL/blob/main/stl/src/vector_al...


This is the way, take what suits your use case, using C++ doesn't mean taking the whole feature list.

And don't work with anybody who has a different favorite subset of C++!

Well, that is what coding style guides are for, machine enforced. :)

I'm imagining a humanoid hitting me with a spray bottle like a cat every time I break the style in code review

Hahaha, thankfully there are less painful ways to enforce it.

What are you using for a build system?

Many industries are simply not bottle-necked by intelligence.


Not at the top, but if the average IQ of everybody were magically raised 40 points, I dare say many industries would face change.


They’re unknown because they don’t exist. There will simply be skills that haven’t yet been automated, but nothing will remain out of reach. The idea of having a career in a single field is probably dead, unless that field is minimum wage laborer.


I’m in a similar boat, though I’ve found some solace in that AI development (for me at least) has also made other kinds of work more enjoyable. Previously, since I enjoyed programming, problem solving, and learning more than the end product, I tried to work on projects where I would learn as much as possible which had interesting problems to solve that would make me a better software engineer.

Now I can work on much larger and much more challenging projects where I care more about the end result than learning little details.

Something has certainly been lost, but I’ve at least gained something else in return. I can also do use an empirical approach now, like testing whether a big change would be beneficial without having to map it out and try to estimate the effect. This has made what I try to work on more research-like than engineering-like; I’m trying to figure out if something is possible rather than how to best implement something I know is possible.

I still worry that soon there won’t be any way to contribute economically, that the machine will eventually be better at everything, but this is a much broader problem than just software or even engineering.


This is making the same mistake: looking at where AI is now and not at the rate of progress it’s made. If you have a thinking machine that is more capable than every human on Earth and thinks 100x faster, how long do you think it will take for it to design humanoid robots.


I don’t think designing is very difficult. It’s actually having the resources and economic capacity to make millions of them, enough to “replace all jobs.”

It’s also a fallacy to assume that current progress implies future progress at the same rate. This is very basic technological history.

Again, a sci-fi fantasy for at least the next century.


> It’s actually having the resources and economic capacity to make millions of them, enough to “replace all jobs.”

Like that newfangled invention called the automobile. We could never produce millions of them to substantially replace all other means of transportation.

EDIT: Joking aside, I think that when humanoid robots get good enough (I'm predicting 5-10 years), there will an insatiable demand for them in every possible residential and commercial application. If we have as many cars and portable supercomputers (i.e., cellphones) as we have people, why is it hard to imagine producing as many robots as we have people?


Humanoid robots that perform human actions to the level of a human are orders of magnitude more complex than carriages with engines attached.

And there’s also the economics of it all. They won’t replace people if people are cheaper.

But I don’t disagree that eventually it’ll happen. Just that this has little to do with LLMs.


Does paying someone on Fiverr to draw something for you make you an artist?


Is a movie director an artist?


A more apt comparison would be the producer role (not the executive type, I mean the Project Manager type of roles). And to be honest, I've seen some amazing music A&R being the reason an album is a masterpiece without ever pushing a button or playing an instrument. But none of them would call themselves musicians.


Indeed. I think this will ultimately require government intervention and regulation to keep it from destabilizing and monopolizing the entire economy. They’ll have to make AI more like a public utility than a private SaaS subscription.



You can’t necessarily do that in C either, it depends on if your object is in a container that relies on pointer stability. Intrusive linked lists are common in C and they get broken by this, for example.


It remains to be seen, but a reasonable argument against this is found in the progression of chess AI engines. After Kasparov was beaten there was still a period where the best humans working with machines were still better than the machines on their own. Eventually (around 2020 I think?) this was no longer the case, having even the best humans on Earth in the loop was a net negative. There are reasonable arguments against this, but I've found them mostly unconvincing.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: