That sounds like the descriptions of the IPO purchasers (being the cash out providers for insiders) just before the last dotcom crash. They didn't know what it was but they wanted to be invested in tech.. anything they couldn't understand was going to have an absurd ROI, putting them in the rich crowd.

Like the nature of the dot com crash, if it ends like a pyramid scheme, that reflects worse on the state of finance and analysis of our industry than on the last "suckers" in another tulip season.

There is nothing inherently wrong with a briefcase, but I think the ideal use of large internationally recognized notes is to sew your life savings into your clothes before you sneak across the border to try to start a securer life.

The alternative to flight is fight.. The more you deprive someone of options in one direction the more often they take options in the other direction. But what kind of cold, sick people would like small arms skirmishes so much that they would fund bias towards them in international policy over decades under the guises like a pathological fear of chemicals?

But none of your examples are as cross system portable and "native/normal feel" as writing an app that only works in chrome/chromium.

For the decades leading up to this stage cross system GUIs with a few simple library dependencies have been an unachieved "easy" task. Web remains as frustrating as ever because now we need it to work on all non portable browsers even on platforms that supports better ones. Then we want new features at an alarming pace that GTK could never normalize across *nixes.

Using the only non-browser that I think sort of got cross system portability working as an example.. I don't think things functioned reliably against the weird m$, Ibm and gcj Java implementations. But since they aren't really GUIs themselves with bookmarks, and familiar menus, no one gets upset when you tell them to replace an odd Java implementation before running a Java program.

Why is native/normal feel the end-all-be-all of UI systems? I've never quite understood why this is so desirable. Or why the answer seems to be using a shoddy UI system stuffed in a browser frame.

Because chances are that whatever custom UI/UX design you come up with isn't going to be better (or even as good as) OS UI toolkits that've been designed by experts, battle tested for decades, and used for every type of application known to man.

Applications with native UIs also tend to give a a better impression of responsiveness, and they reduce mental load for your users since they're don't have to relearn much (if anything). They can rest assured that every button and popup menu and text field (for example) functions identically to every other such control they've encountered on the system and in other native apps. This is worth way more than most people think.

One easy example of this is text fields in OS X. Native text fields there all have a form of emacs key bindings built into them to make powerful text navigation and manipulation a systemwide thing. Every application built with Cocoa gets this for free, but more often than not applications using non-native UIs don't implement this functionality at all. This is highly frustrating when you've worked said bindings into your workflow.

>Applications with native UIs also tend to give a better impression of responsiveness

Not just an impression. They often are actually more responsive. Except when they hang, which does happen sometimes, but then so do web apps.

I know a great coder who refuses to start personal projects because he can't find UI libraries which are:

1. Cross-platform across mac-win-linux-android-ios 2. Built for a compiled language such as pascal or C++ 3. Built to use native controls 4. Integrated to registered libraries through an interface like activex 5. Accompanied by a UI builder with design-time and runtime states and component builders. 6. Easily integrated to embedded and server-side SQL.

Sometimes we impose too many constraints on ourselves and never actually start anything. Fear of success?

Good point. And actually, Delphi matches many of those bullet points. Expensive, though. (The promo of the free Delphi 10.1 Berlin Starter version just got over on Aug 9. First time in a a while, maybe, since Turbo Delphi Explorer.)

I think writing an IDE or anything else with editor integration during the editor wars would be a similar analogy:

- you could push one or the other

- you could try to support users on both side based on the editor variable

- you could go the new route where only users who care enough to invest do

- you could go the Jed simplicity route.

In the end, IDEs like jetbrains have the new route with plugins for the factions. Most lower investment cases do the Jed route which is more like web neutral. No one who pushed the unwanted editor on its opposing group seems to be still standing.

It is a good idea because you reduce the learning curve for end-users of application by the use of common controls. Think about the MS-DOS era, and then Windows came along, with the ubiquitous F1 key everywhere, Ctrl-P and Ctrl-S, not to mention the toolbars, etc.

I'm coming up blank trying to think of web sites and chrome based apps that provide a look and feel consistent with - and as performant as - what is offered by the native platform.

Visual Studio Code

They could be made portable if an equivalent amount of effort was spent devoted to that goal.

The French program as quoted is nothing like basic income. I've seen quite a few people just need a few bucks. The longterm risk of that and the likelihood that if they didn't get the few bucks they would need permanent safety net was sometimes pretty high.

For example, I knew a vet in college who came very close to dropping out, where a few hundred bucks the safety net never knew he needed made all the difference. I can only imagine what percent of their lifetime writeoffs come from having these condescending "shutup, we know what you need" safety net systems.

Give me money and I'll make you rich. Don't mind that I am spying on your allocators of money. More money please. My friends that I bought with your money want to sell crack on your streets, thats cool right? How about some heroin? More money please, I'm having trouble tapping the lines of everyone who has something bad to say about me. Oh I mean us.

And the last thing you need is those recruiters finding qualified employees in the US when you hire by h1..

I find that companies are very much opposed to seriously finding those matches where the employees are convertable since longterm employees cost twice as much as the untrained new hire in a role that now uses half their abilities. Further, if they are "certified" as competent in both fields instead of eliminated from the market as tainted goods, they can be snatched by better managed rivals who know how to get full value of a programmer-accountant instead of paying for both skillsets and not being competent to consistently manage profit from either one.

401k plans managed fairness by making sure your top and lowest employees got reasonably comparable benefits. It helped, but also lead to outsourcing the low roles. In this case, I think companies should be limited to h1s that cost more than the greater of: the average inflation adjusted salary they've laid off, the average salary they still have and the average market salary for the specific role. If that's too expensive for them, maybe its fine to let them workout their problems without crying about the labor market not matching their inconsistent needs.

It might not be sufficient, but I would no longer pay for education and do it "on the record" without first taking the equivalent free classes.

From what we know about human memory the practice of cramming a topic for 3 months is not helpful and just the result of resource costs.

I find these quotes very confusing, did they delete any words of criticism&support as well as the repost of the photo, and if so were they posted separately or together with the photo?

It seems like purely reposting a photo without comment could now be being called a post of support. While fb users can use whatever slang they like, I expect a media that assumes we don't know about these behaviors in the walled gardens and tells us what specifically was censored.

(Perhaps this seems like splitting hairs to FB users, but as a non-user of a communication network, I would tolerate a network that bans pictures of blue but not a network that bans criticism of its ban of pictures of blue. The latter requires government intervention.)

This could end well, or at least comically. I am sure the Saudis have a treasure trove of evidence on the source of Afghan war derived terrorism and the US is now equally compelling them to share it and hide it?

Killing Malcolm X might not have been enough to supress the theory that chickens will go home to roost.

And with wikileaks they have a convenient way to release that info while on the surface maintaining a friendly relationship with the USA.

Not sure what you mean about Malcolm X though. What are the chickens here?

Malcolm X got a fair amount of criticism for saying JFKs assisination was chickens comming home to roost, I.e. poor US policy brought the same back on them. In this case, the terrorist the US designed to attack Soviet forces now view the US as their enemy.