Big Tech is overvalued. The current PE ratios require the Mag 7 to grow to a size rivalling the US government, a scenario that won't go unchallenged. But there is still value to be found elsewhere in the broader tech industry, which will only grow long-term.
@devops_nk My dear scrum masters. Do your job. Cut people off when they start the ballad of the latest blocker. They will hate you for it, but yet you must persist. It's the only way. A standup that goes beyond 15 minutes is not a standup, it's a settle in and spread out.
@WSJ Eat a hundred jobs, produce one. Look, AI didn't kill jobs, it transformed them. I can't tell if the commentariat is intentionally gaslighting people or just criminally under informed.
@zacbowden The innovation is in the idea that "windows is a service". And don't discount ads in the system tray, online accounts, and center aligned start menu.
Gigantic companies trying to control the web is killing what remains of the open web, and various initiatives to "bring trust to JavaScript" are just the latest effort. Apps are a closed off walled garden and now the web must be so too, in the name of security. F.
@Hasen_Judi @dvassallo I was writing JS before Chrome existed. I know what I'm talking about, just don't have time for your absurdist nonsense where dom is only sufficient if you can constantly tear it down and rebuild it. Please buzz off.
@Hasen_Judi @dvassallo I have never tried that, it might actually perform alright. Regardless, it doesn't need to be that fast. When I say it's fast I mean it's fast enough. Regardless, I get the feeling we are not going to change each other's opinions. Have a good day ๐
@Hasen_Judi @dvassallo The DOM is fast but the API is non-ergonomic. frameworks start out well but gradually metastasize into utter monstrosities. Throw in cargo culting of modern webdev and you start throwing more frameworks to solve problems of previous frameworks leading to a layer cake of crap
@Hasen_Judi @dvassallo It's not that bad. But contemporary frameworks do a lot of throw away work - recompute the entire tree whenever the dom changes, create and throw away event handlers, instantiate objects like there's no tomorrow, repeatedly clone objects and then throw them away.
@aboodman@dvassallo Most frameworks are incredibly inefficient. @viperHTML demonstrated great performance many years ago. We trade runtime performance for supposed developer efficiency.
@commonnotcommon@ImSh4yy "But ui framework X is great, and then you need y for routing, and z for state management. And can't forget z* for normalizing your state, before you denormalize it with z**". It's all a combo of performative efficiency and cargo culting.