What is this horrible fascination with light grey text on white backgrounds?
It started out with the horrible fascination with the "flat" style whereby it was hard to tell buttons from boxes etc. It was hard to use, but art trumped* function.
But they were not satisfied whacking shadows and shading, they had to whack colors also. At this pace, we'll go back to monochrome uni-spaced character-mode UI's. Keep your ASCII art; it may get you a promotion from a young PHB who won't realize it's from 1982. "Wow, this is so modern and stylish. Good job! And can I have a copy of that 'visi calc' software you showed me? It's totally cray!"
After all, I've seen disco come back twice in my lifetime. UI fads seem in the same category as clothing and music fads. Oh right, it's not "UI" but "UX" now. Experience this!:
Git off my flat light-grey lawn! (drought made such fashionable)
* "T" word not intended to be connected with you-know-who.
IT job titles are indeed a mess. Often one does a little bit of lots of things such that to be accurate, you'd have to break down tasks by percentages, which would make job titles resemble URL parameters: Coding=50%, Testing=20%, Analysis=20%, Documenting=20%, AdministrativeBS=20%, Etc.
(Adds up to more than 100% you say? It's called "undocumented overtime":-)
Often it is a matter of personality and preference. Certain languages and/or frameworks attract certain personalities such that one size doesn't fit all. Try a different company or stack if you don't like the current environment and feel trapped in a rut. Since everyone who will give you advice prefers different things, in the end there's no substitute for actually trying.
The correct way is to make it an interface usable from any language. Then it matters not a whit what language you work in. If you do that enough, you can pretty easily migrate from one language to another, one interface at a time, and it simply won't matter to the rest of the code.
That can be a lot of overhead. Often one can't convert between language types one-for-one automatically, a human has to study the situation and choose the correct translation per usage point. Language-independent layers are often not easy and not free.
You should always do it properly because there may be malware half-way writing itself when yanked, and damaged malware can prevent reading of the drive. Most malware wants to snoop, not crash.
No, it's because Twitter's stated policy is to give more leeway to elected officials because they shape and give policy. Whether that's fair or not is another matter.
That means if you or I call somebody a "smelly cunt face", then they may delete our message or account. But if a politicians calls somebody that, it stays.
Some of the technology was related to military spy scopes, so there may have been some "military concerns" that mucked up inspections or followup. Being espionage-related, we outsiders don't get the full story.
USA should have more anti-trust rather than Europe having less. Oligopolies and monopolies degenerate competition and choice. He's talking out of the wrong end to fix the wrong end.
How about a compromise whereby Google puts their own apps in a clearly-labeled group/box/folder of applications, but still include the generic ones in the usual spot.
If there will be data association conflicts, then the service should default to the generic apps, but if one clicks on a Google app, it would say something like, "Foo data/service is currently associated with Generic App X, to change the data handling to this app, go to the..."
MS has too many ways to script OS-related stuff. They have the command window, power-shell and there are different-but-similar API's and languages they support (or half support).
Choice can be good, but it can also confuse and dilute resources. I don't want to have to learn others' 13 different ways of Windows scripting (guestimate). I can control what I use (if not dictated by the shop), but not what others use to write scripts in. Thus, it looks like I'll have to learn all 13. (I'm an app-dev, not a sys admin.) #IdontGeddit
Microsoft doesn't care about Walmart succeeding in retail, it cares about selling more cloud processing to Walmart, by making things more complicated and AI-driven, requiring more computing power.
Eventually that might be true, but in order to have a cash cow, you first have to grow a cow. Walmart is way behind Amazon in online retailing. MS is known to play the long game (or at least the medium game). Thus, it's in MS's best interest to help Walmart get big enough.
It's like teaming up with IBM.
But MS's cloud is more competitive than IBM's. Sure, they are both full of AI hype, but AI is only a fraction of the stack.
Slashdot Mirror
Let's counter with an ethnic look. I personally dig Mayan art. I can see it with a sort of Next Generation (Trek) feel.
It started out with the horrible fascination with the "flat" style whereby it was hard to tell buttons from boxes etc. It was hard to use, but art trumped* function.
But they were not satisfied whacking shadows and shading, they had to whack colors also. At this pace, we'll go back to monochrome uni-spaced character-mode UI's. Keep your ASCII art; it may get you a promotion from a young PHB who won't realize it's from 1982. "Wow, this is so modern and stylish. Good job! And can I have a copy of that 'visi calc' software you showed me? It's totally cray!"
After all, I've seen disco come back twice in my lifetime. UI fads seem in the same category as clothing and music fads. Oh right, it's not "UI" but "UX" now. Experience this!:
Git off my flat light-grey lawn! (drought made such fashionable)
* "T" word not intended to be connected with you-know-who.
IT job titles are indeed a mess. Often one does a little bit of lots of things such that to be accurate, you'd have to break down tasks by percentages, which would make job titles resemble URL parameters: Coding=50%, Testing=20%, Analysis=20%, Documenting=20%, AdministrativeBS=20%, Etc.
(Adds up to more than 100% you say? It's called "undocumented overtime" :-)
I remember back then a good many dot-com's merely gave stock options on top of rather ordinary salaries.
Well, if you perfect your Q# scripts, then maybe That Orange Guy will merely end up part of somebody else's universe.
or maybe not
Are they demoted to Customer Failure Representative if they screw up?
Where's the "Synergy Assurance Representative" on that chart? The PHB's aren't keeping up.
I'm just being an Agitation Engineer; colloquially known as a "troll".
Often it is a matter of personality and preference. Certain languages and/or frameworks attract certain personalities such that one size doesn't fit all. Try a different company or stack if you don't like the current environment and feel trapped in a rut. Since everyone who will give you advice prefers different things, in the end there's no substitute for actually trying.
That can be a lot of overhead. Often one can't convert between language types one-for-one automatically, a human has to study the situation and choose the correct translation per usage point. Language-independent layers are often not easy and not free.
You should always do it properly because there may be malware half-way writing itself when yanked, and damaged malware can prevent reading of the drive. Most malware wants to snoop, not crash.
The discrimination starts
They can when falling off cliffs.
I'd like to request help on de-whoooshing.
No, it's because Twitter's stated policy is to give more leeway to elected officials because they shape and give policy. Whether that's fair or not is another matter.
That means if you or I call somebody a "smelly cunt face", then they may delete our message or account. But if a politicians calls somebody that, it stays.
No, I mean USA should clamp down on MS, Google, etc. for typical anti-trust patterns of behavior in the USA.
Some of the technology was related to military spy scopes, so there may have been some "military concerns" that mucked up inspections or followup. Being espionage-related, we outsiders don't get the full story.
Elect a clown, expect a circus ... a bad circus.
USA should have more anti-trust rather than Europe having less. Oligopolies and monopolies degenerate competition and choice. He's talking out of the wrong end to fix the wrong end.
But we have 16 gorillas.
That his toupee size?
How about a compromise whereby Google puts their own apps in a clearly-labeled group/box/folder of applications, but still include the generic ones in the usual spot.
If there will be data association conflicts, then the service should default to the generic apps, but if one clicks on a Google app, it would say something like, "Foo data/service is currently associated with Generic App X, to change the data handling to this app, go to the..."
Hackers keep trying different variations, usually using bots. The quantity does not surprise me.
MS has too many ways to script OS-related stuff. They have the command window, power-shell and there are different-but-similar API's and languages they support (or half support).
Choice can be good, but it can also confuse and dilute resources. I don't want to have to learn others' 13 different ways of Windows scripting (guestimate). I can control what I use (if not dictated by the shop), but not what others use to write scripts in. Thus, it looks like I'll have to learn all 13. (I'm an app-dev, not a sys admin.) #IdontGeddit
Microsoft Bob will be their new door greeter
Eventually that might be true, but in order to have a cash cow, you first have to grow a cow. Walmart is way behind Amazon in online retailing. MS is known to play the long game (or at least the medium game). Thus, it's in MS's best interest to help Walmart get big enough.
But MS's cloud is more competitive than IBM's. Sure, they are both full of AI hype, but AI is only a fraction of the stack.