I completely agree.
I’m a staff software engineer at Sunrun, the USA’s largest residential solar installer.
I mostly work with kotlin, but also java, python, ruby, javascript, typescript. My hobby is picking up new hobbies. Currently bird photography and camping.
I completely agree.
it does if the other ones have edible seeds, seeds without arsenic, or fewer seeds… your analogy makes no sense.
Also, writing memory safe code honestly isn’t that hard. It just requires a different approach to problem solving, that just like any other design pattern, once you learn and get used to it, is easy.
the CVE list would disagree with you.
https://en.wikipedia.org/wiki/The_Power_of_10%3A_Rules_for_Developing_Safety-Critical_Code
and their 40 page coding standard document. https://ntrs.nasa.gov/api/citations/20080039927/downloads/20080039927.pdf https://ntrs.nasa.gov/citations/20080039927
and their software safety handbook. https://standards.nasa.gov/standard/nasa/nasa-gb-871913
all 389 pages of it https://standards.nasa.gov/sites/default/files/standards/NASA/Baseline/0/nasa-gb-871913.pdf
It’s also just a huge fallacy. He’s saying that people just choose to not write memory safe code, not that writing memory safe code in C/C++ is almost impossible. Just look at NASA’s manual for writing safe C++ code. It’s insanity. No one except them can write code that’s safe and they’ve stripped out half the language to do so. No matter how hard you try, you’re going to let memory bugs through with C/C++, while Rust and other memory safe languages have all but nullified a lot of that.
You ask them to add a license, you don’t suggest a license.
You can write cross platform mobile (and desktop and even browser) apps with Kotlin.
that’s so weird because I got an email inviting me to participate and I haven’t ever been considered a ‘prolific poster’. I’m only at 60k and 12 years. I had no clue I was invited until I looked in my spam folder.
I’ve been saying this for years. My site only has a few lines of javascript. the rest is pure html and css, and it’s very simple. https://tylerthrailkill.com
Manually patched by pulling the commit and building your own source?
Wait so was the hacking live?
Just so you know, there are some major security issues on 0.18. That’s why programming.dev immediately updated. The later bugs on 0.19 we were easily able to work around, while the security issues are major and should be resolved as soon as you can, as it affects every user.
Like I said, none of that happens to me and I’ve been using YouTube since 2006. It really does seem like a difference between paid and unpaid amounts.
Do you pay for premium? From what I’ve seen the algorithm is much more hostile to people who don’t pay. I literally _never _ have these problems about YouTube recommending stuff I don’t care about.
Your logic doesn’t make any sense. They make money off of people paying for a service or watching ads. If you’re blocking ads then you’re costing Google money and no creators are getting paid. If you’re paying for the service then you don’t get ads, and you pay the creators, and you pay for Google to keep running the service.
Anything but the last one. Don’t duplicate the http code in the body, else you’re now maintaining something you don’t need to maintain.
I’m not a fan of codes that repeat information in the body either, but I think if you had used a different example like “INVALID_BLAH” or something then the message covered what was invalid, then it would be fine. Like someone else said, the error data should be in an object as well, so that you don’t have to use polymorphism to figure out whether it’s an error or not. That also allows partially complete responses, e.g. data returns, along with an error.