And they probably don't dare to do Heinlein's Glory Road, but maybe Citizen of the Galaxy.
Then you can also look at movies that have been successful despite the Hollywood stance.
I'm waiting for Valerian and the City of a Thousand Planets to come out right now. And don't complain that it's a Star Wars rip-off, it's actually the other way around. And given that it's Luc Besson that has directed it I have a feeling that it may be at least decent. It may not be on the level of Leon or Nikita, which are the movies Luc Besson is rated against in everything he do - even if it's not outspoken.
I don't mind HTTP and HTML, they work reasonably well. The problem is all the ads injected/embedded from other sites than the source site.
What really worries me is that today some media outlets instead develops their own apps for reading their content where they claim that it will be a faster and better experience. I don't trust them and I see a risk with installation of apps because then the app has more ability to do suspect stuff on my device than what's normally possible with HTML and some JavaScript.
Which means that you live at about a measely 64 degrees North - and I understand what you talk about as I have lived at 67 degrees North. There are two seasons, mosquito-free and mosquitoes.
Just get to work early and you can leave early so you will get more daylight after work. When you work in an office you don't need daylight anyway so why let it go to waste?
Then give them a part to work on and tell them to break it down into pieces no larger than about 40 to 50 rows, let them also write code that tests their code so that they can explain what each piece do.
Today the tools for maintaining code are a lot better than what many of us suffered in the 80's. If we were lucky it was 'vi', not 'vim'. Or on other platforms like OpenVMS it was "EDIT/EDT". A few here may remember EDLIN from DOS. Then realize that in the beginning programmers coded on punch cards that had to be loaded in correct order. Darn the person who dropped the box of cards and had to sort them out in the right order.
The programming environments today are good at detecting coding errors on the fly before compiling as well as offering ability to refactor code with ease.
Not everything works out, but the pieces that do came at the right time with the right functionality. Just because someone failed doesn't mean that you shouldn't try since you may have the correct flavor at the correct time.
One problem for large banks is that they are tied down in systems written in Cobol a long time ago where only few persons have a good grasp of what the system do and with parts that nobody dares to touch because it works but nobody knows why since the person who wrote that stuff once has passed on to the afterlife.
What you list is one side of the coin - trying to get too much under one hat. You'd better turn to FVWM2 or something to get a lightweight non-bloated platform.
But the other side of the coin is that with openness you get interoperability - people can build their own applications interacting with your platform. The sum of the parts is greater than the parts themselves. The alternative is a lot of manual labor moving information between systems with the result that either the job isn't done or it's prone to error as well as being a lot slower.
Just look at the Linux kernel - it's found "everywhere" these days, and is a framework that's possible to adapt to new hardware by adding new drivers and you can remove unnecessary parts relatively easy. It's the core of many different Linux distributions ranging from small ARM to huge multicore NUMA architectures. Developers of applications for the Linux platform can therefore develop on a PC even though the application then is re-compiled to be executed on an embedded system or on a massive supercomputer. That's the point behind openness, and it started almost 50 years ago when Unix was conceived because Multics was too closed. However it didn't really take off until Linux came around where people discovered an OS that could be adapted to their solution with no heavy strings attached in the form of licensing, just navigation around the GPL constraints which aren't that cumbersome compared to Oracle or SAP licenses.
No, not even the web - just look at sites designed for a single web browser. Primarily sites for IE or Edge, but it used to be Netscape specific once upon a time.
Especially when you start to look at "necessary" plugins.
Slashdot Mirror
I wear ESD-slippers with socks.
Restructuring is generally a disaster waiting to happen.
Anyone that thinks it's a good idea to outsource to India.
And I wonder how this is really worth getting a patent for, it's a pretty normal procedure that many with a laptop has been using for years now.
And they probably don't dare to do Heinlein's Glory Road, but maybe Citizen of the Galaxy.
Then you can also look at movies that have been successful despite the Hollywood stance.
I'm waiting for Valerian and the City of a Thousand Planets to come out right now. And don't complain that it's a Star Wars rip-off, it's actually the other way around. And given that it's Luc Besson that has directed it I have a feeling that it may be at least decent. It may not be on the level of Leon or Nikita, which are the movies Luc Besson is rated against in everything he do - even if it's not outspoken.
There are a large number of books that they can use as a base for movies.
The reason is not that they are out of ideas, the reason is that they are lazy and just re-use what did work one more time.
Just give all their relatives a strain of HeLa.
I don't mind HTTP and HTML, they work reasonably well. The problem is all the ads injected/embedded from other sites than the source site.
What really worries me is that today some media outlets instead develops their own apps for reading their content where they claim that it will be a faster and better experience. I don't trust them and I see a risk with installation of apps because then the app has more ability to do suspect stuff on my device than what's normally possible with HTML and some JavaScript.
Which means that you live at about a measely 64 degrees North - and I understand what you talk about as I have lived at 67 degrees North. There are two seasons, mosquito-free and mosquitoes.
Just get to work early and you can leave early so you will get more daylight after work. When you work in an office you don't need daylight anyway so why let it go to waste?
Then give them a part to work on and tell them to break it down into pieces no larger than about 40 to 50 rows, let them also write code that tests their code so that they can explain what each piece do.
Today the tools for maintaining code are a lot better than what many of us suffered in the 80's. If we were lucky it was 'vi', not 'vim'. Or on other platforms like OpenVMS it was "EDIT /EDT". A few here may remember EDLIN from DOS. Then realize that in the beginning programmers coded on punch cards that had to be loaded in correct order. Darn the person who dropped the box of cards and had to sort them out in the right order.
The programming environments today are good at detecting coding errors on the fly before compiling as well as offering ability to refactor code with ease.
Not everything works out, but the pieces that do came at the right time with the right functionality. Just because someone failed doesn't mean that you shouldn't try since you may have the correct flavor at the correct time.
Please elaborate on what you mean.
One problem for large banks is that they are tied down in systems written in Cobol a long time ago where only few persons have a good grasp of what the system do and with parts that nobody dares to touch because it works but nobody knows why since the person who wrote that stuff once has passed on to the afterlife.
What you list is one side of the coin - trying to get too much under one hat. You'd better turn to FVWM2 or something to get a lightweight non-bloated platform.
But the other side of the coin is that with openness you get interoperability - people can build their own applications interacting with your platform. The sum of the parts is greater than the parts themselves. The alternative is a lot of manual labor moving information between systems with the result that either the job isn't done or it's prone to error as well as being a lot slower.
Just look at the Linux kernel - it's found "everywhere" these days, and is a framework that's possible to adapt to new hardware by adding new drivers and you can remove unnecessary parts relatively easy. It's the core of many different Linux distributions ranging from small ARM to huge multicore NUMA architectures. Developers of applications for the Linux platform can therefore develop on a PC even though the application then is re-compiled to be executed on an embedded system or on a massive supercomputer. That's the point behind openness, and it started almost 50 years ago when Unix was conceived because Multics was too closed. However it didn't really take off until Linux came around where people discovered an OS that could be adapted to their solution with no heavy strings attached in the form of licensing, just navigation around the GPL constraints which aren't that cumbersome compared to Oracle or SAP licenses.
The only exit is then to commit suicide in a spectacular way with a lot of spectators.
They only need to gain control, not get the whole package. Or they just need to control the owners.
Stranger things have happened.
Microsoft will soon buy Facebook.
Set up your own DNS server to gain direct access to the root servers and use DNSSEC.
And any 1/2" fixed width spanner is always 65/128 in width causing round nuts.
And they try to trap each other because they are run by different three letter agencies.
No, not even the web - just look at sites designed for a single web browser. Primarily sites for IE or Edge, but it used to be Netscape specific once upon a time.
Especially when you start to look at "necessary" plugins.
Just look at Windows, after a few releases you are forced to upgrade your software to support the new whims of Microsoft.
Except that JavaScript is worse than Java when it comes to the ability to debug.
All script languages are repeating the mistakes of classic Basic.
Just a virtual machine on top of the real hardware, like Java or for that matter any interpreting script language like Python.
It's not only a performance problem but also a HMI problem. You have different HMI devices on a Nintendo than on a stationary PC.
But most HMIs are compromises so there are things on a Nintendo Wii that's a lot better than on a PC even for CAD use.
In the end - if you make a solution that suits everyone, then it actually suits nobody.