clairity

but the ability to affect weight is mostly in the components, and the battery is the largest and heaviest of these. aluminum is pretty light but you need a certain amount of it to have the structural characteristics they're aiming for.

sure, it's light enough for me though (<4lbs). i like the tradeoff of more (heavy) battery vs. shooting for the absolute lightest machine.

i have a perfectly usable MBP right now, but this is the laptop that i've been waiting for. seems to hit the sweet spot on price while having a large screen but still "thin & light".

yes! i'm doing something similar on a personal project, trying to leverage the rails conventions as much as i can, and so far, it's been a real net gain in productivity from something like rails 5.2/6. i'm using the bleeding edge rails 7.1.alpha, which has a number of niceties like built-in password challenges, template locals, common table expressions in AR, and default dockerfiles (which i don't use), pluse better support for encrypted attributes and (postgres) enums. i'm also using some new-ish ruby features like endless methods, which is surprisingly useful for thinking about how to make methods more atomic and modular.

the CO₂ levels we see day-to-day (as long as you don't work in certain very specific industries) cannot have the effects that are fashionable to discuss. it's bullshit, an intentional disconcern for truth. bullshit by definition is distracting, as it literally takes attention away from truth-seeking and effective policy-making.

here's a USDA fact sheet summarizing the effects of CO₂ at different concentrations that's more easily digestible than an academic paper: https://www.fsis.usda.gov/sites/default/files/media_file/202...

if you look at the paper, you see no such conclusive evidence, but rather weak correlative assertions in noisy and complex environments. also notice the incentives and implicit bias of the involved. unbiased studies from the past several decades have so far shown cognitive effects require 10× that level of CO₂ to show any conclusive effects. even the pm2.5 effects attempt to make a short-term correlation, which is dubious at best. long-term pm2.5 effects are more conclusive, which is why we should be more concerned about them.

CO₂ is a fashionable concern but not scientifically supported. more importantly, it distracts from things we really should be concerned about as states and nations, like actual pollution and the alarming concentration of power and wealth.

> "although the effects of CO2 in cognition and energy levels are debatable"

it's really not debatable. the feeling of stuffiness is a function of many things, but environmentally, it's mostly temperature and humidity (we humans are hot and breathe out lots of humidity). there are no cognitive/energy effects until you get into the 10's of thousand of ppm, as the mechanism of action is competing out oxygen, not some intrinsic maladaption to CO₂, which is actually vital to life on earth. it's fashionable to hate on carbon right now (it's mediopolitical), and that's really all there is to it.

particulates, VOCs and chemical off-gassing, on the other hand, do have known mechanisms of harm, and that's something you should be more concerned about, but not yet alarmed. most of that pollution comes from cars and coal/gas power generation, so long-term, we should move toward more efficient habitation (e.g., denser cities, public transit) and cleaner power generation (including nuclear) if we really care about our collective health.

practically no one should be worried about CO₂ in their daily lives. it's thoroughly a red herring.

rails has the concept of app templates, so you can create this for yourself. here's one step-by-step example: https://citizen428.net/blog/rails-quick-tips-5-create-apps-f...

there are also repositories, like https://railsbytes.com/, where you can peruse similarly pre-composed app templates of varying quality.

nice! that's something i stumbled over when re-architecting a 2-sided marketplace (in rails) for one of my startups. the data model they describe is roughly what i ended up with, but it took some iterating to get there. the key understanding was that the relation table in a many-to-many relationship is not just a technical detail but encodes important information about real world systems, especially the human kind. as engineers, we get often get stuck on the entities being the important bits, but more often, the relations are where all the action is.

this one really annoys me because proton mail uses the "spoofed" utc timezone to show when i sent/received emails, as if i live in the uk or west africa. they also refuse to add timezone as an app setting to correct this issue.

it's a mistake to believe that any major political party adheres to a principled political philosophy, but it's true that single-party politics is ripe for corruption, which is CA (especially SF and LA) in a nutshell. it's much easier for money to talk when only one party is listening. this is the same dynamic that antitrust in commerce is meant to prevent. politicians spend something like 80% of their time now soliciting donations, even in single-party areas, which is very telling of their priorities (rhetoric be damned).

neat stuff!

you have a typo on that page under https://htmx.org/essays/view-transitions/#the-css : @keframes instead of @keyframes

"most ... in the US" is probably going overboard, but that's not too far from the truth in LA, where, for instance, many of the restaurants in little tokyo are korean-owned, despite the namesake. there can be good korean sushi, but it mostly tends toward the cheaper end, which means it's often not as good as a japanese sushi bar, where the best sushi is exquisitely delicious (and quite expensive). it seems like japanese sushi chefs aren't interested in the lower end of the market, so cede it to others willingly, and touristy areas like little tokyo have plenty of unsuspecting customers to keep those businesses afloat.

LA has the best korean food in the US, particularly because it has the best banchan (like kimchi!). even so, i generally wouldn't go to a korean sushi restaurant for good sushi in LA.

adults really shouldn't pregurgitate spurious reasoning like this for children, no matter how well-meaning. instead, we should tell them the direct truth, perhaps only eliding nuance and detail for the appropriate maturity.

swear words are exclamatories, meant to indicate extreme emotion. so using a lot of swear words is like shouting all the time, or using all caps all the time in writing. it washes away the richness of expression and makes the swearer seem unable to properly contextualize and express their emotions. our brains are attuned to wash out sameness and pick out differences, especially sharp ones. that's also why selective swearing is very effective, and constant swearing is ineffective.

there's certainly much more to it than just that, but that should be the core contextualization of swearing for kids. let them experiment on their own but just like shouting all the time, let them know it won't be tolerated in most situations until they can effectively and appropriately wield this grammatical tool. don't impose some indirect, off-the-cuff age cut-off, which they'll surely understand as being arbitrary and therefore easily (and rightfully) dismissed.

it's even on coffee bags: https://barrio.la/trystero-coffee/ a conspiracy, i tell you!

i've read both gravity's rainbow and atlas shrugged, and found both to be worth reading, but gravity's rainbow was immensely denser and commensurately more intriguing, if also frustrating. atlas shrugged is as straightforward as to kill a mockingbird or the handmaid's tale in its plot and messaging, and worth the read in for similarly straightforward reasons. gravity's rainbow seems like it was strained through the multiverse of everything, everywhere, all at once and spit out linearly fractalized. it's challenging to say the least.

tolkien, on the other hand, i found so boring as to never have been able to finish even a fraction of any of his books.

yah, this is like the todo app of content management, being able to change the text (and perhaps add bold and some links), and has probably been built thousands of times by now in the short history of the web. building in-place editing for fixed text nodes isn't that hard, whatever the underlying toolkit. a CMS should be able to do that in its sleep. it's when you get beyond text into other media and into layout, spacing, color systems, and dragging-and-dropping arbitrarily interleaved blocks of those things where it actually gets useful (and impressive).

that's the only telemetry it sends (afaict) and that's pretty easy to block with lulu itself (which is what i do).

i wish you were hiring a product manager, as i'd love to help you fix the horrid UX on the departure details screen i just posted about. it's been there for years, and i can't imagine that anyone who actually uses the app would have let it go that long without fixing it.

i use transit in LA (where it's the default app for metro) and it has a huge glaring UX failure in that the departure times list at the bottom of the line details screen takes up at least a 1/3 of the screen, and when you want to see more of the map and try to push the list down, it closes the details screen. it's so frustrating, because i end up doing this 2-3 times per use, needlessly tapping back and forth. there's already a close button available so scroll to bottom to dismiss is wholly unnecessary. the departure times list wastes a ton of precious screen real estate as well - it could simply be a comma-delimited list on one line that could scroll sideways, and thus obviating the need for 1/3 of the screen for mostly whitespace.

i do like that the departure times are (slightly) more accurate because of the crowd-sourcing. however, the underlying data from metro is a mess, so they end up looking bad anyway because trains and buses still show up (or don't) unexpectedly due to metro's unreliable data.

it was used in the NBA dunk contest this past weekend. it works, it's neat, and it never goes flat.

why doesn't rails have a local-first equivalent? it's something i'd love to see, as many apps can benefit.

back in the day, we built a real-time sports stats app on top of rails and firebase (before it was gobbled up by google) that provided some affordances in that regard, but truly offline first--saving locally, then syncing when online--would be a great rails use case.

it'll (slightly) scare folks who don't think too deeply about it or don't have lots of legal knowledge/experience, but not the folks most likely to use them for illicit tracking. all it does is alert them to do their tracking more surreptitiously and perhaps to cook up an alibi beforehand.

yes, mixins. even just static sets of declarations would be a great start, e.g., wanting to apply the same set of base rules to both an entity and various classes without error-prone repetition (which you typically separate to have control over cascading and specificity).

css variables in media queries would be helpful too, but mixins to me is the next big step after :has() (oh so useful, come on firefox!) and this nested css syntax. unfortunately, it may be years for us to see it in browsers. there's no consensus yet on mixin syntax or where in the css lifecycle it would be implemented (there are potentially serious performance implications apparently).

to take that further, whenever you see a dichotomy like this, it should be a signal to turn your brain on, not to conform to a side, which is turning your brain off. it's crucial for democracy that we do so.

the best response to a dichotomy is rarely centrism (taking the middle position). that's just implicitly accepting the framework of the dichotomy. critical thinking requires moving laterally among multiple dimensions to uncover the crux of the dichotomy itself (the power interests that form the dichotomy) and to reason yourself into a better framing.

with respect to DEI, the term DEI itself is now political, so that slides us right into the false dichotomy. if we want to talk reasonably about the issue, we should probably leave that term aside.

nope, that's exactly right. at 5-10% you feel real effects, not at 1200ppm or 3000 or any other psychosomatic level.

"poisoning" is a needlessly loaded word in this context. CO₂ is literally critical for life. just about any molecule/compound at those concentration levels (outside of those we co-evolved with, like nitrogen) will have noticeable effects as well.

right, CO₂ has become a (inter-)national psychosomatic obsession of the privileged class, but no one should be worrying about CO₂ at all, unless you work in some very specific industries. you'd need a ppm of 50,000-100,000 to feel any real effect from CO₂, or to see noticeable greenhouse effects from it. it's today's equivalent of fearing power lines or MMR vaccines. it's fretting on something that feels tangible and controllable, without delving deeper and examining the (social and mass) media-driven presumptions underlying those fears.

pollution, on the other hand, is a real concern. that's stuff like radon, VOCs, methane, dioxins, and SOₓ emissions. as such, one thing we should be doing with vigor and relentless focus is phasing out coal plants (if we were actually putting our priorities in the right place) rather than worrying about the sideshow that is carbon emissions.

blind folks aren't dumb. they can analogize what 'show' and 'hide' mean in context (not to say that this shouldn't be made better).

in any case, i agree that there's a lot going on to add affordances for keyboard users that screenreader users don't need. screenreaders would just need the <nav> element (probably should be aria-labeled too) and the <ul> link list.

it's neat but a little convoluted. i'd also vote for using a <button> rather than a checkbox plus anchors, but buttons do have technical limitations (as noted elsewhere) that browser engines should fix (similar to how dialog elements are now nearly javascript-less, only requiring a `showModal()` call to open), rather than having to have authors work around them.

the tunnels i went through in japan were all at least 2 lanes in each direction. there were plenty of cars and traffic in the cities i visited so it can't be that inconvenient.

it would be roughly $600B to build enough neighborhood parking garages in LA to serve all its residents. that's just half a year's worth of GDP, which is not nothing, but certainly within reach. with just that, LA could remove all on-street parking in neighborhoods and turn it into bike lanes and/or extend the curbs to add more trees and sidewalk.