I worked at a company where one of the pieces of hardware we were building at the time used a PowerPC CPU (this is back in ~2007). We had a rack of Apple xServe for build and test. The xServe was nice pieces of hardware compared to the x86 kit we had, more like Sun gear in their attention to detail and ease of use.
At my current company we compile for x86 and devs can do a full build and test environment on their laptops (which are 95% MacBook Pros) but it is unclear what will happen when Rosetta support is pulled. Now the interesting thing is we plan to move our stuff over to target the AWS Graviton (and other cloud ARM cores) as those instances are cheaper for generally the same performance (for what was are doing anyway) so the point will be moot. There will be some crossover point where having build and test servers in a rack will be cheaper than doing it in the cloud. At that point having Apple ARM based servers would be a win assuming we can build a binary that works for Graviton, et.al.
I agree. You can watch a lot of the old races on various YT channels and also in the F1 app (assuming you pay for it). There are some great races but most are pretty predicable for the big teams with the money, baring any random engine blow-ups.
The real issue is the cars are just too big and heavy. There was a point in time when you could pass someone even in Monaco.
I am in tech (okay now I am really wondering what % of people on here are NOT in tech). I have spent years in Japan for work, and ironically right now as I type this, I am sitting in a seat on JL2 from Tokyo to SFO. I worked with all of the large Japanese companies over the years and I can say Fujitsu has always been the most impressive, and to you comment, most like golden age IBM (I worked there for a brief time also). They, like IBM are most likely to have brilliant tech, and then shoot themself in the head for non-tech reasons.
I agree. We have a leadership channel at work for well, the leadership team. Those conversations are sensitive. Evaluations, hiring bands, salaries, future product planning, markets, funding, etc. Access to that channel is strictly controlled. I am not worried about anyone taking a screenshot. In the case of allowing an AI agent to participate in the channel, I would be worried about that AI using information from that channel to answer a question outside of that channel. Keeping the agents "learnings" clearly behind a "firewall" would be of great importance.
Beyond that, the team are free to have private conversations between themselves. This is NOT something we log. At the end of the day, hiring good people and trusting them is important. The logic of making sure the AI does not leak those conversations also applies.
It is a new world, re:AI. It has its uses and things are changing at a rapid pace. It is not clear to be the protections we have implemented in todays paradigms are well implemented yet in the new AI world.
At my current company we compile for x86 and devs can do a full build and test environment on their laptops (which are 95% MacBook Pros) but it is unclear what will happen when Rosetta support is pulled. Now the interesting thing is we plan to move our stuff over to target the AWS Graviton (and other cloud ARM cores) as those instances are cheaper for generally the same performance (for what was are doing anyway) so the point will be moot. There will be some crossover point where having build and test servers in a rack will be cheaper than doing it in the cloud. At that point having Apple ARM based servers would be a win assuming we can build a binary that works for Graviton, et.al.
reply