Yeah I do like watching them and listening to them. I should just try going out without a camera. Haha I have a macro lens I have done a small amount of bug and flower photography with, but haven’t done much in years.

I mostly do bird photography, with a 600mm lens, so the activity pretty much has to be just the bird photography, because it is a heavy bag to carry and I have back problems.

I can never get up the energy to go out and do any anymore.

Well they (probably) don’t go to places like this because they have any indication it’s other people. They’re (likely) incredibly anti-social in “real” life and online is hear a video game to them with no “real” people on the other side.

Deno was created by the creator of Node. When he first announced deno he stated he was going to “fix” n number of issues with node. In his presentation with the n number of issues, I think only two of them weren’t the same dumb mistakes that he had made with node (but it’s been a long time since watching so I could be remembering wrong). As far as I remember, Deno was always going to end up just as bad as node if not worse.

You still need an email address…. which is functionally an account.

Complaining about needing an account to contribute is wild to me.

The first two or three examples are really bad but the rest are quite good.

The description of the post said “complex yaml files”.

JSON is not easier for most strings. Anything multiline for example.

But yaml is a superset of JSON so you literally can use JSON and it’s still valid YAML.

They mention their company numerous times over, sure doesn’t seem like a personal blog. It seems like a company discovering something that has been documented over and over again.

I think it might be broken on mobile?

Article written like it’s someone that just discovered types even though a majority of the programming world said to use types for decades…

Also I completely disagree with the assertion that you should write everything including backend in typescript in order to share types. You should be using a schema and generating your types if you are writing large systems. That way any service that uses your APIs can generate the types as well and isn’t locked in to your language.

And please dear lord stop writing backend code in JavaScript or typescript or any scripting language.

Other than that, yes, use types. They literally do exactly what every proponent of types has said they do for years. Turns out it’s a huge benefit!

Everyone is biased, some less so. Use something like media bias checker or Ground News and read what they say the bias is and why.

None of the complexity of GitHub actions would be solved with any other configuration language. It needs to be a full scripting language at minimum. The problems with GHA have nothing to do with yaml.

You shouldn’t write complex yaml files. Keep it simple and yaml is great. Do complex stuff and you’ll hate your life.

Awesome picture. I love the vibe

Ruby and Python are both scripting languages and have been since being invented. Static type annotations are a dumb thing to add to a language like Python and Ruby, they’re not static languages. If you want static typing you should be using a different language. The syntax is most definitely not worse, and that’s not an opinion, Python’s for comprehensions are nightmares of readability, and hardly make sense 5 minutes after you write them. Ruby prioritizes readability over everything else.

Speed is almost exactly the same, with Ruby winning on many benchmarks. The only people saying Python wins are Python programmers. There was a post on the clojure community the other day comparing specific instances and while clojure was winning them all, Ruby was in second on most of them.

Python only looks better from the outside. I spent years coding in both at the exact same time at the same company. The only two things Python wins on is number of packages, and even that is a dumb metric (looking at you npm), and Click, which is an absolutely fantastic CLI framework.

I haven’t heard that in 15 years. The main reason to use Ruby is that it’s a better Python. The tooling is 10x better, it has all the same language features and more, it has easily enough packages to handle any situation you want, and it doesn’t have all the bike shedding that Python has.

You shouldn’t be writing applications in a scripting language anyway. They’re for scripting, it’s in the name.

Whaaaaaaaaa!!!??? That is so helpful. Why does no one ever talk about this when working on userChrome!!!