My team upgraded our frontend monorepo from npm+lerna to Yarn 2 with PnP. We saw vastly improved installation time, most importantly on incremental installations. The startup times for jest, webpack, and TypeScript also improved. PnP's dependency strictness eliminated cases where updating a package in one workspace would break a different workspace.
It was a fairly difficult migration, in particular because Yarn 2 PnP does not allow you to import a module that is not specified in package.json. Lots of libraries play fast and loose with dependencies, and so our .yarnrc.yml file which adds those missing dependencies is now 172 lines. PnP requires configuration for vscode and a custom build of TypeScript, which isn't ideal, but those have worked well.
Barry Richard, an election lawyer who served as a lead attorney for President George W. Bush during the 2000 recount in Florida, criticized the campaign’s efforts. “I wouldn’t call it a strategy,” he said. “There isn’t any legal basis for anything I’ve seen so far.”
Other election law experts have questioned the multipronged attack. Richard Hasen, professor at UC Irvine School of Law and author of “Election Meltdown,” said the lawsuits, even if partially successful, were smaller-scale and didn’t threaten the results. “If they’re not being filed to change the election outcome, what’s the point?” he said.
There is also the font selection and the borderless terminal which improve the aesthetics
Without that it could look like this https://i.imgur.com/TVwkQI0.png
But I agree, the author did really good job in creating a clean an visually pleasing UI only using text and standard symbols
I always find myself wanting just a little more terminal text style control. Usually I’m left wishing I had either an alternative font mode or double sized text. (Double specifically to avoid breaking the X*Y text cell grid)
But little wishes for extra expressiveness aside, i really don’t think terminal UIs would benefit from anything like CSS. The terminal functions as my working environment. I rely on being able to visually pattern scan for errors, warnings, typical command output, time stamp and log alignment etc. I do not want anything messing with how I set all this up.
I've avoided looking too deeply into cursive in the past because I naively assumed it would be difficult to make it look like like anything other than a late-90s BIOS, but this is exciting.
This looks like a "draw the rest of the fucking owl" thing. Yes, it's not a lot of manual work, but I wouldn't be able to do it at all because I don't have a sense for design.
Citymapper is excellent, especially for short trips that can be done in many different ways. Sometimes, for longer trips, Citymapper shows “Uber” or “long walk” as part of a route. In those cases, I would generally prefer to bike, without a bike share. Is there a multimodal transit app that includes transit + cycling?
Neat! When working with Options/Results/Iterators, you can use `.map` [1] for exactly this purpose. It would sometimes be convenient to have something like `.map` / `.let` on unwrapped values as well.
While there might be a better syntax if you only care about this one feature, async/await needs to fit into an existing language, and this syntax makes sense with the rest of Rust.
This syntax makes it clear that’s it’s not a function or macro invocation, works the same way as ‘?’, and allows for clear and concise chaining.
It was a fairly difficult migration, in particular because Yarn 2 PnP does not allow you to import a module that is not specified in package.json. Lots of libraries play fast and loose with dependencies, and so our .yarnrc.yml file which adds those missing dependencies is now 172 lines. PnP requires configuration for vscode and a custom build of TypeScript, which isn't ideal, but those have worked well.