If you don’t want to go full Cloudflare you can mitigate DDOS using these kind of technique locally.
https://blog.nginx.org/blog/mitigating-ddos-attacks-with-nginx-and-nginx-plus
Cloudflare will be a lot more effective in case of attack. But I don’t think most people need more than a few mitigation rules. If DDOS really come, there are very few things you could do to mitigate anyway.
I think unlike Google, there are still many pure engineers that need to contribute to open source to be motivated and are still have some power.
I feel, but I am not sure, that for Google, thing have switched more and faster to the side of Big soulless corps.
Generally speaking my experience is that even in these big soulless corps there are positive and passionate people. But quite often they do not have enough decision power to have a positive impact.
I would suggest Helvix or Helvim
“Hi computer! Write me a program that make money. I must just run it and I become rich.”
malbolge
and just after haskell
I use this nice trick to use Clojure has a bash script. This auto-download clojure so this id quite portable and reproductible.
Previously I also used Haskell’s turtle lib that could run with a portable shebang and it could even be compiled later if you need more speed.
I don’t see how this could be prevented.
There are already many “small web” movements. With different proposals. Like gemini, sub-set of currently supported web standards (typically no-js, no-css, no POST, etc…)
But the monetized web is doomed to reach a point were it will be controlled in such a way that you will not be able to block ads, not be able to hide your pseudonymous identity.
I remember reading an article many years ago about the cat and mouse game between ads publishers and ad-blockers. The conclusion were that in the end, ads blocker will lose the final war. And with these kind of system we are closer and closer to reach it.
I think we need to collectively find a way to have sub-nets. For example declare that our website conform to certain sub-net properties.
The small webs are different for everyone. It would be very nice if we could put an HTML header that would list which small webs pattern this page is compatible with. And have a browser that would adapt to your preferences and also a way to filter your small-web preferences in search engine.
The closest to this we have today is probably gemini. But this a very small but friendly web. I am sure we could find other solutions to create an alternative “respecting his users” web.
“Do the right thing” in corporate speak generally means to obey some business conduct to prevent any risk for the company to be sued. Mainly, take care of interest conflicts. Do not personally contribute to hide such issue and there should even be an internal team taking care that if you tell the truth your managers could not retaliate.
Mainly, “Do the right thing” is about protecting Google. Not “Do the right thing for the world and strive for progress”.
Google stopped to try to create progress. Instead they just need innovation. This is what they are after. Innovation, not progress anymore.
This was a very great article to read whose title does not make justice to the content.
I think I kind of dislike the generalization on generation. To me recently there are simply a lot more people that see programming as a job and not as much as a passion.
I learnt programming as a scientific activity and not as a productive one. So this was driven by creativity. And many in my promotion shared these values. But even in my time, many were just interested in the job. And of course, these people were not as effective. They were mediocre in comparison to people programming in their free time.
And yes, there is probably a lot more people like this today, in particular in younger generation. But there are still a lot of people programming for fun in their free time in the latest generation. This is just, they are now hidden by the majority of more “normal” people. Because let’s face it. Attitude of people programming during the week-end for super long hours while still programming for work during the week is not sane and abnormal.
Edit: a big missing part is that passionate dev are not necessarily what company prefer. Because yes, they can do incredible work. But quite often I see company prefer to have few of them and a bunch of more mediocre but reliable developers.
The first pass of elm ecosystem solved it. Before elm, it was also solved by other frameworks. But people wanted to be able to reuse their components and not rebuild new ones. React provided the ability to reuse css, and dirty js code in the middle of your application. You already had an way bigger ecosystem because you didn’t have to learn and built a complete new system again.
Personally if I had the choice I believe a new start should start at the browser level. Stop supporting HTML/CSS/JS. Create a new app-centric DSL and not a document centric one like html/css/js.
Ideally something inspired from cocoa layout. And I am dreaming but not accept generic code on the client side and only support a small controlled API. It would solve so many security issues. Sure, the creativity in such an ecosystem will be severely reduced. But we will have a so much improved UX.