Is there a rule that all old websites should work? If its being maintained then it will be reviewed and updated. If no then it's probably best that it is broken so people will know it isn't being maintained.
Old cars that do not meet current safety standards can't be driven on highways. old TVs can no longer be used without an addon tuner. Lead paint can't be used anymore, asbestos is no longer legal for insulation, Windows 95 isn't supported by modern games, etc etc.
The reality is that HTML from 2000 still works as intended but that's a coincidence. There's no good reason to use it as a reference for a browser in 2012. If you want to archive information, HTML is one of the poorest of options. It is a presentation language only, not a primary source or a data store.
No IE 8 is a heap of memory leaks pretending to be a browser. It never cleans up after itself, rudimentary DOM work brings it to its knees and generally it's rendering engine (Trident) is just a poorly written pile that was corrupted from the start to make it backward compatible with OS rendering needs and Sharepointe.
Microsoft has yet to write a render engine for the web. They still have to answer to too many masters in other product divisions.
Responsive design in its current form has been around for several years now. It was popularized in an article on A List Apart. The concept was to use media queries (very new at the time) to define CSS rule for different sized screens while using the same HTML markup for all screens. This was in contrast to the then standard approach of using server side lookups Ina DB such as WURFL to get screen sizes and then serve up different markup and different CSS.
JavaScript is not necessary or even desired as a part of it.
Jettas have a V4, we're talking about at minimum a V6 and often a V8. Big difference in price. There's a 5k difference between a V8 4.6 and a V8 5.7 liter engine for trucks and they don't have to fit it into a smaller compartment.
You do know that if you do not participate in G+ they can not collect more info and you can remove any profile info you put in. Don't think of it as a G+ account, for you it's just a GMail account. It's the same one you happily used to log in and manage search history, analytics, Picasa in its time, Google API keys, Google Play, etc. Same as it was.
Nobody complains that the new Chevy Volt isn't compatible with their set of tools they bought just last year to work on cars.
Nobody complains that the HE dishwasher they bought wont except regular dishwashing crystals.
Nobody complains that the new bike they bought can't use all the old tires they have from the last bike.
Nobody complains that the HD TV they bought doesn't have RCA cable inputs.
Why is that? Face it people, progress happens and sometimes you've got to let go of the old and invest in the new.
Luckily there is eBay and Craigslist where you can sell your old stuff to someone who can't afford the new shiny yet. Give them a break and sell it to them.
I'd have an extra 2k in my pocket each year. That's why it's not a good choice got me right now as the EV I would need is 10k more expensive and I don't have faith in that vehicle lasting >5 years just yet.
Actually it does. When the interfaces at the edge begin to fray, can't quite connect to newer more sophisticated interfaces, then software begins to wear out. Hacks are kludged on top to bridge the gaps but these too are a temporary fix and begin to require more and more maintenance, visibly breaking down at times. Then it's subsystems are asked to process too many transactions, a new automated feed is sent down its pipe and it just can't keep up, it's algorithms were not designed to handle this much throughput.
At this point the software is like an old building, remodeled a few times, new wiring run through old harnesses, plumbing that has been expanded but with a boiler room that can't keep up, a foundation that just isn't rated for what is being asked of it. Sure it was a fine building during its prime but sooner or later the wrecking ball is going to be called.
If it requires IE 9+ I'll piss my pants in shock and giddy joy. It's the only way Corporate will get off IE8. Web devs the world over (except in China) will sing the praises of all things Office 2013 and evangelize its sacred holiness to the masses.
All of those features mentioned are not part of Office. They are a part of Sharepointe with Office integration or they are a part of Exchange with Outlook integration or they are a part of any number of other integrated niche software available from Microsoft.
They are not included in Office.
Yes MS Gold partner organizations get all of this stuff and pay hundreds of thousands annually for it. It's still NOT part of Office.
Doesn't matter. California is at will employment. No contract can stop you from leaving or joining another company. If she breaks other contracts such as NDA they could sue for that.
Wow. Would it not be better to just have a chat with the parents of the kids? If the parents are also a-holes then feel free to sue them for negligence, but the school is not the children's guardian. Then those parents can turn around and sue the school if they can.
For sports you should only be suing if the referee is not stopping the game or the administrators of the league are not setting safe guidelines. If everyone is doing their job and kids are still out of control (even with penalties and game losing player removals) then you are back to the parents.
If you need secure modular code and that adds business value then it should be a story for the backlog. If it does not add business value then it should not be on the backlog. If you skip it and then realize it adds value then it goes on the backlog but in the next sprint.
It's really not that hard. Agile also means continuous improvement and that means the project is never done (though it may be put away for a few months). The backlog will keep growing with new refinements, enhancements, refactoring, bug fixes, etc. when you have enough work on the backlog (that isn't a blocking issue hotfox candidate) you begin planning a release, review the backlog, etc and start sprints.
If its a project with a hard stop eg a contracted project then these topics need to be assessed and decided upon early (do they add value to the deliverable). If not then that is the client's decision.
If you didnt get your stakeholders to practice agile (go to backlog meetings at least) then it won't work. They also have to participate. They should set business value (1-10 works) and provide clarity on what needs to be built. At the end of a sprint they see the work and add refinements to the backlog.
They should release it as a public BETA. That's what Apple did for the first year of OS X 10.0. I fondly remember how incomplete it was but how you could port lots of UNIX apps using X windows easily with a few linking switches in the make file. Nobody used it professionally, everyone loved it (except the printing houses, they had a huge investment in OS9 stuff).
Slashdot Mirror
Fireworks is better at it.
Is there a rule that all old websites should work? If its being maintained then it will be reviewed and updated. If no then it's probably best that it is broken so people will know it isn't being maintained.
Old cars that do not meet current safety standards can't be driven on highways. old TVs can no longer be used without an addon tuner. Lead paint can't be used anymore, asbestos is no longer legal for insulation, Windows 95 isn't supported by modern games, etc etc.
The reality is that HTML from 2000 still works as intended but that's a coincidence. There's no good reason to use it as a reference for a browser in 2012. If you want to archive information, HTML is one of the poorest of options. It is a presentation language only, not a primary source or a data store.
No IE 8 is a heap of memory leaks pretending to be a browser. It never cleans up after itself, rudimentary DOM work brings it to its knees and generally it's rendering engine (Trident) is just a poorly written pile that was corrupted from the start to make it backward compatible with OS rendering needs and Sharepointe.
Microsoft has yet to write a render engine for the web. They still have to answer to too many masters in other product divisions.
Responsive design in its current form has been around for several years now. It was popularized in an article on A List Apart. The concept was to use media queries (very new at the time) to define CSS rule for different sized screens while using the same HTML markup for all screens. This was in contrast to the then standard approach of using server side lookups Ina DB such as WURFL to get screen sizes and then serve up different markup and different CSS.
JavaScript is not necessary or even desired as a part of it.
Jettas have a V4, we're talking about at minimum a V6 and often a V8. Big difference in price. There's a 5k difference between a V8 4.6 and a V8 5.7 liter engine for trucks and they don't have to fit it into a smaller compartment.
You do know that if you do not participate in G+ they can not collect more info and you can remove any profile info you put in. Don't think of it as a G+ account, for you it's just a GMail account. It's the same one you happily used to log in and manage search history, analytics, Picasa in its time, Google API keys, Google Play, etc. Same as it was.
Makes you wonder if there isn't a strategy in there somewhere.
Windows 7: Corporate
Windows 8: Beta testing new stuff on Home users
Windows 9: Corporate
Nobody complains that the new Chevy Volt isn't compatible with their set of tools they bought just last year to work on cars.
Nobody complains that the HE dishwasher they bought wont except regular dishwashing crystals.
Nobody complains that the new bike they bought can't use all the old tires they have from the last bike.
Nobody complains that the HD TV they bought doesn't have RCA cable inputs.
Why is that? Face it people, progress happens and sometimes you've got to let go of the old and invest in the new.
Luckily there is eBay and Craigslist where you can sell your old stuff to someone who can't afford the new shiny yet. Give them a break and sell it to them.
Car pool, reusable throughout the day (not locked in a garage for 8 hours) and at night. Its like public transport but much more flexible.
I'd have an extra 2k in my pocket each year. That's why it's not a good choice got me right now as the EV I would need is 10k more expensive and I don't have faith in that vehicle lasting >5 years just yet.
Don't you have multi user systems? Each user logs in and voila - its their preferred skin/theme. No fuss no muss.
If not , I'd hate to be help desk there "why is the desktop filled with icons in the shape of a penis?"
My Great Great Grandpa's buggy got from point A to point B. Too bad they stopped making buggy whips, would have been a nice heirloom to hand down.
Until they see a competitor with faster cheaper processes, automated with smart tools, eating their lunch. By then of course it will be too late.
Actually it does. When the interfaces at the edge begin to fray, can't quite connect to newer more sophisticated interfaces, then software begins to wear out. Hacks are kludged on top to bridge the gaps but these too are a temporary fix and begin to require more and more maintenance, visibly breaking down at times. Then it's subsystems are asked to process too many transactions, a new automated feed is sent down its pipe and it just can't keep up, it's algorithms were not designed to handle this much throughput.
At this point the software is like an old building, remodeled a few times, new wiring run through old harnesses, plumbing that has been expanded but with a boiler room that can't keep up, a foundation that just isn't rated for what is being asked of it. Sure it was a fine building during its prime but sooner or later the wrecking ball is going to be called.
If it requires IE 9+ I'll piss my pants in shock and giddy joy. It's the only way Corporate will get off IE8. Web devs the world over (except in China) will sing the praises of all things Office 2013 and evangelize its sacred holiness to the masses.
All of those features mentioned are not part of Office. They are a part of Sharepointe with Office integration or they are a part of Exchange with Outlook integration or they are a part of any number of other integrated niche software available from Microsoft.
They are not included in Office.
Yes MS Gold partner organizations get all of this stuff and pay hundreds of thousands annually for it. It's still NOT part of Office.
Doesn't matter. California is at will employment. No contract can stop you from leaving or joining another company. If she breaks other contracts such as NDA they could sue for that.
I pay me taxes guv'ner, I don't see why I shou'dnt use them up every chance I get. Like me mum always said "you can't take it wit you".
Ah The League of Extraordinary Gentlemen, yes yes a fine film by all accounts (have not seen it myself but I hear good things).
Wow. Would it not be better to just have a chat with the parents of the kids? If the parents are also a-holes then feel free to sue them for negligence, but the school is not the children's guardian. Then those parents can turn around and sue the school if they can.
For sports you should only be suing if the referee is not stopping the game or the administrators of the league are not setting safe guidelines. If everyone is doing their job and kids are still out of control (even with penalties and game losing player removals) then you are back to the parents.
If you need secure modular code and that adds business value then it should be a story for the backlog. If it does not add business value then it should not be on the backlog. If you skip it and then realize it adds value then it goes on the backlog but in the next sprint.
It's really not that hard. Agile also means continuous improvement and that means the project is never done (though it may be put away for a few months). The backlog will keep growing with new refinements, enhancements, refactoring, bug fixes, etc. when you have enough work on the backlog (that isn't a blocking issue hotfox candidate) you begin planning a release, review the backlog, etc and start sprints.
If its a project with a hard stop eg a contracted project then these topics need to be assessed and decided upon early (do they add value to the deliverable). If not then that is the client's decision.
Ugh - Agile is over a decade old.
If you didnt get your stakeholders to practice agile (go to backlog meetings at least) then it won't work. They also have to participate. They should set business value (1-10 works) and provide clarity on what needs to be built. At the end of a sprint they see the work and add refinements to the backlog.
They should release it as a public BETA. That's what Apple did for the first year of OS X 10.0. I fondly remember how incomplete it was but how you could port lots of UNIX apps using X windows easily with a few linking switches in the make file. Nobody used it professionally, everyone loved it (except the printing houses, they had a huge investment in OS9 stuff).
MS could learn from that.
Uh. Any OS or Mail app worth a damn has smart presets.
OS X Mail.app has Gmail as an account type. Select it and all it asks for is your username and password. Done. It's even part of the OS set up.
You can also pick me.com, hotmail, yahoo, Exchange or Advanced (custom).
At no point are you asked for a server or setting for anything but a user and pass, except with Exchange and Advanced.