Well I discussed this with the Author briefly and that's a huge undertaking and he is working on it but the results especially desired results will take time.
Yea as the author of the article that's what I'm wondering too this is scheduled to be "released" in a couple of days. I basically figured I wouldn't need to do much more than not link it anywhere on my website or sitemap.
haha looks like I might have to straight up make non public posts unavailable for viewing in the future.
That is precisely what prompted me to write this article, it was an update to a piece of software I require to use for work that suddenly just stopped working properly.
That's actually a point I wish I touched upon more in the article, how SaaS and the ability to patch software issues later down the line made sloppy coding a norm, because you can always just push a patch and expect your users to update to resolve their issues.
Whereas back in the ol' days (promise I'm not that old) a bug in your software would essentially mean severely dissatisfied costumers that may not purchase the next version from you
Do you really wish to go into stuff that has very little to do with the article itself?
I'll gladly provide an answer but I don't think it's constructive.
I host the site on vercel with astro, I'm on the pro plan which usually costs me somewhere around 20€ per month +/- 5-10€ depending on my monthly traffic.
add to that the minuscule cost of my domain and other stuff I'm paying about 250-300€ per year
My adsense avg per day is just about 1.20€ roughly.
So at best I break even, at worst I lose a bit of money.
I still maintain my position that everyone is welcome and should use adblock or brave or pi-hole on my site if they so wish I won't mind.
But I do like the fact that I don't have to foot the bill :)
Basically if I had to lose money to write I'd probs stop writing if I'm honest.
Google changes the amount and placement of the ads depending what "ad market" you are from so US and other similar countries might experience more ad placements than lower ad market countries.
I tried spinning it down to basically minimal ads in adsense settings and it's still quite a lot.
I strongly encourage the use of adblockers or pi-hole even on my site and see no problem with using them on my site.
The income from adsense just about covers the hosting bills in a year so far, I'm currently exploring alternative methods of monetization that would provide more value to the readers.
Some of it is the fault of AI and the belief that software is super easy to create now and maintenance won't be an issue in the future, mainly by folks who have very little to no experience with writing software but attempt it via the many ways you can do it with AI these days.
Then there's the shiny object syndrome of humanity in general even if we just look at websites they went through so many different cycles, plain html, flash, everything built with bootstrap.css, then came the frameworks, then back to SSR/SSG, etc... etc..
Both of those are just symptoms of a larger disease , namely lack of enthusiasm in general has fallen, a lot of it has to do with how demanding day to day software jobs have gotten, or how financially unstable the younger generations feel so they rarely set aside any time for creative endeavors and passion projects
Cool but I don't know how credible this information is. From what I've read on how they got that data and came to these numbers it does not exactly inspire a high degree of confidence
Making a broad statement like there has never been a memory safe C program is a bit of a dickish thing to say.
especially when you phrase it as
> Can you provide examples for it? Because it honestly doesn't seem like it has ever been done.
it comes off as pedantic and arrogant.
It obviously is possible to write memory safe software in C and obviously it has been done before otherwise we would not be currently communicating over the goddamn internet.
Asking for evidence of something this obvious is akin to asking for a source on if water is in fact wet.
> The Rust community should be upfront about this tradeoff - it's a universal tradeoff, that is: Safety is less ergonomic. It's true when you ride a skateboard with a helmet on, it's true when you program, it's true for sex.
Well put! And this should not be contentious issue, it simply is annoying to deal with Rust's very strict compiler. It's not a matter of opinion it simply is more annoying than if you were to use any other language that does not put that much burden on you the developer.
Not all memory safety bugs are critical issues either. We like to pretend like they are but specifically in `coreutils` there were 2 memory safety bugs found recently.
However is it really a big concern? if someone has gotten access to your system where they can run `coreutil` commands you probably have bigger problems than them running a couple of commands that leak.