In India's case it's silly to make a comparison.
1,603 karma · joined June 17, 2017
hn@ahmed.al-sudani.com
Opinions obviously do not represent my employer.
In India's case it's silly to make a comparison.
If a functional language is presented today that does not automatically curry calls, I have no interest.
Just because the tool does not work for you does not mean there's a defect in the design.
Where do you think rust got (more than) half of its type inspiration from?
Either way no one has to use any language. Personally OCaml is not my cup of tea--Haskell is. But it is a great tool and it's solving hard problems.
Spoiler: this person had a very different experience. They spent 2h20m charging going from Illinois to Florida (at least I'm pretty sure it was Florida)
This is not a great time to buy any efficient car. Things were easing until gas prices jumped up ... and the recent lockdowns in China probably haven't helped.
It's a good idea to wait for a more opportune time if you can.
It's exciting in the same setting up new software is.
Reserving opinion on how much I agree with the sentiment :)
The STL map allows you to:
- specify the key/value types
- specify the equality predicate
- specify which hash function to use
- iterate over values
along with a host of other things that most users don't initially need but they might need in the future.
You could implement something that has feature parity in C++ or ideally find a battle-tested library that does.
Using C, however, you'd have to sacrifice type safety and possibly readability. Yes it can be done, and yes it can be done correctly. But it's tricky and difficult to ramp up on for the new developer. This is the one that you should be careful about adopting.
My philosophy is to use the STL containers because they're familiar and they're more than good enough for 99% of the use cases out there. Developer time has a premium, and this saves developer time.
If you need performance because you're constrained by CPU cycles or if you're running at scale (Google for example), by all means reach for something better.
https://inflationchart.com/m3-in-home/?time=10%20years&zero=...
Neat website btw. Thank you for sharing.
- those hash maps are optimized for large sets
- they work around several edge cases
- they implement way more features than an in-house implementation
- they need to support many types of hardware
A decent engineer can beat the std collections in a day on performance. But to do that in production over a decade with shifting requirements is a different ball game.
Do I need to manage memory? Does it manage memory? How do I iterate? How do I add a new key space without thrashing the original implementation and making it twice as complicated?
That's the biggest thing a standard interface gives you. Even if it's less performant and not well-designed, I'll take it.
The C++ containers are actually well-designed and performant so it's a no-brainer if you get to choose.
Almost forgot the type checking you get with C++. That's also a major factor.
People willing to put money into your product sends a great signal about its quality/usefulness.
This is a great model for generating useful OSS projects.
Glad to hear your infection came with no severe symptoms.
Being able to come in contact without worrying about being the unlucky person who gets hospitalized is something to be thankful for. The vaccines have been a gift.
China seems to have a perfect storm of a healthcare system already stretched thin, low immunity among the population, and a super infectious strain.
The lockdowns are probably their best option but they also need to ramp up mRNA vaccinations in tandem. Zero COVID is unsustainable.
Something like 50% vs 90% though that could be old data.
- lower vaccination rates
- vaccine drives prioritized the young and healthy (the idea being they can handle side effects so this seemed like the best way to achieve herd immunity)
- the newer strains are super infectious and would overwhelm the healthcare system
They don't have a good way out now. They should have used the time they got last year to buy MRNA vaccines, but they did not.
The central government has likely given up on zero COVID but are sticking with those policies for now to "flatten the curve" while this wave takes its course.
I run a server that lets me receive calls wherever I am (SIP or forwarding, as required) and send messages. Like a self-hosted Google Voice but more flexible and with a greater choice of numbers + forwarding destinations.
All my server does is respond to HTTP requests from Twilio and send HTTP requests when I send a message.
Somewhere in the Twilio interface, you can define a SIP endpoint, but I forget where it is. That's enough for placing calls and does not require running a server.
Almost forgot to mention that I receive text notifications via pushover because I am not an Apple developer ... so no app for me.
Raising my hand in agreement!
A couple highlights:
- Video syncing library before those became cool (2014). Originally built on top of firebase; now rewriting with my own backend. Very slow going :)
- Twilio server + interface. I'm my own service provider (thanks to Twilio)
Thank you for sharing. There were GCC segfaults that started appearing on my machine a few months ago, and they magically disappeared after a recent update. Those tools are going to be a massive help next time that happens.
- Google search
- Google maps
- YouTube
- FB Messenger/WhatsApp
- Oculus
- FB Marketplace
Re: dirty windshield. Humans see through those, and we have windshield wipers if visibility is impeded.
I'm still excited about the LIDAR possibilities but vision alone has done a remarkable job.
Especially appreciated the OS minutiae and opinionated commentary (... and the doc vs reality observation in Linux's vfork).
The piece lives up to the great title :)