dfgdfg34545456

As my organisation migrates everything over to AWS I do find myself questioning what the costs will look like when it is all done and we are completely locked in. AWS/Google/Microsoft cloud services put you in the position of an almost completely captive customer. What large corporation would ever sign up to that?

The post seems to be assuming that multi threaded code is easy to build and maintain. From my experience it is horrible, every new thread means going from n bugs to nn bugs. As a programmer I prefer* async constructs in languages, and do not want to spin up and manage threads and all the state synchronisation that involves.

If TC39 Signals are merged this will be redundant. Signals are better than this as they keep track of the tree and don't do unnecessary traversals. With 'automatic useMemo' (this), the tree still needs to be fully traversed.

Looks like Farringdon that they end up at. Amazing video either way, thanks.

At a glance of that article they improved some of their furnishings and facilities. Is that the only thing you are considering when I refer to a carrot and not a stick?

"Rate limit exceeded." It appears another software law has been violated.

My thoughts on the office/home work management debate:

- Encourage workers back in with a carrot not the stick

- Be mindful of workers with families or other dependants who see wfh as a great benefit

- Don't count days in office and assess people on it - by doing this you are sending a signal that days worked at home don't count.

The problem with your question is that they are there to show off their knowledge. I failed a tech interview once, question was build a web page/back end/db that allows people to order let's say widgets, that will scale huge. I went the simpleton answer route, all you need is Rails, a redis cache and an AWS provisioned relational DB, solve the big problems later if you get there sort of thing. Turns out they wanted to hear all about microservices and sharding.

This article is trying hard to sound like it is based on years of learnings, but honestly every point in here just reads like it was cobbled together after the xz incident.

Thanks, that is helpful.

Java is better than Javascript, I'm mystified. I have used Java and Javascript lambdas, the Java ones use 4 times the memory of the JS lambdas and are slower, to do the same thing.

I like that typescript catches when I need to do null checks so I don't end up with the most notorious runtime error seared into the brain of every JS developer "cannot read property of undefined".

Some parts are nice, like the string literal typing "this" | "that". Other things are hacky, like "branded types", gross.

But then I think of my commercial codebase which is extremely well tested, regular old JS, and wonder if is worth the hassle.

>You’re putting yourself at a big disadvantage.

Why not just appreciate the diversity of opinion and move on, rather than lecture people?

In NodeJS for example don't you have use Buffers and special decoders to deal with UTF-8 strings? I.e it's a pain there too.

Thank you for the English lesson, but it's a big leap from this supposed connotation to "painting pet projects black".