News for hackers. Stuff that matters.

ekeane

Re:Why Gelsinger was wrong for Intel on Sunday December 08, 2024 @09:40PM (#42362624)
Intel did a great job coming up with great ideas before everyone else, then killing them off once someone decided they weren't going to immediately make 60% gross margins. I'm constantly amazed at how quickly the company managed to throw away good ideas because it could only make 40% gross margin, or was going to take another few years to develop a market.
Re:Why Gelsinger was wrong for Intel on Sunday December 08, 2024 @09:38PM (#42362618)
Intel has a habit of coming up with great ideas, then deciding that they aren't immediately successful or immediately 60+% gross margins, so it clearly isn't worth following up. Intel's R&D department is a grave yard of great products murdered at the alter of Gross Margin.

Larrabee is one such product. It wasn't immediately great, and didn't immediately promise great returns, and didn't quite have a market yet, so it was killed. I can't imagine where Intel would be in the AI world if they had the foresight to stick with Larrabee.

Re:Why Gelsinger was wrong for Intel on Sunday December 08, 2024 @09:34PM (#42362600)
I was inside since Otellini (left last year). Otellini at least 'stayed the course' reasonably well. I never felt like the company was going to GROW, but at least not die.

BK is who did his best to sink the company, multiple mis-guided layoffs, bad top level hirings, and stupid direction changes every time he read a new news article. Don't even mention his absurd AMA on reddit where he couldn't stop using the ellipse and laughing like a 14 year old girl.

Bob Swan wasn't the guy who could right the ship. He was another Otellini type guy, someone you bring in to not mess stuff up. Pat was a great pickup for Intel, and his return was my first time hoping that Intel could actually survive and grow.

Unfortunately, he came by too late. Foundry STILL hadn't really made progress, and the rot in the rest of the company had set in too far. The brain drain from BK was still being felt everywhere.

Frankly, I still feel like Pat was the right guy, 10 years too late. He joined to right the ship, but by the time he came aboard, the ship had already hit the iceberg, and the bow was 30 feet in the air. And now he's being blamed for the ship sinking.

Re:Improving _Generic in C2y on Sunday August 04, 2024 @10:24PM (#41157664)
Presumably because the article points that out.
The clang driver is particularly bad at this. There is a frequent 'just add one more thing here!' in every section of the driver. Additionally, it is large, somewhat complex, and not very exciting, so those refactors/simplifications don't happen nearly as often as other parts of the clang code base.

The tablegen/macro-gen stuff DID get added at one point fortunately, but before that it was pretty rough as well.

Re:EU fines Intel $400M for blocking AMD's market access on Saturday September 23, 2023 @08:14PM (#37628874)
Eh? Intel stock is basically flat in that time. It was ~28 around this time in 2007 (IIRC, was my hire date), and its now 32.

Intel stock is a lot of things, but 'up 80%' hasn't been something true since the early 2000s.

ETA: That was 16 years ago I was thinking of, I forgot about the nasty dip in 2008. I misremembered, it was ~26 when I was hired, dipped to 18 the next year, and slowly climbed a while and has been around that $30/share number for ages.

Re:New C features in GCC 13 on Friday May 05, 2023 @12:18AM (#35825171)
That is a 'warning as default error', so for at least Clang16, it is still disable-able. The Clang code owner is on a bit of a well-deserved war-path against these, so they are likely to be completely illegal in the next version or two.
Re:Is It Snowing in Portland, Oregon? on Sunday December 26, 2021 @03:18PM (#29695922)
My parents had me do a driving school that specializes in inclement weather training. A few years ago, I did one at ProDrive at Portland International Raceway, and they have a car on a sled that reduces traction that is REALLY good for teaching kids this.

Definitely worth looking into in the PacNW.

Re:Intel Haskell Research Compiler on Thursday April 13, 2017 @09:21PM (#14112070)
Intel's compiler is written in C as well.
Re:Ask HN: Who wants to be hired? (April 2016) on Friday April 01, 2016 @12:57PM (#11406399)
Location: Hillsboro Oregon Remote: Yes (Please!) Willing to relocate: No Technologies: Modern C++, SQL, Networking, etc Resume: https://github.com/erichkeane Not very updated, but my linked in: https://www.linkedin.com/in/erichkeane Email: [email protected]

Currently seeking a remote Modern C++ position!