Hacker News new | past | comments | ask | show | jobs | submit login

At Google, no one wants to work on existing things. You must create new product/feature to get promoted. Then you move on and thing gets shutdown. This is direct consequences of their internal incentive structure.



The big problem here is that there are a lot of people that have spent a lot of money in buying quality hardware that isn't just for leisure, it's for protection. I'll cite my 4 Nest Protects and an outdoor camera as an example. If somehow they get "sunsetted" due to some Google whim, fad or Because They Can, then I'm going to be pretty p*ssed to say the least. Based on past experience I don't trust Google to act in the users interest.


It's especially annoying when you bought a product specifically because it wasn't a Google product and you had confidence that the developers would leave the devices fully functional for its lifetime, then the company gets bought out by Google and the APIs get shut down or sucked into some goddamn cloud service nonsense.


Google is notorious for abandoning past projects. They are of the "try everything and fail fast" variety, and I wouldn't trust my money with their hardware. Not even software, except for Docs and Gmail.


This is why I feel like Stadia is doomed to failure from the start. It took Microsoft failing for an entire generation, even when they brought some new technology to the table, to start seeing real mindshare in the video game industry.

I don't see Google running a service at a loss for half a decade.


News flash, it will.

All gadgets that are internet connected will stop working sooner or later, I guess with Google it is sooner.

This and privacy concerns is the reason I'm abiding anything IoT. Why should I purchase something that I can't own.


I heard that’s how PowerShell came in existence. Nobody wanted to improve conhost.


> I heard that’s how PowerShell came in existence. Nobody wanted to improve conhost.

PowerShell still relies on conhost.

Do you mean PowerShell ISE instead of plain PowerShell or do you mean cmd.exe instead of conhost?


You're right, cmd.exe not conhost.


It's not really possible to substantially improve either conhost or cmd due to backwards compatibility considerations.

The risk of breaking something for someone is just too high.


And some people dont realize the amount of work Microsoft puts into backwards compatibility. Just look at articles describing the leaked Windows source they describe Microsoft putting in code to path third party Windows software to make sure it still works.

This is also why Wine struggles from version / config to version / config. They cant account for every edge case the way Microsoft does / has. Microsoft by comparison has unlimited resources while Wine is just volunteers who can only test so much software.


They just announced Windows Terminal and even spent time and money on a marketing video for this yet unreleased product:

https://www.youtube.com/watch?v=8gw0rXPMMPE

Granted, conhost will stay for compatibility reasons and this is a new thing.

But it's open source: https://github.com/Microsoft/Terminal . And according to the readme contains the source for conhost.exe too.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: