Considering the insane memory consumption of claude code running in my terminal, electron was never really the problem, bad software was the culprit all along.
I did my time in C++, had fun, learnt plenty, then got an offer to do some python with a way better salary. At some point company have to seriously up their offer if they want me to care about ABI breakage, weird bug cause by undefined behavior, and the usual 100k loc of legacy code with 10+MB sized object and no coherent memory ownership.
As I see it, Carbon have in its explicit goals to fix both the syntax issue and the major ABI retrocompatibility issue, while herb approach is to just deal with the syntax: Sure it is better than nothing, but I'm willing to bet that this will not convince most of people that saw their idea being killed by the committee on the ABI altar.
I'm currently living in a country with an healthy approach on work/life balance, seeing the appalling situation in the us always made me defiant to move there. I hope this awakening on the issue will be picked up by politics and will lead to better regulation.
I would like to point out that yosefk fqa is a bit old now, and while some problems mentioned are still relevant, tools and conformity across up to date compilers are magnitudes better now.
Mind this is only the simplest functions and thing can already go wild if you apply classic bad C++ coding practices, like cascade inheritance or god object.
Add to that, you will (oh yes, you will, at least once) make type errors with macros, and you will fail to maintain all the class constructors and virtual functions.
Welcome back to the 80's, where C++ used to play with macro to make templates and inheritance was only a basic compiler trick.
I can only emphasizes the need to move to real C++ if you want to use C++ idioms, to do it safely and performances wise: here you just opened the gate of Macro error's hell which will be more horrible than anything the C++ could throw at you.
It's sad to see so much trolling on this language but I suppose we all had to maintain old C++ programs that became spagetti codes and dependancy hells.
I'm currently working on a new project using C++11/14 and it's a pleasure to see more functional features that will allow to be more concise.
Well, with Microsoft (and many other software company) ready to pull the plug of updates on this OS, I hope you have faith in your antivirus to stop every unpublished exploit.
The point of maintaining the source code to the latest version is to guarantee its survival to the long term: at some point you will have to pass the ownership to another, younger, dev that might not have been taught into this older technology; or port your script to a newer hardware, and eventually deal with an sub-optimal or incomplete VM.
Either you maintain to the latest version and distribute the cost in time or one day you will have to start from scratch, and probably lose more time and money to do so.
See every organization still running on XP ? They may be sentence to death in 3 month, that may be the hardest way learn it.
I'm in France right now and the usual legal notice here is a ... 3 month notice.
This is a double edged sword: unless common agreement, the employer have to pay the employee 3 month (and if asked, the employee has to stay at work), but it gives him the time to replace it properly.
I won't go in detail to the different legal issues for each case, but it avoids these kind of problem for startups (and create others).