My problem with it was that it looked truly disgusting and I don’t say that lightly. They had essentially cloned the Reddit “new” theme that has the all too common obnoxious overuse of white space over content.
I don't care about the visuals of Reddit, but copying the design of "this is a site for commenting, answers are just top-level comments with no distinction" seemed like they did not see the difference between Stack Overflow and a subreddit.
> In 1832, President Andrew Jackson had replaced soldiers’ daily spirit rations with coffee beans and sugar. This created a heavy logistical burden for the army, with a 20-day supply for 100,000 troops weighing 250 tons, all needing transport by horse-drawn wagon. Roasting, grinding, and brewing coffee in the field was also time-consuming for soldiers.
respect to the third wave coffee connossieurs of the 19th century
Awesome. People take concrete for granted. Even at small scales (e.g. your patio) with formulas provided on the cement bag, concrete can go wrong (crazing, scaling, cracks). There's a lot of unappreciated craft in the work, not only in the composition and mixing, which is what this research seems dedicated to, but also in the placing, leveling, curing, finishing.
Civil Engineering is hard, and concrete is a perfect example of how something as "simple" as concrete in reality requires significant interdisciplinary collaboration with domain experts in ChemE, MatSE, Physics, Applied Math, and CS.
Some of the most robust HPC applications I saw back when I was an undergrad were done by Civil and Structural Engineers in the ONG space.
That’s funny because I don’t see civil engineers being “glazed” much online. Usually they’re the butt of jokes and ridicule from other engineering majors who perceive civil engineering as less ‘rigorous’ than other disciplines. I’m curious where you see this civil engineering “glazing”?
They're usually held up to as the pinnacle of "real engineers" in discussions where software people are trying to portray software as insufficiently rigorous.
Yeah the other varieties of "real engineer" think of them about the same way that NPs think of MDs.
> Copilot is for entertainment purposes only. It can make mistakes, and it may not work as intended. Don’t rely on Copilot for important advice. Use Copilot at your own risk.
> We don’t own Your Content, but we may use Your Content to operate Copilot and improve it. By using Copilot, you grant us permission to use Your Content, which means we can copy, distribute, transmit, publicly display, publicly perform, edit, translate, and reformat it, and we can give those same rights to others who work on our behalf.
This is as good as when the engineer from the Claude team said they load their website in such a way as to protect against hostile actions such as scraping.
Nice to see Firefox experimenting with browser features, even small stuff. I don’t think this solves the user problem they mention though.
> This work is inspired by user research that we conducted last year, which explored how people resume tasks after interruptions. One key insight we learned is that when we are interrupted, even a small reminder or message can significantly improve our ability to resume a task
Interruptions are unplanned for. Don’t think I’d be preemptively leaving notes on my tabs to defend against interrupts. Especially since tabs are an ephemeral interface. Much more likely that useful notes go into an actual knowledge base (i.e. the other note tools mentioned).
For a browser tab, I’d prefer to have automated lineage/metadata (e.g. I opened this at X time, branching off Y page, etc) that I can use to deduce where I’d left off.
I’d rather have a local web archive of my tabs in my browser so that i can see what the website was like when I last saw it.
Add to that a background vector db with a RAG for each website visited and I can then search for all my past history of webpages later on, all offline!
Or maybe a right-click and "save webpage as markdown" powered by a mini locally running fine tuned model or something.
> I’d rather have a local web archive of my tabs in my browser so that I can see what the website was like when I last saw it
I'd start by having an option for a significantly longer browsing history. Just having an usable history search would help. With the history limitations browsers have right now it's exactly short enough to be practically useless.
Other than that, a local private RAG with my own history would indeed be nice.
I actually do (did) use kill to quit Firefox, because that keeps the most amount of state. It does no longer seem necessary, I'm not sure, but I still do it out of habit.
It's essentially mystery shopping. There's a pretty big disconnect between what a large corporate HQ thinks occurs at their stores and what actually occurs at their stores.
Mystery shoppers were often paid in cheaper groceries, one time payments, etc (at least in the early 2000s). Mystery shoppers wasn’t a full time hourly job.
Don’t think this article should frame consolidation as a failure of the individual bets.
The reality is likely that shipping these separately was (1) faster given org structure at the time and (2) made sense in the environment (e.g. if Perplexity launches a browser and that turns out to be what users want, we should have one too). Better to iterate and move on then try crystal balling perfect projects.
reply