muhanga

Yes. Clisp to Java to Scala and to the Java finally. Every switch was to get more money. As a result in the end I got more money and more domain experience. Most switches were traumatic for a week and then it was back to normal.

If you use a programming language which behaviour depends on the symbols that you hiding 90% of the time (I am talking about line ends and whitespace types) you will have a bad time. No amount of gitattributing or autocrlf magic will save you. You will suffer and you will get a phantom bugs if your editor and diff viewer will not show you "whitespace" changes.

And at the same time any programming language that will break due to whitespace should be chastised and laugh upon. Whitespace type should never be significant modifier for behaviour.

Also YAML can fuck off right into the sun.

Clojure. Simple language for complex things. It also has java interop and Javascript interop and c# interop. So I will be fine.

Thank you for sharing link to the site! I have found 4 new terminal fonts to try.

Some might. I using Comic Code and Fantasque Code from time to time as it forces my brain to reinterpret "known" code and helps to find errors that way. It also help with minor dyslexia moments. I like Radon, except I fully hate how "i" character is looking it is a "z" with a dot on it. If there were variant with normal "i" I would consider using it.

And release zip contains a _MACOSX folder which is a clear indication of sloppiness and/or rushed release. ... and ligatures don't work out the box in JetBrains product IDEs.

And if only they slapped beta on this there will be not problem what so ever...

Will Amper kill Maven and Gradle?

If it works and it is free then maybe, but probably still not. Also it is a Gradle plugin, so it will not touch Maven at all. And it uses yaml configs... I do not like this at all 😀

Maven is very good for small projects and Gradle take a niche of Ant on steroids. Nobody in his sane mind will migrate from one build system to other until benefits of migration outweighs the burden of redoing all pipelines from scratch.

The problem with JB products that they are barely working now. If you step one iota outside of mainstream functionality then it will break.

Both Maven and Gradle integration are very very brittle. And also not really optimized for big projects with big amount of modules/sources.

And I love JB products. It saddens me to see every year I drops in quality of IntelliJ. And New fancy interface transition is just the mess.

Migration to the subscription based allowed JB to release more products but overral quality dropped.

And sadly one more font I will never be able to use due to missing support of non-latin characters.

Sadly some features are nice.

Game mods and Advent Of Code did it for me.

I did a small RimWorld mod and a parser for NoManSky internal format.

Creating both of them was a blast. I had fun doing programming stuff again.

Advent Of Code allowed me to try different languages in a small bursts of the different problems. Somehow I really like this format.

Assigning different vlans for devices should enable network separation. "Stuff" from different vlans should not talk to each other.

From my personal consumer experience I would say twitch streams and steam demo fest are my two main sources of new games to "put a pin". And on twitch I mostly watch small channels (below 200 viewers), with couple of exceptions.

I don't think that this is Angular specific. Long lived branches is a known problem in development world. So far I only encountered one solution/rule that worked (for me): long lived branches can only do nonbreaking changes. If you want to have a long lived branches and it will have a breaking change/feature, then you should first extract breaking behaviour to the develop branch and only then work in the long lived branch or feature.

This is obviously quite hard to do in some cases, but I didn't found anything else that works in such situations.