I should clarify that by "what many people would ideally like to eat", I meant, "for the purposes of health". It just so happens that over time, my preferences have aligned with exactly what I was targeting for health reasons. Something to do with gut flora? I dunno.
Given that nutritional science is such a dumpster fire, I basically end up with a hybrid diet that's based on the parts of nutritional science that aren't too controversial: high in fiber, low-GI carbs only (and less carbs than most eat), fats are almost all "healthy fats", mountains of vegetables and fruit, and I try to minimize red meat.
I eat a LOT (and a variety) of vegetables, quite a lot of beans and lentils, quite a bit of fish, eggs fairly often, a low to medium amount of meat (about 50% poultry and 50% lamb and pork). I get some additional fats from olives (which I cook with fairly often) and nuts. Whole grains make it in there to round out fiber intake, but not in particularly large quantities. I don't enjoy or eat much dairy (excl plain yogurt, I love it), fried stuff, or processed carbs. The only thing I would change about my diet for health purposes would be to go fully vegetarian (for a combination of health and ethical reasons), but I just find that whenever I weightlift regularly, it can be difficult to get enough protein without meat.
This sounds like I'm unusually ascetic about food, but I actually LOVE food: before I started cooking, I would eat a different cuisine everyday, and now that I cook regularly, I try to rotate through at least a handful of cuisines (keeping every cuisine's ingredients around is tougher). My relationship with all the unhealthy foods that people crave tends to be analogous to how you probably feel about Pixie Stix: yes, to some degree we're wireheaded to enjoy it, but once you're out of the habit of it, it actually starts tasting pretty gross. The flavors are unsubtle and uninteresting, once you stop being used to the dopamine hit you get from it. This is how I feel about (eg) grilled cheese, or bread-heavy dishes, or the cheese and dough part of pizza.
I find them in recipes fairly often[1], and make tapenade sometimes, but they're actually pretty easy to work into many of the meat or fish recipes that I make[2], as long as the flavors are complementary. Hell, even my first regular,
staple "recipe" when I started learning to cook had olives in it and was super easy: a 3-egg scramble with chili powder, smoked paprika, baby spinach, quartered black olives and optionally a little bit of crumbled feta. Super fast, super easy, super delicious, and it came from just looking at my spice rack plus deciding that I wanted some Mediterranean flavors in my eggs.
This is probably made a lot easier by the fact that the cuisines I decided to focus on when I had to narrow it down for cooking were Mediterranean (excl Italy) + Middle Eastern + North Indian, and most of the Mediterranean makes regular use of olives.
[1] I'm relatively new to regular cooking, since the first few years out of college, Google fed me, so a lot of my cooking is still following recipes by the book
[2] I really enjoy Fish Veracruz, which is a good example of this
I mistyped in my previous comment: I don't make the eggs with Spanish olives, I make them with black olives. I find Spanish olives harder to cook with because the flavor can overwhelm other flavors, but I do eat them alone and every once in a while find a recipe that works well with them. I cook much more often with black and kalamata olives.
I compiled hello world in Rust into wasm the other day for the first time and it was incredibly satisfying for whatever reason. New technology is fun I guess.
Note: This page isn't rendering properly on iPhone
I'd say the most basic advantages a web app has for a user are no install, cross platform support and same look and feel across those platforms. These advantages may not seem all that important to the technically inclined but they are massive.
From the producer side: web applications are faster to prototype, develop, publish and monetize than desktop applications. This is also a massive advantage for the average application, cost wins.
The main advantages a native desktop application still has are performance, native look & feel and native feature support.
Purists will argue these native features are super important (they are in particular cases), meanwhile economics will keep pushing towards more web and electron apps. Such is life.
The no install thing is huge when you are working in a more enterprise-y context. Usually the environment is locked down so users can’t install software and it is a huge hassle to roll out updates, it took several weeks where I worked.
Also the users local environment becomes less of a factor.
React w/ Babel is undoubtably over hyped and yet surely its still a fairly significant value add over vanilla JS (when applicable) for how simple it can make state management and putting together UI.
Evergreen browsers, ES6 and etc are also make development significantly smoother in my experience, and I didn't even experience much before IE9.
That is is what drives me away from novel input methods and over-configured setups in general. On one hand it feels silly, but it feels a lot worse to be bewildered by a default setup.
I've used Dvorak as my primary layout for ~12 years now, and I'm just as capable at typing on QWERTY. Colleagues object if I set servers and test machines to a different keyboard layout.
The biggest struggle is words beginning "am" or "ma", the two keys which are in the same location on both layouts.
If you can learn to cope with changing between a Mac and non-Mac then you can learn to cope with changing keyboard layouts.
I'd recommend using only one layout when learning though: I switched solely to Dvorak when I was learning, then learned to use both side-by-side afterwards.
I use Dvorak, and it's only once a month or so that I type more then two words on a Qwerty keyboard.
If I'm helping a colleague, I expect them to type, otherwise they probably won't remember anyway. Otherwise, all I'm likely to type is a couple of letters to search for a name on the video conferencing system or a YouTube video on a friend's computer.
Can I ask how long did it take you to be touch typing on dvorak and how would you describe the benefits?
I like the idea of 'better' input methods including key layout but in reality I've found it simpler to stick to the defaults of the world. I'd be interested to hear your experiences
I learnt during the summer after the first year of university, when I was working on a small summer project at the university. It can't have been more than two months, probably more like one. I didn't touchtype Qwerty, although I could type fairly fast while looking at the keyboard.
I made the "tent" showing the keyboard layout, as described at [1].
It's simply more comfortable to use Dvorak. The clearest way I have to show that is by tapping fingers on the table: it's much easier to go small-to-large than large-to-small. On Dvorak, that means typing digraphs like sn, st, sh, nt, nh, th is optimized (Qwerty equivalent: ;l ;k ;j lk lj kj — what a waste of easy-to-type combinations!). The reverse combinations are rarer in English: ht, hn, hs, tn, ts, ns.
All the rare letters are on the bottom row, so the most awkward movement — bottom row then top row — is minimized.
Added to that, hand alternation is much better, which is also more comfortable. Taking my first sentence, "after" and "was" are all on one hand, and trigrams like "ear" (learnt), "rst" (first), "ect" (project) are common, yet ugly to type on Qwerty.
If you can touchtype Qwerty, type this to simulate typing the first two sentences:
G pdaolk hfoglu kjd ;fmmdo aykdo kjd ygo;k tdao sy flg.do;gktw ,jdl G ,a; ,sovglu sl a ;mapp ;fmmdo roscdik ak kjd flg.do;gkte Gk ialqk ja.d nddl msod kjal k,s mslkj;w rosnanpt msod pgvd slde
To remain closer to the defaults of the world, I've never bothered with Colemak or similar. I can add Dvorak to any computer I use, which I will occasionally do if someone asks me to use their computer to take minutes in a meeting or similar.
Thanks for the response! Typing that paragraph in dvorak definitely felt smoother than qwerty. The tent is a good idea for handling the switch, maybe I'll be a convert yet
Huh, that's completely opposite to my experience. Sure, I miss some niceties, but I can't say that I am anywhere close to baffled or confused by a default setup.
Your experience is unsurprising. It depends on how much time you spend in a default configuration and how disparate your config is to that default.
I have no qualms using default vim despite it not being my standard method of work, but I still hate the feeling of any case where some muscle memory sequence does not result in what I expect. Ideally I don't want to have to think about anything outside of the problem at hand at all, and this is exactly the kind of thing that breaks immersion.
Because of this, among other reasons, I like small configs, standard input methods, programs with sane defaults and having a simple dotfiles repo.
On this note I can't wait til the next best set of standard input/output comes along, like AR screen so we can move around freely and naturally while working... that's the dream
Can I ask what this consists of?