TheMonarchist
Joined 5 years ago
Karma
64
Submissions
125
Member since
Jul 23
Someone's interests should be in line with those of the country.
View on Hacker NewsRecent submissions
Comment · 4 years ago
This has been my primary research strategy for the past decade.
It's digging gems from piles of rubbish, but when you find them you know that they are genuine.
Comment · 4 years ago
> I'm not aware of a way to construct an std::vector without throwing an exception.
You use an allocator with enough pool for whatever you need to do and avoid out of bounds access.
Comment · 4 years ago
> Calling Thing::default() clearly communicates that your just getting baseline values and not a lot of magical other initialization stuff going on— with a Thing::Thing() in C++, you're really at the mercy of whatever the project conventions are for how "fat" the constructor is going to be.
In C++ the constructor without arguments is called default constructor. Of course the expectations depend on conventions, but usually it's something from uninitialized garbage to an empty state.
Comment · 4 years ago
> Like maybe checked exceptions in C++ would work
Comment · 4 years ago
Comment · 4 years ago
I wish people were content at thinking that they know better.
Right now they try to coerce others to act like they do in many parts of the world.
Comment · 4 years ago
To me it seems like a naturally arising question,
but these days people aren't always rational so IDK.
Comment · 4 years ago
I wish I could say just "no" but nowadays you can't be sure where used laptops have been anyway. If you can't buy a new laptop, you could as well just buy one that has been in China.
Comment · 4 years ago
Experience-based guidelines for adopting C++11/14 at scale if you haven't already.
(The experience requirement ruled out C++17 and C++20.)
Comment · 4 years ago
> Lambdas, Streams… Java is far from "80s style OOP" today.
Streams are a library feature. At a cursory look Boost seems to have had something similar since 2003: range adaptors[0].
Moreover lambdas have existed since 70s. They are modern only in the sense that Java got them in 2016 or so.
> It steals the best from the more avant-garde languages and builds it in coherently. That's no small task, so it takes few years.
That's a nice way to say that it gets new features only when they are undeniably useful.
> Therefore I wouldn't call Java "cutting-edge", but "modern" easily.
If Java is modern, C++ is cutting edge. It got the syntactic sugar for lambdas in 2011 - five years before Java.
However I may have put too much weight on "modern" in the question title. The demand for Java coders is going to be higher than the supply not unlike COBOL. If you can live with its limitations, you can make a living maintaining Java codebases for decades to come.
[0]: https://www.boost.org/doc/libs/1_78_0/libs/range/doc/html/ra... (Nowadays you would use Eric Niebler's Ranges-v3 when C++20 Ranges aren't available.)
Comment · 4 years ago
Java was designed to support 80s style OOP. While many mainstream languages do the same, it isn't particularly modern. I haven't followed Java's evolution in the recent years but as I recall it is the last language to adopt anything new.
Comment · 4 years ago
The interesting languages are those that don't need killer apps to succeed.