2,674 karma · joined October 4, 2010
I don't comment on things I haven't read or watched, but it's clear not all of us do that.
Parents are not required to do any of that.
Texas has problems, but this isn't journalism.
Ghost kitchens are still a great idea, just not one that will support nonsensical WeWork hype and money.
Then they bill for their time and 'expertise'.
It wasn't worth $44B when he bought it, so I'm not sure why the NY Times would even use that number in any way. If I pay someone $100,000 for a stick they found on the side of the road, it doesn't make that stick worth $100k.
I doubt Twitter was worth $19B even before Musk overpaid for it. It was a 15 year old company that couldn't make money.
The key is that they wouldn't know either. It could be a slow 'death by a thousand cuts' and they wouldn't even know they were bleeding.
This is why companies, even massive companies, generally die eventually. There are very few that last even 50 years without eventually being acquired or bankrupt. And how does it start? Little mistakes, lack of focus, everywhere.
He told me repeatedly that companies that lay off the moment a bad quarter appears - or if they lay off employees if they even think the market will slow down - are always terribly run companies.
He said it was a clear indicator of poor internal planning and forecasting, that any company who suddenly needed to shed 5,000 or 10,000 employees on one bad quarter was was one to avoid.
Next.js fixes quite a few of the initial problems with using React even though there's still some stupid and even some new stupid introduced.
I'm definitely building in Next.js now, not vanilla React.
I think the problem is that SPAs are limited in use, but a lot of devs ONLY build SPAs and that creates a mess. Before Next.js, if I was building anything other than an SPA, I'd really have to wrestle with if I should build it in MVC or React...because it was a lot more trouble in React to do it well. But I don't have that problem with Next.js.
I suspect that people struggling to work with Next.js from React don't have the experience of web app development before React existed, so suddenly they are faced with the same learning curve of people who had to figure out React when they were used to full-stack development.
Now that I've been on Mastodon and Lemmy, it makes more sense, but this is a HUGE barrier to adoption.
For example, if Bob at ABC Company is working on an MS Word doc, yes, Microsoft can steal that data. But it's worse when Teams is on a corporate network, because maybe Bob has a Teams meeting, pulls up the Word doc, discusses it with coworkers Sarah and Bill, and now Teams tracks the doc, the conversation, who was in the conversation and what the conversation was about. It tracks the email conversation that follows. All of this is proprietary information. Teams has handed Microsoft the internal working projects, context, thoughts and strategy of ABC Company.