that said, i wouldn't even worry about your accent. oftentimes, it's a great piece of conversation fodder, and a connection to your past that you take with you where ever you go.
9,767 karma · joined January 23, 2014
[ my public key: https://keybase.io/clairity; my proof: https://keybase.io/clairity/sigs/ma5o_Z3EY_dqOeB7SVbxVEV9kRTXFx0l4kYLtxhMvc4 ]
that said, i wouldn't even worry about your accent. oftentimes, it's a great piece of conversation fodder, and a connection to your past that you take with you where ever you go.
i'd disfavor a national LVT however, as i disfavor more power being concentrated in fewer hands. it should be a state level concern at most.
apparently <dialog>'s still needs some accessibility/interaction improvements to be a first-class solution, but it's getting there: https://nolanlawson.com/2022/06/14/dialogs-and-shadow-dom-ca...
in my neighborhood, laborers use blowers to blow shit randomly into the air and the gutters (and into my windows) rather than being picked up and put in the trash/compost bin. blowers create pollution via that random action as well as via their exhaust, and that pollution combined with their ineffectiveness make them a net negative to me, not the noise. while i don't love noise either, any outdoor labor will produce some noise, so noise is unavoidable, which is why it's limited to working hours by statute (after 8am).
car/motorcycle exhaust noise, on the other hand, is entirely artificial, unnecessary, aggressive, and offensive, and should not only be banned, but punished heavily.
yes, other countries (including the US) have done this too, but in this case (and many other cases), it's a civilian, not a gvernmental or military member, who has been pulled directly into the crossfire, and that's the core "wrong" here.
yah, this is something i learned when designing my first server stack (using sun machines) for a real business back during the dot-com boom/bust era. our single database server was the beefiest machine by far in the stack, 5U in the rack (we also had a hot backup), while the other servers were 1U or 2U in size. most of that girth was for memory and disk space, with decent but not the fastest processors.
one big db server with a hot backup was our best tradeoff for price, performance, and reliability. part of the mitigation was that the other servers could be scaled horizontally to compensate for a decent amount of growth without needing to scale the db horizontally.
despite the rumors, i don't think we see the headset in the next 3 years, and we won't get an apple car in the next 7. there's no competitive nor wall street pressure for either of these rumored product developments (as in, there's no threat to apple if these aren't released sooner rather than later).
i will say the headset fits apple's future product roadmap better than the car, because apple wants to firmly own personal computing tech, which is increasingly miniaturizing and becoming more pervasive/integrated into our lives. the car is a nice extension, but not core to that vision. even apple home is more central to that vision than the car.
processed foods only comes in a box, bag, or can; that is, most of the center aisles in a grocery store. buy mostly fruits, vegetables, meats, seafood, and dairy--things found on the outer ring of the store. if you want grains or beans, prefer buying the grains/beans directly, not the boxed form of them.
so looking at the source, the html is invalid (no title, for example), it eschews the lowly <p> tag for multiple <br> tags, the chemical structures are practically unmaintainable, monospace is not very readable for paragraphs of text, and it extensively misuses a deprecated element, <tt>, for the monospace font. seems less an example of ingenuity, and more hubris. these things could be fixed in less than an hour, but apparently that's wasted time (they do better with their blog, since that comes by default with wordpress).
with that said, the goal is ambitious and noble, but it harkens back to alchemists trying to make gold from lesser elements, something that seems tantalizingly achievable but is it really? i'll give them that there is a ton of free energy hitting the earth every day, and part of the overall progress of humanity will be better harnessing that energy going forward, instead of burning through the finite, previously-transformed solar energy that is buried oil & gas.
with that said, i did some experimentation with these new color spaces recently and found that even these are not foolproof for those of us who don't want to be steeped in the depths of color spaces and human perception. for instance, mentioned in the article is automatic gamut mapping for when you try to display a color that's outside the gamut. seems like that's a good thing since it would take care of some rare edge cases, right?
no, the edge cases are all over the place. the gamut "depth" is dependent on the component values (like lightness and chroma), so if you want to go from a light red hue to a light yellow hue, you can't just change the hue component, because the lightness and chroma values might put the target color out of bounds. that's where the automatic gamut mapping kicks in. but guess what? the various browser engines currently have their own algorithms, and they that don't pick the same nearby colors.
the evil martians oklch color picker[0] shows this visually. if you look at the hue vs. lightness graph, notice how jagged the (planar projection of the) gamut is there. for any given horizontal line (constant lightness), you might end up out of bounds on the chroma component for a chosen hue. this can happen in any of the 3 dimensions.
also, while oklch is more perceptually even generally, there are gradient examples where it's not much better (i think orange/brown gradients is one of those cases, but i'm not certain, offhand). color is apparently quite hard, so i'm not knocking the effort or the improvements, but there are still some gotchas remaining for designers/developers.
bootstrap does this as well, and since tabler is built on bootstrap, it seems they're extending that precedent (there's a lot of "!important" going on to, which is not a good sign). i'll admit i'm not much of a bootstrap fan either.
i'm slowly developing my own personal css framework where i'm trying to have no tooling at all, including no scss, and very, very minimal js (and certainly no framework or packaging/transpiling of js at all) by default. it leans heavily on css variables and all the other current css goodies (good riddens IE!). that way, it can fit into any use case without having to worry about tooling conflicts. bulma kinda takes this approach (particularly, no js), but it's weirdly not as extensive as i'd expected it to be.
the underlying html and css, however, give me pause about how easy it would be to integrate into a larger project. <div> soup is how i'd describe the demo html, and its css uses custom properties (css variables) in a way that, on first glance, seems to make it more verbose without adding power, flexibility, or maintainability (or accessibility, but that seems a really big challenge for data-heavy frontends like this).
i'd probably try this out if i needed a dashboard on a project, but perhaps would want to test drive it on a small/test project to see where the gotchas are first.
the back would be ok, but one of the reasons i like the side button with fingerprint sensor (or in-screen) is that it can be face up on a surface and you can still actuate the sensor. it's not that big a difference, but it is slightly better UX.
i also like the fingerprint version over faceID because it's not 2 steps to open the phone most of the time, but still gives you the option to see the preview screen when desired (pressing the home button with the fingernail/fingertip).
my plan is, i'm gonna use this thing until it dies! =) but no, i'll probably upgrade next year, as the 6S no longer gets ios updates as of this year but i see no need to upgrade quite yet. i'm not sure if i'll get a 13 mini (assuming no more minis to come) or splurge and get a 15 (that i don't really need, but it'll be new and shiny and irresistable).
as noted in my other comment, i'd be ok with a full screen version of this phone if they put the home button on the side and keep the fingerprint scanner (in button or in screen) and leave off the front facing camera (pinhole camera is acceptable too, but not a notch). i'd prefer to keep the headphone jack, but that's probably asking too much of apple.
i still use my trusty 6S because i prefer the fingerprint scanner and home button, plus having a real headphone jack is useful every now and then.
but it doesn't work, see? so might as well stand for something, rather than nothing, if that strategy doesn't make you invulnerable anyway.
my basic argument was that douglass tried violence, found it didn't achieve his aims, and decided to use his intelligence and empathy instead, and achieved (some of) his aims by winning over those on the margin, not trying to necessarily win over the extremely prejudiced. this happened over a lifetime (some 80ish years), and who someone is is a totality of those years, not some arbitrary subset of them.
negative qualitative judgments like yours don't really add to the discussion, because the apparent objective is to tear down rather than build. why not try reasoning to a positive position instead?
those ideas are seeping in from social and religious debates, not legal and civic ones.
learning that infinite things could be finitely bounded was mind-blowing back in the day however.
getting caught up in a side means you can't pick and choose from the whole menu of ideas out in the world. it means that if you're against abortion, you must be for guns (or vice versa), lest you suffer cognitive dissonance and social anxiety. that's exactly how political parties, pundits, the media, and partisans of all stripes get twisted up into contradictory positions, but can never extricate themselves, because they'd have to acknowledge a modicum of reasonableness coming from "the other side". it's pretty silly to get so tied up in a tribal affiliation that you shut down your own thinking that way.
this is actually the topic of the linked paper (i.e., culturally motivated reasoning), which was hardly discussed at all in these comments.
through experience douglass realized violence doesn't work, something many of us have to learn for ourselves as we grow up. he ultimately realized that to achieve abolition, he needed to outreason the slavers, not outgun them, which is what he's principally known for--his reasoned positions on (anti-)slavery.