This seems obviously wrong? Any system whose name includes the word "forecast" was built to predict the future in some domain / over some time horizon / to some level of granularity.
nope, this is Mira Murati's thinking machines. she used to be the CTO of OpenAI, but started her own thing once she [I think] realized that she was missing out on the gold rush by staying there.
I also tend to put a Makefile into the root of any repo I work in (ignored via .git/info/exclude), so that shell commands relevant to my workflow can accumulate under that Makefile. I've been doing this for at least 10 years and love it. Most repos have some sort of a cli interface, but that doesn't mean that they're any good. Make is nice way to wrap all of them, and to standardize on at least the build/test/run commands across many disparate repos.
I just want to hack together something that works for my use case. If I can share that with the wider team, that is superb. But I really don't enjoy my hacky utils being subject to tedious code review scrutiny they don't deserve.
To be clear, I _do_ add utils that I think will be useful to the common repo, subject to review, and mostly they will be merged. But if it gets painful, I just retract the PR and keep it locally.
Have you ever tried to submit a PR of your Makefile to the maintainers of, say, an open source npm package? If you have, what compelling story were you able to tell about that Makefile that got the maintainers to merge your PR? And after they successfully merged it, did you continue putting up PR after PR for each successive round of tweaks to that Makefile?
What an extraordinary amount of unnecessary effort that would be. My workflow does not belong to the repo, it belongs to me. The only thing that belongs in the repo is all the shared workflows (or the elements they comprise.)
Arc's fluid transition between tabs, bookmarks, and favorites was excellent UX. It finally helped me tame 100s of open tabs by helping me treat "apps" as distinct from "pages".
Every new browser should be doing something to recognize the fact that browsers are an application platform, and they should be absorbing more desktop OS features in the direction of native-feeling applications.
One of the things I want from a browser is to fade to the background and to expose those applications as natively as possible at the OS level (e.g. I want to be able to put browser-based applications into my dock without having to download special electron wrappers for them.)
> One of the things I want from a browser is to fade to the background and to expose those applications as natively as possible at the OS level (e.g. I want to be able to put browser-based applications into my dock without having to download special electron wrappers for them.)
This would be awesome, thank you for sharing your feature request!
I loved the older version of Android which used to expose very single chrome tab as an app, that was a great UX as well.
Some churn is fads, but some is legitimate (e.g. "we know how to do this better now".) Every living system is bound to churn, and that's a good thing, because it means we're learning how to do things better. I'm happy to have rust and typescript, for instance, even though they represent some amount of churn for c and javascript.
The spirit of this post is great. There are real lessons here that the industry will struggle to absorb until we reach the next stage of the AI hype cycle (the trough of disillusionment.)
However, I could not help but get caught up on this totally bonkers statement, which detracted from the point of the article:
> Also, innovation and problem solving? Basically the same thing. If you get good at problem solving, propagating learning, and integrating that learning into the collective knowledge of the group, then the infamous Innovator’s Dilemma disappears.
This is a fundamental misunderstanding of what the innovator's dilemma is about. It's not about the ability to be creative and solve problems, it is about organizational incentives. Over time, an incumbent player can become increasingly disincentivized from undercutting mature revenue streams. They struggle to diversify away from large, established, possibly dying markets in favor of smaller, unproven ones. This happens due to a defensive posture.
To quote Upton Sinclair, "it is difficult to get a man to understand something when his salary depends upon his not understanding it." There are lots of examples of this in the wild. One famous one that comes to mind is AT&T Bell Labs' invention of magnetic recording & answering machines that AT&T shelved for decades because they worried that if people had answering machines, they wouldn't need to call each other quite so often. That is, they successfully invented lots of things, but the parent organization sat on those inventions as long as humanly possible.
i tend to draft everything lowercase, and then go back and uppercase things depending on how much of a formal vibe i'm going for. capitalization rarely helps me formulate an idea, and so my writing often splits into phases: (1) formulation, (2) polish.
also, it's worth noting that proper capitalization does not automatically yield text worth reading. from that perspective, i like lower case text as a form of rebellion against the artifice of rules; any rebellion against particular aesthetics is fair game in my book. more generally, i'm skeptical of process advocacy in cases where the process seems to be done for its own sake.
on the flip side, good grammar helps me parse sentences, so i do sympathize with arguments in its favor.
I find all lowercase messes with my parser, and is fustrating to read. I think I may treat sentences as a single unit, and use the capitilization to detect the boundaries. Without it I find bouncing to/from sentences slower (which can happen if a latter sentence/paragraph adds more context, and I want to revisit the previous idea).
Interestingly your semi-colons stand out much stronger than the periods for me.
I'd love a version of this where I can paste my full list of extensions, instead of a box where I can only paste one. The latter is tedious, so I'm not that likely to do it.
I think this is best seen as an art project, not as a business idea. I'm also assuming that the cost to run such an app are near zero, so the break-even cost would probably be, like, one person a month generating one new thing.
Confusingly, the about page suggests that this is an AI-driven storytelling app: https://www.thiings.co/about. Maybe that's a vestige of prior iteration of the app, though.
The concept minds me of the million dollar homepage, where you could pay a dollar per pixel of advertisement. Here, you're paying a dollar (that's a guess; i didn't check) to get a new object listed in the potentially infinite grid, which gives you a unique URL for that object, an emoji-like reference image, and a one-paragraph description for aliens, were they to land on earth and ask what that object was for.
Basically, looks like an art project that monetizes participation.
reply