Agreed that it’s an entirely acceptable position to try and avoid being stuck in the crossfire of cyber warfare. Let’s be clear though, cyber warfare is already going on and Russia+China are pulling no punches routinely wiping American and European servers in various ways. Anyone on the front line of cybersecurity sees them knocking ceaselessly.

Whether it is being offered to the end users as free (as in freedom) software or as paid closed source has the usual implications. Ease of use, accessibility measures and support impacts inclusivity. Supported languages (natural and programming) will influence further who uses them or not. What constitutes the user base will determine what’s it’s used for and in turn will apply pressure to the editor to take a certain direction.

Political impact is not always obvious and not every single grain of software will be infused with a powerful one. The point is that our choice is either to ignore it or to acknowledge it. We can’t opt out of the world; blind neutrality is as political as any other position.

I would like to offer as a counterpoint that everything is political. Tech is no exception. Tech is a tool, a tool comes with a specific affordance and an affordance suggests to the wielder a certain worldview. To wilfully ignore the social and political impact of one’s work does not protect it from the world’s turmoil.

• C++ is fine
• Python is fine
• C# is fine
• PHP is fine
• JavaScript is fine
• C is fine
• Java is fine

I could go on

Also chaotic neutral: prioritizes issues by curiosity.

Only part I miss from going at the office. It’s not the same when you have to bake your own bribes.

If it listens and nods to the unedited, director’s cut version of my woes and frustrations, I’ll give it a cookie.

Or a crab.

It’s fascinating how s-expressions are both data type and language syntax. Such power. Only other time I saw something remotely like this was XSLT & XML, which I admittedly do not miss one bit.

Are passionate about the development lifecycle of other engineers and their pain points.

If you’ve been coding for 55+ years, you’ve almost gone through a whole engineer life cycle and you most probably know a lot about pain points.

How do you produce the coffee to power the rust users?

Holy crap that’s a lot of devs 😳

Team of three. We do the feature branches, pull requests and code reviews. With the right culture, it keeps devs informed about the various projects and gives a nice space to discuss about the practice.

EDIT: we do automated linting and formatting checks too. Keeps things coherent.

Oh this is interesting, but how do we get identical twins then? How come we get two gastrulation processes doing the exact same dance side by side, if not DNA?

Also I didn’t know about Copy Cat. Being a clone and coming out nothing like the original, what a cat thing to do. They’ll wiggle out of anything, them adorable bastards.

A lot of sectors need custom software and some of them have a mission more noble than profits. Government, education, science, culture… IT jobs in non-tech places can be rewarding too and you’ll get to have plenty of colleagues that aren’t your classmates. Being knowledgeable about various open source software can be valuable as well career wise.

On présente souvent l’innovation et l’évaluation de la performance basée sur les résultats comme deux bonnes choses, mais d’expérience les deux mises ensemble peuvent se refermer sur l’employé comme un piège.

Si on innove franchement, on prend des risques. Nombre d’expérimentations ne déboucheront sur rien et une évaluation trop bêtement basée résultat classera ces essais dans la catégorie des échecs, aux dépens de l’employé. À terme, l’employé apprend essentiellement à rester dans ses ornières pour sa propre sécurité. L’organisation ne peut pas compter sur l’innovation si elle met le fardeau du risque sur le dos de ses forces vives.

Nooo not the hivemind jokes again :(

The real joke is these comments lamenting unpopularity get to be the most upvoted.

3/14 is a weird way to write March 14th, but April 31st is just not happening.

This is an advertisement for a commercial editor. The blog author is the CEO of said product.

If you want your writing to still be readable on a computer from the 2060s or 2160s, it’s important that your notes can be read on a computer from the 1960s.

Was that blog post stored on punched cards just in case? I’m nowhere near pretentious enough to waste effort on making whatever I’m doing readable in a century, whatever method that may be. Nobody knows what computing will look like in one hundred years. Trying to solve problems that don’t have any guarantee of ever existing is bad practice.

Today, we are creating innumerable digital artifacts, but most of these artifacts are out of our control. They are stored on servers, in databases, gated behind an internet connection, and login to a cloud service.

Personal devices die at least as fast as the servers making up the cloud. Someone’s iPhone is not a place to store stuff for posterity.

These days I write using [yaddi-yadda] It’s the plain text files I create that are designed to last.

Plain text might be great for a writing app, but it’s not doing anything for video, graphics or audio.

Author should take their own cue and stick to chiselled stone tablet given the obvious importance of their work for the future of humanity.

No biggie! The birth of JS is told in numerous different places (and ways) on the net, if you’re curious you should definitely look it up.