tcmart14

Yes I know that. But you were saying track record. That's a 3 year old device. Let's not say they have a track record until they take a device cradle to grave in 8 years. A lot can happen in the next 4-5 years. Then you claimed Apple doesn't have a track record and they have taken a device, claimed 7 years and actually done 7 years cradle to grave.

Telerik has been around awhile and makes $60 million a year and their business model is selling essentially UI components at the heart of it for Microsoft UI frameworks. There is also SyncFusion and DevExpress.

Its crazy, but there is clearly money to be had in this.

Because 7 years from now, my iPhone will still have the latest OS and security updates. I also have the budget iPhone 16e. I also haven't broken a phone since I was 16. Not like cheap androids that are often abandonware by the device maker before they even hit the shelves.

It sucks. I wish that would change, but that is what made me switch from Android to iPhone after 12 years on Android. At the time, even flagship androids were lucky to get 2 years of OS updates and security fixes. Apparently Google and Samsung are going to support their devices longer, but I'll wait till they have a track record. But ultimately, an iPhone for me does come out cheaper over the lifetime of a device than cycling through cheap androids every 2 years.

I'd also add that the mobile gaming market on iPhone is the largest individual gaming competitor, at least by the dollars, and bigger screen probably enhances play experiences that can be had on mobile.

But its also hard not to be. I'm not a fan of Musk and it doesn't even have to do with Musk himself as its a common theme I see among a lot of the big tech companies or really any company doing a big project in my neck of the woods. An hour north east of me, there has been big on going data center projects for 10+ years. Sounds good right? I got a lot of family and friends in the trades. But I can almost set my watch to it. When work ramps up, its always good pay and 15 years of guaranteed work until suddenly its not. 8 months go by, suddenly everything is paused and all those contractors are out of work for a year and a half until things start up again. Then its rinse and repeat.

Never had a zune, but I did have an iPod. I am willing to accept Zune was superior. But its just an example that, yea, often times the superior solution doesn't actually win. There is a huge list of better technology that lost out to worst technology. Which is why I find it funny the claim that the market is optimal in choosing winners and loosers.

Shoot where I am at, it can also change on a week by week basis. This week, I can get away with some shit to improve the UX and depart from the mock up. Next week, if the feature doesn't look and function just like the mock up says that was handed in the case, I'm in trouble. No matter how bad it is.

My guess is, user list would be the least. Microsoft has this thing about getting you all warm and snug because they have a solution for everything. Need an IDE? VS Code and VS proper. Got your hosting needs (azure). Literally everything. You wanna build applications around AI. We got you too, along with the VCS to keep your app in and pipelines. Hey, go ahead and send us your data so your AI application is better because you're really just calling our models. Right, and this goes even further. Data is incredibly valuable. And here we are, now paying companies to vacuum up all our data. Every last bit. And I am just seeing GitHub as another way to get people in the door to do just that.

Probably the biggest thing that has me dumbfounded about everything in the AI space and the tooling in GitHub and stuff with co-pilot. They've figured out a way to make us pay them to steal all our valuable data. And to package it up all nice for them with a bow on it and not question it.

My only push back would be on the FREE part. I coulda bought that 5 years ago. Now I look at GitHub and go, "if the product is free, it's because Im the product" with all their co-pilot stuff.

I may have come out with a different interpretation than you did of GP's comment. I see how you got to yours. But the way I read them saying they should slow down was, maybe slow down on new features. Which would mean they could shift resources from new features to infra.

I think that is one thing about trying to study Shakespeare in class that can be improved. The class shouldn't just be taking turns saying the lines out loud. But you don't need a full theatrical production either or memorize lines. Read the lines with some light acting out of scenes with just the tables, chairs, and a small bit of imagination could be the class room study impactful.

Yea, its not one I exactly agree with. But it is what the team collectively as a whole said is something is important. So to the other comments acting like I am just being ridiculous. Everything I deny PRs on is something time and time again the team collectively agrees on when asked how code should look and the process and all of that. The team can choose at any time to change that and for some reason, enough people on the team when asked in a meeting if branch names matter a lot and if they should follow a certain format, its a yes.

That's on him to handle and it hasn't been a problem.