So is abstracted crap only ok if it's already in the JS standard library?
577 karma · joined September 11, 2018
So is abstracted crap only ok if it's already in the JS standard library?
I have some knowledge, albeit very primitive, that I picked up from an HCI introduction and some good designers, but nothing too technical / formal yet.
As opposed to the very few questions about rxjs, where people understand everything perfectly.
I guess.
On my screen, the website is scrollable. Not sure if the animation needs to have top: 30vh and height: 80%
Also: there is a big layout shift right after loading.
const tokens = ['parenOpen', 'bang', 'plus', 'minus'] as const;
type Token = typeof tokens[number];
type TokenTable<T> = Record<Token, T> // alias for { [key in Token]: T }
const isToken = (t: string): t is Token => tokens.includes(t);
const patterns: TokenTable<RegExp> = { bang: /\+/, // rest }
Also, it appears to be feature-rich and yet easy to use for simple use cases.
If there is an upcoming meeting with a zoom/teams/<call app> link attached, you can join by pressing enter.
Never had to look for a meeting link again.
I'm not sure if Alfred has this as well, but nevertheless, i just love this feature
In a perfect world (for me, from my point of view), there are no deadlines, but rather short plans and enough understanding of the plan to decide whether doing something specific is useful or a hindrance (and to what degree) for executing that plan.
But alas, deadlines are easier to decide on.
After all, it is currently the nature of web software that the source code must be available (for browsers to interpret)
citation needed.
Other than that, I would love to see a bit better semantic markup, not because I'm some sort of HTML purist who demands everything to be pure, but because it would make it easier to style with CSS (which I did, to add dark mode, bigger font sizes and max widths). Currently, it's nested tables with occasional classes and ids, but not for everything.
> Do we really want to live in a 95% Chromium browser world? That would be a horrible future for the web. We need more voices, not fewer.
It's difficult to become a voice for Safari, if Safari is hiding behind a hefty price tag.
Debugging Safari issues on Linux or Windows machines make it easy to grow a disliking for the browser. There are ways to do it effectively, of course, but no simple or pleasant ones.
[0]: https://twitter.com/jensimmons/status/1490747578526404608
Why would I engage in the dance of crypto just to host some content no one will read anyway?
What's IPFS?
So.. not anywhere.
Or can the data be available in a highly fragmented fashion _and_ still be useful? I just can't imagine any content system that does not end up being centralized or highly inconvenient.
And probably spending an absurd amount of money for more or less Auto-Generated art?
It's really useful because it will even understand Angular2 codebases and autocomplete custom components in html snippets.