Earlier quoted context omitted.
So this works in theory until there is a really bad bug in some part of the code base and there is no one who knows how to fix it. Or it breaks some kind of migration plan. Or it is embedded somewhere on some architecture that slows down an important projects development. or makes an application incompatible with a future OS If they’re not going to keep a team dedicated to keeping it alive, then you get into a situat…
Microsoft still patched products so old they had lost the source code by editing the binary itself!
Google Kills Cloud Print
551–560 of 567 posts
Re: Google Kills Cloud Print
#552Earlier quoted context omitted.
I know it's beside the point, but you stepped on one of my peeves. Google doesn't have to pay their engineers "a lot". They don't have to keep sucking more and more wealthy people into a concentrated corner of California. They could open a modest office in Nebraska and pay some 5-figure salaries. They could hire some run-of-the-mill college grads to work on a "dead" project. They could cut their teeth on low-profile…
Recently Google has actually been low balling a lot of candidates and is nowhere near top of market. In many cases they are refusing to match competing offers, and are even offering people less money than what they are currently making
Google tried to lowball me all the way through, and asked me to share screenshots of actual emails from other companies to prove my other numbers. They increased the numbers but frankly, they weren't anywhere close to Airbnb/Lyft. They did not act like a company that would beat other offers for talent. My offer was in the AI Assistant team under Google Search, so it wasn't an orphaned arbitrary product team either. Broke my heart coz I was so keen on joining Google from the start.
Hope this helps somebody out there!
Re: Google Kills Cloud Print
#553Earlier quoted context omitted.
Contrast with Apple. AirPrint was introduced in 2010 and is still going strong.
AirPrint is a local service; it doesn't do what Cloud Print does. (The name is a clue.)
And to be completely honest, CloudPrint won’t do anything in a year.....
Re: Google Kills Cloud Print
#554Earlier quoted context omitted.
A lot of the responses to the parent are things along the lines of "well it needs to be owned by a team" and all the usual valid cost-related reasons why [x] can't be maintained, and of course that doing so is boring. Isn't this the kind of project that should be reserved for people in explicit learning states such as (for example) novice hires, new hires, and aspiring mangers who haven't done any management before?…
I think if they release it as OSS some people would eventually fork it and maintain it.
Re: Google Kills Cloud Print
#555Earlier quoted context omitted.
> Spend $1M in St. Louis and move 100 employees out of SF. ~100/100 SF Google engineers would change teams if they received a mandate that their team was relocating to St. Louis (or basically anywhere). Anyone who couldn't arrange to change teams would quit.
The fact that Google has 70 locations around the world, including 26 around the US, indicates that some Google employees are happy to work outside of SF.
Re: Google Kills Cloud Print
#556Earlier quoted context omitted.
Picassa? Could have open sourced it. There are a few others in the graveyard that were easily able to live on any infrastructure.
How do you know how much of Picasa’s code was intertwined with Google’s? Could it have been a profitable in going concern by itself? How?
It had a huge installed base, but of course Google would not sell user engagement in bulk, only in tiny pieces as ads. Advertising the things people take photos of is pretty straightforward too, another reason why Google killed Picasa instead of letting it free.
Re: Google Kills Cloud Print
#557Earlier quoted context omitted.
90s and 00s Microsoft was successful in part because they were an incredibly stable platform to develop against. 10 year support goes a long way, and if you paid enough money you could email in your bugs and get custom hot fixes made for issues that annoyed you. Even their /bad/ technologies had long term support. If you built on top of shiny new thing and Microsoft dropped it in the next release, it was still going…
Microsoft didn’t care about developers that was always a talking point. Microsoft maintained backwards compatibility because of a new operating system broke old code, companies wouldn’t upgrade and it made its money from operating systems. Apple doesn’t care as much about backwards compatibility because it doesn’t really care if you upgrade your operating system - especially on the Mac - or stick with your old one un…
Microsoft put an insane amount of effort into documentation[1] and sample code. They ran developer training programs around the world and published an actual magazine.
They funded the writing and publishing of countless[2] books for developers. They still run Channel 9, where they produce/publish long and short form technical content.
If you wanted to develop for a platform in the 90s/early 2000s, Microsoft had the best documented platforms with an incredible amount of samples to learn from.
[1] Each product team targeted at developers had a dedicated, non-trivial in size, full time documentation team. On top of that Microsoft would hire 3rd party software companies to start using early versions of new APIs and write large scale sample apps using those APIs. I worked on one of these samples apps, it was a complete end to end ordering system for a furniture store that included everything from a tablet pc app for the sales staff to use inputting customer orders, syncing to a database in the warehouse to get the order loaded on a truck, and the delivery driver had an application running to get a signature on delivery of the order. Since this was pre-cellphones everywhere, the truck driver's laptop stored data offline and when brought back to the warehouse it synchronized itself with SQL server using some features new to SQL server at the time.
That was one of thousands of sample apps Microsoft made to show off its APIs. Compare this to the modern world where the cloud database provider billing you by the hour is going to throw out a couple basic hello world examples and that is about it.
[2] Technically countable but a very large #
Re: Google Kills Cloud Print
#558Earlier quoted context omitted.
Microsoft didn’t care about developers that was always a talking point. Microsoft maintained backwards compatibility because of a new operating system broke old code, companies wouldn’t upgrade and it made its money from operating systems. Apple doesn’t care as much about backwards compatibility because it doesn’t really care if you upgrade your operating system - especially on the Mac - or stick with your old one un…
> Microsoft didn’t care about developers that was always a talking point. Microsoft put an insane amount of effort into documentation[1] and sample code. They ran developer training programs around the world and published an actual magazine. They funded the writing and publishing of countless[2] books for developers. They still run Channel 9, where they produce/publish long and short form technical content. If you wa…
There were no other platforms seriously in contention in the mid 90s and early 2000s. There was Apple circling the drain and Unix vendors were all over the place.
In today’s world, if you are a major corporation that needs help you have all sorts of “partners” that will help you with your chosen platform, information on any API usage is all online.
In the classic MacOS days in the 80s and early 90s, Apple had the multivolume “Inside Macintosh” series.
Re: Google Kills Cloud Print
#559Earlier quoted context omitted.
> They are also giving over a year of warning. That's plenty of time for people to migrate to a new service or figure out how to implement an alternative. Python 2 would like a word with you.
Except Python is a widely used language, and this is a simple service for end-users. You don't need to rewrite an app because they're shutting down cloud print.
[I for one remain convinced that we are totally going to figure out printing once and for all any decade now...]
Re: Google Kills Cloud Print
#560I don't think Google understand how essential product support is.. It's one of the reasons why Microsoft is extremely popular for the cloud ( I think). Microsoft is very clear on products which aren't SLA supported. The only thing I remember is killing Silverlight. And seeing .net core thrive, it was the right decision. But don't forget, that changing the direction of the company was made public with a new CEO, altho…
How was it the right decision? Silverlight was cross-platform, then they made a Windows-specific fork which is WinRT XAML/WinUI (most people don't realize this but this stack originated as a repurposing of the Silverlight codebase directly, it wasn't a rewrite), now they are apparently hoping to make it cross platform again (see e.g., https://www.theregister.co.uk/2019/11/20/winui_winrt_windows... ) It seems like the…
At the time, it was not easy to port WPF to core ( mostly because of System.Drawing), they did it now and it's a new framework.