I think it's more about how using "most" as a measurement, no matter who the audience is that you pool from, is not a good way of producing a valuable list. In the end, having someone learned and well read produce a hand-written list with deeper cuts brings more value.
He is definitely "online". I saw him tweet about Hasan's dog which - you have to know about streaming political figures and the latest happenings at least a little bit. Maybe not addicted but he knows what is up and still has the views he has.
I wonder how people are able to stay functional while being online. I'm in 2 states. (1) Very productive and joyful. (2) Extreme dysfunctional and commenting on HN and Reddit.
My guess is that you're assuming all user defined types, and maybe even all non-trivial built-in types too, are boxed, meaning they're allocated on the heap when we create them.
That's not the case in C++ (the language in question here) and it's rarely the case in other modern languages because it has terrible performance qualities.
I think usefulcat interpreted "std::vector<int> allocated and freed on the stack" as creating a default std::vector<int> and then destroying it without pushing elements to it. That's what their godbolt link shows, at least, though to be fair MSVC seems to match the described GCC/Clang behavior these days.
Well if you're using the standard library then you're not really paying attention to allocations and deallocations for one. For instance, the use of std::string. So I guess I'm wondering if you work in an industry that avoids std?
I work in high-scale data infrastructure. It is common practice to do no memory allocation after bootstrap. Much of the standard library is still available despite this, though there are other reasons to not use the standard containers. For example, it is common to need containers that can be paged to storage across process boundaries.
Tbh I think it's ok - as much as I also want to avoid Twitter I do encourage original sourcing, especially since these nitter services can also have downtime fairly often. As long as someone jumps in and shares a link
This seems problematic to me. Beyond just caching issues, did you ever get permission from users to store their personal data? They gave google permission, but not you.
Public data can be personal data and anyone doing the same as TFA is making itself a liable processor. But, aren't you a processor by using OAuth in the first place? Yes but with what TFA is doing you have a greater liability surface.
I don't live in Europe, I will never travel to Europe, I don't plan to ever do business with Europe. I don't care if Europe sentences me to be shot into the sun for GDPR violations, it's not like I'm going to be extradited for it.
And I'm not aware of any law anywhere here that says I can't download a public photo. The use case is clearly valid and benign, the photo is public, there's no way a judge would go for that no matter how you twist the law.
Yes. I'm not for calling out individual people, those who probably had hope and some may be young and didn't have the warning flags going off. I can only imagine they're disappointed and had no malice.
But people who have some level of fame who put their name behind it, and who had some influence in inspiring others down this wrong path most definitely need to address it. If you truly believe the intelligence of tech people over others in every field which led you down this path, follow the proper postmortem process.
It is absolutely not all major employers. I'm on a visa and have worked for two major tech companies in the US over the last 10 years. I have never been a contractor. I've also compared salaries and know I am doing comparable or better. The majority of my team have always been naturalized citizens.
"the entry into the United States of aliens as nonimmigrants to perform services in a specialty occupation under section 101(a)(15)(H)(i)(b) of the INA, 8 U.S.C. 1101(a)(15)(H)(i)(b), is restricted, except for those aliens whose petitions are accompanied or supplemented by a payment of $100,000 — subject to the exceptions set forth in subsection (c) of this section. This restriction shall expire, absent extension, 12 months after the effective date of this proclamation, which shall be 12:01 a.m. eastern daylight time on September 21, 2025."
So it applies to all H1Bs. Subsection c is limited (but will be interesting to see how it plays out) so I don't bother sharing.
Arseny Kapoulkine is an amazing engineer. Highly recommend following his blog or social media. Other than working on luau and the rendering engine at Roblox, he's also responsible for meshoptimizer which if you're in graphics you've most definitely heard of, and volk, which now comes packaged with the Vulkan SDK.