Yesterday, we launched a generative image model that competes with the top of the field. I figured some HN folks might be interested in this deep dive from the research team.
Watching them figure out how to make the best use of our relatively-limited resources has demonstrated "necessity is the mother of invention" for me. Instead of just "pour more money on it," they came up with a different training strategy / hypothesis (the title's Layout Bet), and it's exciting to see that bet start paying off.
> Reynolds was in for yet another unwelcome surprise: The developer sued her for being “unjustly enriched” by the construction of the home on her land.
> The developers’ lawyer told SFGATE in March that Reynolds appeared to be taking advantage of the developer’s mistake. “Keaau Development Partnership is the only entity that has suffered hundreds of thousands of dollars’ worth of losses,” Peter Olson said. “She’s trying to exploit the situation to get money from my client and the other parties.”
I'm glad the judge laughed that one right out:
> The court has dismissed that case.
> “The clear motivation of KDP and PJC was to cut corners to reduce construction costs,” the ruling read. “... The encroachment on Lot 114 is so great that the Court finds it has caused the complete destruction of Ms. Reynolds' estate as it had been originally held and enjoyed.”
I use macs at work and Linux at home. There's no uniform way to make a Linux machine accept things like cmd right arrow to jump to the end of the line, etc.
Given the weird take on x86 being inherently "more powerful" and the copy-pasted error from the marketing site (32W vs 32WH) this "article" looks like gently massaged advertising copy:
> Alternatively, HP’s EliteBoard will bring Windows and a more powerful x86 architecture to the keyboard-PC form factor. HP says the EliteBoard will support Windows 11 Pro for Business and an AMD Ryzen AI 300-series processor with an up to 50 TOPs NPU. The device will be sold with a 32 W internal battery and is part of Microsoft’s Copilot+ PC program.
My takeaway from the read wasn't that it was trying to convince anyone to take any particular action, and even emphasized that the mediocrity of AI output as more people use it will be a benefit to the smaller number of people doing their own thinking.
By default, Lit renders into shadow DOM. This carries benefits like encapsulation (including the style encapsulation you mention). If you prefer global styles, you can render into light DOM instead with that one-line switch.
However, shadow DOM is required for slotting (composing) components, so typically what I'd recommend for theming is leveraging the array option of each component's styles:
static styles = [themeStyles, componentStyles]
Then you define your shared styles in `themeStyles`, which is shared across all components you wish to have the same theme.
That sounds like possibly a configuration issue rather than strictly performance (although I agree the symptom is worse performance). For instance, specifically the value "~60fps" vs something as high as 400fps sounds like running with vsync enabled vs. with it disabled.
Hey, I worked on this & totally agree - I want my tools to be editors, not slot machines.
My focus has been on the beta "Edit" feature, tucked away into the top-right when you're looking at a single image. It lets you directly manipulate the image as both a spatial canvas and a semantic structure.
Watching them figure out how to make the best use of our relatively-limited resources has demonstrated "necessity is the mother of invention" for me. Instead of just "pour more money on it," they came up with a different training strategy / hypothesis (the title's Layout Bet), and it's exciting to see that bet start paying off.