The 'one weird trick' could've been spotted in a graphical bundle analyser. But are they not caching npm packages somewhere, seems like an awful waste downloading from the npm registry over and over? I would think it would be parsing four different versions of the AWS sdk that was so slow.
No worries, it's still broken by the way, I have an enterprise SAML log in for figma, not sure if that helps. I did want to demo this to my company, but maybe you are not ready for prime time just yet?
I think as always in software, "it depends". The author appears to be assuming there are no tests on all of these paths that we will apparently miss when we migrate the code over. If so that is a problem with testing rather than migration.
Also how messy are we talking? I've seen code at a bank where a junior contractor implemented, in reams of code, his own database locking primitives, apparently unaware that the db could handle concurrent accesses on its own.
Rewrites aren't such a big issue these days, this seems a little dated. The real issue where we get painted into a corner now is architectural, say if you went really hard down the microservices route and tried to back up out of it.
It was about maybe late last year/Jan this year. When you say intermediate language, do you mean PHP has a bytecode interpreter instead of AST? At the time I looked at it, to convince myself there was no issue with Ruby, I actually hooked up the same table/query to PHP and used PHP's excellent profiling tools, then compared those to the Rails profiler. There wasn't a great difference. PHP was faster sure, but there was definitely no knocking Ruby's speed.
I remember looking at BSON de/serializers for some perceived performance issue a while back, ruby was only marginally slower than PHP for the same task, which was just pulling big record sets back from the db. Can you elaborate?
I find now even in the office, people are so busy switching between being glued to their Slack or or video chat, then switching back to work, that it is harder to walk up to people and interrupt them casually. So I don't feel the quick bounce of an idea off someone is as smooth as it used to be, in my case, where my workplace has one thousand slack channels going all day. Also we don't have telephones, which I believe makes communication harder.
New to London. London transport is good when it works. One thing I don't get, compared to my home country, is why when the train employees strike, they cancel services? Back home they just refuse to collect fares, and open the turnstyles. That way the unions don't offside the public.
Do you mean to say Haskell hasn't solved the halting problem yet?