I work for s company that suddenly asked to rename a lot of stuff. This had consequences. It cost time, money, and created a disconnect between internal to the dev vocabulary that couldn’t be changed easily and user facing vocabulary. Also we were lucky but this could gave broken some long used API that we are proud not to version because the policy we have internally is “we will NEVER break the API”. And so far, for 8 years we still haven’t.

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.

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.

S-expressions are a hack because the Lisp devs didn’t know how to make an actual compiler, and instead had the users write the syntax tree for them. (For legal reasons I am being facetious).

Just for anyone thinking you are serious; https://en.wikipedia.org/wiki/M-expression I love how S-expression existed.

McCarthy had planned to develop an automatic Lisp compiler (LISP 2) using M-expressions as the language syntax and S-expressions to describe the compiler’s internal processes. Stephen B. Russell read the paper and suggested to him that S-expressions were a more convenient syntax. Although McCarthy disapproved of the idea, Russell and colleague Daniel J. Edwards hand-coded an interpreter program that could execute S-expressions.[2] This program was adopted by McCarthy’s research group, establishing S-expressions as the dominant form of Lisp.

I would suggest Helvix or Helvim

Technically, sleep sort is O(n), so faster than the theoretical optimal sorting algorithm O(n.log n) … not so bad ;)

I think we shouldn’t wait for the billionaires to disappear to make efforts.

Saying as long as billionaires are polluting I can still pollute as usual is simply dismissing our own responsibility.

Even though, I agree, billionaires should be the first to make the largest effort.

I think the message that want to be passed by this article is probably pro-oil industry. It gives a false impression that we could tackle ecology not by changing our habits but just be mad at a few billionaires. And this is factually false.

Unlike wealth pollution is more equitably shared among people. Here in order to demultiply the calculated pollution of billionaires they introduced thier industry and the pollution of their employees somehow.

And while it is expected these people pollute more. Getting rid of them will not reduce the pollution as one could expect.

unfortunately everyone, even not the wealthiest will need to change how they live to have a visible impact on pollution. broadly speeking, not just CO2, as we have a lot more ecological problems than global warming. Note the focus on global warming alone is also a strategy to hide the real changes that need to ne made in order to prevent humanity to hurt itself too much by destroying its own ecosystem.

Edit: As I am being downvoted it looks people probably misunderstood my message. I would gladly get rid of super rich people. But while this would help, we would all still need to make efforts. Until we accept that we should change our way of life, we will not solve our balance with our ecosystem.

“Hi computer! Write me a program that make money. I must just run it and I become rich.”

Can a line be a cat? I love kittens.

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.

https://gist.github.com/ericnormand/6bb4562c4bc578ef223182e3bb1e72c5?permalink_comment_id=4547071#gistcomment-4547071

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 positive for any Software developer in the long run. I totally see how this could be positive for CEO/CTO, Project Managers, in the long run, and I see a few short term advantages for Software developers.

Let’s be clear, I saw that coming since Microsoft bought Github, and I am scared by the direction this is taking. The end goal is to move more and more control and power to non-software people about Software development.

By forcing every developer to not use their own tools this will have a lot of advantage for CEO/CTOs but this is terrible for software developers:

1. telemetry: they will try to find a formula to assess who are the best performer in a team. And as with SEO, any formula could be gamed, the best at this game, will not be the best software developers, but the one that will learn how to cheat.
2. global team tooling enforcement: vim vs emacs etc… ? Forget about it, the only way to work on a project will be via this unique allowed editor.
3. assets protection: impossible to download the code on your local computer to use external tools on it. The only way to have analysis tools will be via these “allowed” analysis tools. This will make code analysis and experimentation a lot more difficult.
4. Locked by promoting vendor-specific applications. As you will focus to make your code/app/product work only for Google Cloud for example, you will naturally use Google-Cloud-only features that will make your code difficult (or impossible) to move to another Cloud provider, or god-forbid, host your product on a non-cloud or private made cloud.

And I can think of other possible drawbacks but my comment is already long enough.

• Real programmers code in C!
• NO! Real programmers code in Fortran77!
• NO! Real programmers code in ASM!
• NO! Real programmers code in binary!
• NO! Real programmers build their own hardware!
• NO! Real programmer code using bacteria DNA!

As you only mention git and not any git hosting. I would say you could easily use git hooks. Fir you and probably ask everyone in your team to install the same git hooks to have a chance to review changes before they are commited.

For my team there is an init-git-repo.sh shell script in our repository. When you execute it, it will install all the git-hooks fir your local repository.

You can use them to add checks during commit, merge, etc…

Edit: I read a bit too fast. As you are using bitbucket there id probably the equivalent of github’s CODEOWNER file as already proposed in another comment.

I am self-hosting forgejo. This is a gitea fork that focus on provide a federated github if you want.

It works flawlessly with minimal amount of resources.

nix does not need nixOS to run but is a complex package manager. At least for me, it doesn’t seem more complex than docker ecosystem.

I personally use nix to take care of downloading compatible dependencies in isolation for me. And the rest of the code is really, just basic script shell or Makefile too.

I also could add a fancy mergeShells function I have written in nix to support a docker-compose-like composition of nix-shell files. But you could go a very long way with nix before you even want to do something like this.

I use a similar approach, but I went further by creating a system that compose like docker-compose would. The trick was to write my own nix function mergeShells.

https://her.esy.fun/posts/0024-replace-docker-compose-with-nix-shell/index.html

For now, I am pretty happy with it. Also, I put the init script inside nix-shell and not in external files and use exit signal to cleanup the state.

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 morons… Why use a computer if you don’t have full power?