4 ms·

> The last 10 years of my life writing C++ in a professional context were a complete waste of time that I will never get back. I have nothing to show for it. I

> The last 10 years of my life writing C++ in a professional context were a complete waste of time that I will never get back. I have nothing to show for it. I don't get this part. The language you write something in has little to do with how useful the software is. I've had years writing fulfilling software, and years where I was just spinning my wheels.

wott 5y ago
It seems to be one of those nowadays numerous people who invest a great part of their time into programming 'communities' to the point it becomes a defining point of their life, instead of just considering the underlying tool... a tool (or one hobby) among others. It often ends this way.
- mysterydip 5y ago
  Interesting. The only time I've been part of a programming community (really just forums/discord) is when the language was tied to a platform, like gamemaker studio. Everything else I've just... used.
- junon 5y ago
  The author contributed to the spec. They have very strong opinions about language design. If you don't, fine, but don't drag down and dismiss those people who are on the front lines creating the tools you use.
_y5hn 5y ago
It's just the author acknowledging all the code written belongs to some company or organization, and often, can't even be used as a showcase. It was work for money, plain and simple, but may become a hard sell later. However, it's not necessarily true. Working with large codebases, working on language design questions, committees, everything grows experience that can be used later. It's just not clear now how, as requirements and work in other companies or in FOSS may be very different than that C++ development. The author mentions Go as a positive experience. If the ego could be left at the door, Go could be a good language to make a new home in. Either that or Haskell, though with much more investment in all layers. The language and tooling can have very much to say for overall development and maintenance. Also architecture and design matters, as well as changing requirements. It's all very simple or complicated, depending on unknowable X-factors that often need to be decided up-front.
- junon 5y ago
  > It's just the author acknowledging all the code written belongs to some company or organization, and often, can't even be used as a showcase. It was work for money, plain and simple, but may become a hard sell later That's not at all the point being made...
einpoklum 5y ago
> I don't get this part. The language you write something in has little to do with how useful the software is. The author was mostly referring to his efforts to improve the language, not to write some app or library in C++.
LasEspuelas 5y ago
Sounds like this person's passion is the language. And that she has failed to bend it to her liking. Reading through her post, and just based on it, I would guess she has the skills and opinions to create her own language and potentially demostrarte why her vision is worthwhile.

wott 5y ago

It seems to be one of those nowadays numerous people who invest a great part of their time into programming 'communities' to the point it becomes a defining point of their life, instead of just considering the underlying tool... a tool (or one hobby) among others. It often ends this way.

mysterydip 5y ago
Interesting. The only time I've been part of a programming community (really just forums/discord) is when the language was tied to a platform, like gamemaker studio. Everything else I've just... used.
junon 5y ago
The author contributed to the spec. They have very strong opinions about language design. If you don't, fine, but don't drag down and dismiss those people who are on the front lines creating the tools you use.

_y5hn 5y ago

It's just the author acknowledging all the code written belongs to some company or organization, and often, can't even be used as a showcase. It was work for money, plain and simple, but may become a hard sell later. However, it's not necessarily true. Working with large codebases, working on language design questions, committees, everything grows experience that can be used later. It's just not clear now how, as requirements and work in other companies or in FOSS may be very different than that C++ development. The author mentions Go as a positive experience. If the ego could be left at the door, Go could be a good language to make a new home in. Either that or Haskell, though with much more investment in all layers. The language and tooling can have very much to say for overall development and maintenance. Also architecture and design matters, as well as changing requirements. It's all very simple or complicated, depending on unknowable X-factors that often need to be decided up-front.

junon 5y ago
> It's just the author acknowledging all the code written belongs to some company or organization, and often, can't even be used as a showcase. It was work for money, plain and simple, but may become a hard sell later That's not at all the point being made...

einpoklum 5y ago

> I don't get this part. The language you write something in has little to do with how useful the software is. The author was mostly referring to his efforts to improve the language, not to write some app or library in C++.

LasEspuelas 5y ago

Sounds like this person's passion is the language. And that she has failed to bend it to her liking. Reading through her post, and just based on it, I would guess she has the skills and opinions to create her own language and potentially demostrarte why her vision is worthwhile.