"We're all working really hard to bring on rapture. How dare that pack of libtard yellow-belly commie snowflakes get in the way of our Armageddon. Let NRA bring us the Great RaptureBots like The Lord Jesus Christ wants! Stop keeping us from the grand shooting-range in the sky. And those are not harps, silly effeminate libs, but horseshoes; God's favorite game."
Javascript? That sort of defeats the purpose of server-centric control. Some client-side scripting may be desired in some cases, but shouldn't be the default or primary technique for common interactivity patterns.
When it was released in 1968, the opening scenes with apes, and them essentially turning into humans through evolution, would be sacrilege to many religious people.
That aspect has not changed much. If anything, skepticism of the findings of science have spread to climate and pollution research. The USA is "devolving" in that aspect.
[It left room for interpretation.] You can't blame Kubrick for seeing the reactions to Joyce and deciding: 'Incoherence is the key to staying power.' The audience will find what it wants.
It was the late 60's, and movies became like LSD trips. Sequence, logic, and coherency were out of style, kind of like the current White House;-)
I once created a blog for various rants with Google services and associated a grotesque avatar with it. It was the only Google service I used at the time. A couple of years later I created a gmail account, and linked my phone to it. People then complained that they saw the grotesque avatar on THEIR phone whenever I made a call. It took me a while to figure out how to disable it, and it seems local Android caching added to the cleanup delay. Other info also was visible across services, including Youtube, and relatives reported similar.
This is when Google was trying to out-Facebook Facebook at all costs, and tried to force sharing to kick-start their "social network".
In short, they shared my info across services without asking, or at least not making it clear. I'm hesitant to use Google for anything sensitive or controversial. They created an anti-social network; screwem!
It should be up to the user to decide what a given application has access to outside of standard binaries and user-app-data folder sets. If one wants an app to have access to stuff outside of those, then it should be an OS-level setting, not something the app decides, similar to a fire-wall.
If the app wants to show a tutorial to users for how to config their "folder fire-wall" to allow an app to outside of the sandbox, that's fine, but it should be outside of the app's control still.
In other news, Nancy Pelosi blamed the African Rift on Donald Trump
But it's huuuuuge, it's the greatest rift ever! And Mexico is going to pay for it...
East or West Mexico? It may spit also.
Seriously, though, politicians on all sides routinely blame each other for every bad thing that happens and take credit for the good things. Advice: don't get your "news" from politicians, period.
Auto-layout at the browser side is a nice ideal, but fails in the real world: each browser brand and versions has its own flaws and idiosyncrasies that must be worked around and tested.
Further, one should actually test on a reasonable set of sample screen sizes, OS DPI settings, and browser brands; if you want to do it right. That's a lot of testing. Now, maybe an elite UI dev can pull it off without the needs for combo testing, but that doesn't scale as most people are not elite by definition.
Doing "progressive" (self-scaling) right takes a hell of a lot of work, or at least selectively sacrificing certain things for simplicity's sake that the customer may not like. Things that should be simple are not simple.
Many techies don't want to rock the boat because UI fiddling is good money. But that's selfish thinking. Let's fix stupid tools/standards.
It's my opinion we need a new standard where the positioning is mostly controlled on the server. You can still choose "auto-flow" over WYSIWYG if desired, but that becomes a server-side implementation choice. The server scales the UI based on the device's (client) preferences or stated screen-size. Therefore, one is testing just one layout engine instead of 50+ needed for fat-client positioning of the current browser stack. It's logically better factoring so that your UI's can live long and prosper.
(The existing standards are still good for some things, I will agree, but not everything.)
They should buy up Cyc (Cycorp). If somebody finds a way to combine neural nets with knowledge-bases like Cyc, they could have something much closer to everyday common-sense. And, more trace-able.
Keeping up with the latest UI fads and trends is not an easy thing to do such that a dedicated front-end dev(s) should be brought in if an org cares about eye-candy and a wide variety of user device sizes.
But, if the applications are internal or business-to-business on a small scale, then a trendy UI may not matter much such that specializing by layers may be less necessary.
Slashdot Mirror
"That dress makes your ass look big"
You mean Tesla's autopilot turns you into a line divider.
Such are usually libertarians.
A more realistic portrayal of conservatives:
"We're all working really hard to bring on rapture. How dare that pack of libtard yellow-belly commie snowflakes get in the way of our Armageddon. Let NRA bring us the Great RaptureBots like The Lord Jesus Christ wants! Stop keeping us from the grand shooting-range in the sky. And those are not harps, silly effeminate libs, but horseshoes; God's favorite game."
No, read it again.
Bob/Clippy leading to Armageddon is among my top 5 nightmares.
No, that's the President.
"You want fries with that?"
"Yes"
* Blaaaapp! *
We don't necessarily want them fast, we want them safe above all. Stop thinking like Intel.
I suspect it was more like a jokish name when the site was small and informal, but the site grew in size.
Javascript? That sort of defeats the purpose of server-centric control. Some client-side scripting may be desired in some cases, but shouldn't be the default or primary technique for common interactivity patterns.
That aspect has not changed much. If anything, skepticism of the findings of science have spread to climate and pollution research. The USA is "devolving" in that aspect.
It was the late 60's, and movies became like LSD trips. Sequence, logic, and coherency were out of style, kind of like the current White House ;-)
Google is the new Microsoft, Microsoft is the new IBM, and IBM is in limbo.
The interactive parts are not an open standard.
Who gave it that name? That's a horrible name. It would be like naming a family horse trail vacation company "rash.com".
After it tears, it's "Raft Valley" for those caught in the middle.
I once created a blog for various rants with Google services and associated a grotesque avatar with it. It was the only Google service I used at the time. A couple of years later I created a gmail account, and linked my phone to it. People then complained that they saw the grotesque avatar on THEIR phone whenever I made a call. It took me a while to figure out how to disable it, and it seems local Android caching added to the cleanup delay. Other info also was visible across services, including Youtube, and relatives reported similar.
This is when Google was trying to out-Facebook Facebook at all costs, and tried to force sharing to kick-start their "social network".
In short, they shared my info across services without asking, or at least not making it clear. I'm hesitant to use Google for anything sensitive or controversial. They created an anti-social network; screwem!
It should be up to the user to decide what a given application has access to outside of standard binaries and user-app-data folder sets. If one wants an app to have access to stuff outside of those, then it should be an OS-level setting, not something the app decides, similar to a fire-wall.
If the app wants to show a tutorial to users for how to config their "folder fire-wall" to allow an app to outside of the sandbox, that's fine, but it should be outside of the app's control still.
East or West Mexico? It may spit also.
Seriously, though, politicians on all sides routinely blame each other for every bad thing that happens and take credit for the good things. Advice: don't get your "news" from politicians, period.
Auto-layout at the browser side is a nice ideal, but fails in the real world: each browser brand and versions has its own flaws and idiosyncrasies that must be worked around and tested.
Further, one should actually test on a reasonable set of sample screen sizes, OS DPI settings, and browser brands; if you want to do it right. That's a lot of testing. Now, maybe an elite UI dev can pull it off without the needs for combo testing, but that doesn't scale as most people are not elite by definition.
Doing "progressive" (self-scaling) right takes a hell of a lot of work, or at least selectively sacrificing certain things for simplicity's sake that the customer may not like. Things that should be simple are not simple.
Many techies don't want to rock the boat because UI fiddling is good money. But that's selfish thinking. Let's fix stupid tools/standards.
It's my opinion we need a new standard where the positioning is mostly controlled on the server. You can still choose "auto-flow" over WYSIWYG if desired, but that becomes a server-side implementation choice. The server scales the UI based on the device's (client) preferences or stated screen-size. Therefore, one is testing just one layout engine instead of 50+ needed for fat-client positioning of the current browser stack. It's logically better factoring so that your UI's can live long and prosper.
(The existing standards are still good for some things, I will agree, but not everything.)
They should buy up Cyc (Cycorp). If somebody finds a way to combine neural nets with knowledge-bases like Cyc, they could have something much closer to everyday common-sense. And, more trace-able.
Keeping up with the latest UI fads and trends is not an easy thing to do such that a dedicated front-end dev(s) should be brought in if an org cares about eye-candy and a wide variety of user device sizes.
But, if the applications are internal or business-to-business on a small scale, then a trendy UI may not matter much such that specializing by layers may be less necessary.
We solved that by voting for them so that they go to Washington. How's it going for them, by the way?
Simple, stop putting rats in your pockets.