But I've noticed that most people were happy about free and no restrictions while the automatic part mainly just got how is that going to work and will it screw up my server comments.
397 karma · joined November 5, 2014
But I've noticed that most people were happy about free and no restrictions while the automatic part mainly just got how is that going to work and will it screw up my server comments.
I personally don't want a fully automated process. Shutting down all my virtual hosts to let their tool pretend to be my server is a big NOPE.
There really is no standard.
I don't need any protection. All my data is UTF-8 so having to convert back and forth to the frankenstien 1, 2, 4 byte "unicode" type is waste of time, memory (space and bandwith) and just adds complexity.
So I will not be moving to Python 3 by choice. To me Python is Python 2. If there is no Python 4 by 2020 with proper UTF-8 support I'll just switch to another language.
The HATEOAS just combines the documentation with the protocol. No thank you. I'd rather have a good API document to work from and a fixed API rather than trying to dynamically figure out what's going on. Seems HATEOAS is more suited for interaction with a human rather than a machine to machine protocol.
It's ironic that you used the NOSQL vs RDBMS debate as an example to prove your point. HTTP is a transport protocol. While it has some support for being an API layer it is way inadequate for that purpose. Expanding it is just not feasible as most servers and clients don't even support all of the existing options.
So just use what's best designed for the task. HTTP for transport and JSON for data. Makes things a lot simpler.
I had to make my own buttons as having too many buttons would slow rendering of the page to a crawl. The gradient background was the speed killer.
Doesn't help that you can only remote debug the browser from a Mac.
Then we upgraded to 10base2 once the cards came down in price. Then finally the 4 port 10baseT hubs with a 10base2 uplink dropped in price. We had a 10 player game of Duke Nukem one night in my basement.
But up until now I have never seen a 10base5 network.
The backbone network and teachers network were token ring. Those connectors were huge.
If it's a site that's worth reading I'll overide the CSS with Stylish otherwise I'll just not bother reading the site. It's funny how many sites fall into the later category.
The computer labs were all IBM PS/2 model 30s running DOS. The servers were a model 70 running Netware. The school backbone was token ring.
The lab network ran on some oddball daisychain system. Telephone cable and the cards had two RJ11 jacks on them. Still trying to figure out what kind it was.
So back then I got experience being a Novel Netware admin while today I'd be suspended and facing charges.
Let's play a similar game with three doors, two goats and a car. But you get to pick one of two rules to play by:
A) You get to pick one door you want and get what's behind that door.
B) You get to pick one door you don't want and get the better prize behind the other two doors.
Pretty much everyone is going to pick rule B. So after picking the door you don't want I will open the other doors. If the car is behind one of those doors I will always open that door last. Does the last sentence make you wish you picked rule A to play by? Heck no. We already know that one of those two will be a goat. The order I open the doors won't change anything.
Even if I let you retroactively switch to rule A after opening the first door? This is what trips people up. They think they're getting new information and that their original door choice may be incorrect.
But in this version of the game it's easy to see that we're not changing our choice of door, we're changing from the better game rule B to the worse rule A.
So the correct choice is to always stick with rule B.
Now we map the rules onto the real Monty Hall game. Rule A is pick the door you want and stick with it. Rule B is pick the door you don't want and switch.
So the correct choice is to always switch.
YZD is Downsview