|
|
... of the arguments over which FOSS office suite had got most users, people should recognise that there have been at least 65 million users of them not using Microsoft Office.
This is a good thing.
mind you, Microsoft says there are 750 million Office users worldwide, so we have a little way to go yet.
its often not so easy - they need the power because of modern inefficient programs running on supercomputers - your web app goes slow, just add a dozen more cores and a hundred gig of RAM, and then wonder why the cost of hosting is so high.
As a result, you can take your business elsewhere, but they'll be charging as much. That power is not cheap in the first place.
It is time to reduce the requirements of our programs, I understand that datacentres are 2nd only to the airline industry for co2 emissions.
True,
They're both still pretty inefficient though, I've played a couple of games written in C#/XNA, they're ok, but there's a lot of grinding at startup and a lot of sluggishness after you've played for a while. Could be just general poor programming practice from games devs, but there's a fair amount of language "assistance" there.
except the little problem of major component updates coming in v3.51 and the server OS being released with v3.5 on it,so many of your bleeding-edge programs wouldn't run.
I think they fixed this by simply reducing the amount of development going into
Oracle... we don't care. Please just donate Java to the trash.
TFYFY.
Oh wait, you mean they already did that?!
but you're wrong.
The plugin is simply the vector that a great number of attacks use to infect your system, the flaws are still (mostly) in the JVM.
Don't stick your head in the sand and say "blah blah no flaws in java", as you're doing everyone a huge disservice. There are bugs in the JRE that are exploited all the time (check the security fixes Oracle publishes to see what these are)., and understand that removing the plugin simply means the attackers have a harder, but not impossible, time to hack you.
true, if you looked at the business you'd see the accounts and then panic you'd not earn enough revenue to pay your workers... then you might have a different appreciation for why management wants stuff to sell.
Microsoft's problem is not about that, its more like 2 different managers pulling the company in different directions, expecting incompatible features added so they each can build themselves up over the other team.
in fact, who came up with the summary "you're old so you can't be a coder no more"-type nonsense is what I see on the web from immature kids who don't know the old and good ways of working, all they know is the new let-intellisense-do-it-for-you way of coding and think they're the greatest.
I wonder if I should post to
ho well, anyway, another non-story for
no, Sinofsky realised they had this mess and did what he could to consolidate it - by scrapping the WPF team in devdiv and bringing the technology into the base platform division - so all the other layers on top of Windows could use it, rather than have it as a layer that sat between windows and the rest of the system. He also created the WinRT API to replace win32 - which was necessary as the dev div had gone off and made their own APIs that all the dev tools worked against - ie yet another layer. If they weren't part of Microsoft I'd swear the dev div was trying to become platform independent and provide dev tools for Mac or Linux, that's pretty much the direction they were working towards!
Sure, he also was responsible for the new UI that is Metro, but I can't help thinking that was a mistake driven by morons from marketing, not engineering.
It is normal for a lot of companies, but most companies are not so huge that they are about to topple over under their own weight of different, and incompatible, divisions layered side by side fighting for position.
It also matters because Microsoft is still a very important company.
Its things like this that I, as a manger, would like to hear - sure its all venting anger, but there's always some grains of truth behind it. And my job would partly be to figure out those grains and fix the problems causing them. FYI Microsoft, those problems look to be too many people not working together, effectively acting to make Windows the kind of system that will eventually fall apart under its own bloat of incompatible APIs and subsystems that seem to continually appear.
Its a shame they got rid of Sinofsky as it seemed like he was someone who had noticed this and was trying to pull things tighter together.
But you'd expect a company that is joined-up, has significant managerial talent and expects to produce a good, core product to do a little better than continually produce internally-incompatible extras - what he said about cmd.exe not being upgraded and getting powershell instead rings too true for everything at Microsoft (he did forget cscript that appeared in between them, and no doubt there will be another one sooner or later). The same definitley applies to serious system components, I know the dev div wrote WPF/Xaml becuase they just didn't want to work with the Windows team - think about that, a graphics display system that sits on top of Windows and appears to all Windows APIs as a black-dialog-box. things like that need to be part of the core system. not something totally incompatible slapped on top. And that's not the only one.
I understand Sinofsky got this abd tried to make things work, but I wonder how much politics supporting the status quo got in the way there and did for him? That's the biggest problem Microsoft has today - not technical but organisational.
Thunderbird with the Lightning plugin both connect to gmail calendar and email and work just as much as you'd expect from Outlook. I don't notice any significant difference, even though I generally use both from my phone nowadays.
Only you don't get the social-networking integration and cloud storage hell that Outlook 2013 wants you to have, and you can see tomorrow's meetings in your todo list. Crazily enough, the gmail option is a lot better than the exchange one from v2013 onwards. Just you wait and see when you get the Outlook 'upgrade'
As for admin - you get to outsource that to Google, for free. As long as you have internet (and frankly, if the internet goes down at your offices, people will either sit there not knowing what to do with themselves, or go to the pub anyway)
I don't know - Thunderbird and the Lightning calendar plugin do me just as well as Outlook and its inbuilt calendar does (better actually, since Outlook decided you didn't need to know what appointments you had coming up tomorrow something I found useful for early meetings)
Link the calendar with gmail calendar, and the email with gmail emails... you've got pretty much 100% of the functionality Outlook gives you. (without the flipping Facebook integration Outlook 2013 now shoves at you, or the integration with skydrive). I use it (when I can't be bothered to read my mail using my phone, which seems to be my default view of Gmail nowadays) and it just works.
If you need centralised user accounts, OpenLDAP does that, though its tricky to make that work with a bunch of Windows clients, it does work though its not out-of-the-box. This is how it should be, after all AD is just a fancy LDAP server anyway, but with a special Windows-only protocol that Microsoft had to hand over as part of their agreement with the EU (IIRC). Good to see the Samba team has finally waded through the walls MS must have put up and got samba 4 working as a full AD server.
a lot of Vampire ones no doubt - The Hunger was particularly relevant in that Bowie ends up drained and old which ties in with other comments about potential accelerated ageing of the young donors.
Very stylish film too, lovingly shot with lots of fabulous lighting.
Why on earth would I want to cram everything into a central repository?
because its then much easier to find what you're looking for, compared to having configs scattered all over the place. (eg the mysql config being 'somewhere else' that I can never remember)
However, there is no reason why that central repository cannot be a directory called
It was all so different before everything changed.