Something about this design make it seem more like a chat interface to the terminal, and after using ChatGPT the idea of chatting to a raw computer terminal instead of one way commands seems so obvious... the future interface for everything looks more and more like it's just going to be chat based, or like a Jupyter notebook, and that seems amazing to me... because it's getting us ready for voice-based computing like Star Trek.
I wish one day I can just turn on my computer and it does nothing but chat, no distracting apps or web browsers, just a minimalist chat interface.
It sure if you’re remembering most of Star Trek very well, the crew evidently, and demonstrably does more work on their consoles, which have actual UI’s.
Can you imagine trying to navigate to a sub directory and run a binary but your LLM-assistant has decided that it thinks you want to search for the file name on the web? And you can’t just do it yourself, because they’ve taken away the actual tools from you.
I think I’d actually go and become a goat-farmer at that point.
I found the prompt at the bottom irritating, and I still find it irritating for ChatGPT. But chat apps are probably the apps that normal people spend most of their time in, so for them it's intuitive.
It's like the devs never tried building anything real with their own framework. Internationalisation support was dropped in the app router and the docs just tell you to DIY... but just to make the app support RTL languages you need to do some hacky things to update the <html dir="rtl"> in the root layout.
I find Tailwind really good for prototyping designs and iterating quickly, and as the design becomes more crystallised then I moved to semantic css and start to clean up the complexity. Once I've figure out that patterns and components required...
I’ve found myself wanting a Tailwind compiler that makes it easier to work like this. Iterate fast with maximum verbosity, but later extract common patterns to classes when things are more stable. Anyone aware of any tooling like this?
That would be nice, like a Webstorm / editor feature that detects when you re-use code and recommends abstracting it. I would love that to be able to detect that like "Hey these buttons all share these features, let's refactor it for you"
Go for it! At the very least there are some interesting algorithmic problems in there. I was leaning towards calling it "Leaf Blower", because it's a form of wind that tidies things up. Take it or leave it. :P
I figure most startups would build an MVP in two weeks and then rebuilt it later or move onto the next version and clean it up a bit in each version that follows.
Never change a running system. If you create a working project, you will not change it, especially a startup.
Possible on a later bigger update (if necessary), a complete app would be rebuild. But here is the same problem: why should you do it, if your project works?
I personally had not seen such an update in early stage of a startup. Did somebody have insights or examples?
To me you are adding complexity. Back to finding which styles are cascading over another.
Tailwind is somewhat like lisp in the aspect that people usually don't get what all the hoopla is about. All they see is parenthesis and want a "lisp" without the parenthesis once they figure out polish notation
Yeah, cause I end up with like 5 different buttons designs using Tailwind, and they all have different classes but when I clean up the code later I reduce it down to one button design that fits the final theme.
I had tinnitus for a while, and tried a few things that didn't work but this thomping technique I found on reddit one day stops it, and I just do it every couple of days and it disappears for a while. Not permanent but whenever it bothers me now I just do this thumping and it disappears in a few seconds:
Weird. I tried it and didn't get much effect, but it's interesting to see so many positive comments on it. I'll try it some more over the next couple days.
I think that's because tinnitus comes in very different forms and intensity, and since it can't be objectively measured, it's difficult to compare between individuals. My guess ist that you can only silence very low intensity tinnitus with this technique.
Try a constant pressure massage instead of the thumping. Pressure should be high enough that the sensation is intense but not painful. The goal is to get muscles around the base of your skull to relax. I was amazed at how quickly it had an effect
Statamic is great for simple sites but for larger or multilingual sites it has lots of problems. I have a 5000+ page website that the static site generator takes 3 hours to build and there's been no improvement since v3 launched. You can use their "Static Caching" as an alternative to static generating but for my project requirements I need a purely static site. I'm busy doing a huge rewrite and switching to using Statamic in headless mode with NextJS in the front... which takes just a couple of minutes to generate the static sites instead.
I'm also still waiting for RTL support for languages in the CMS and multi-site permissions which has probably been on the roadmap for over a year but keeps getting delayed. I've submitted many ideas and bug reports on how to improve the multilingual experience but I don't think it's a priority for the team.
A very big German newspaper (https://www.spiegel.de/) runs on Statamic and they probably have an order of magnitude more pages. But not sure what kind of improvements/custom implementations they've done.
> Curious about how SPIEGEL’s stack works? Here’s their high level approach, keeping in mind this is running on v2. Upgrading to v3 streamlines even more of their stack.
> A huge flat file content store organized with each entry inside its own subdirectory (you can’t have more than 10k files inside a single directory, an operating system limitation)
> The content store is using a cloud storage solution.
> Statamic’s control panel pushes entries into the content store, and then into an ElasticSearch instance via message queue.
> ElasticSearch runs as a content API with blazing fast response times and is consumed by the control panel and front-end
> The front-end is built in Go.
> User accounts are connected with an Office 365 Active Directory integration with OAuth.
Serious: you should run a profiler on the generation step (or like... for a minute of it and the CTRL-C out). Often times degenerate cases like this exist but are more or less invisible to maintainers, and just saying "the generator takes forever" is not nearly as actionable as "here's the first 60 seconds of the generation process, does anything look weird?"
I've incidently just completed a headless statamic project that used Astro for the frontend. I'd recommend you check out Astro if you haven't already as dev experiece was great and generally feels a better fit for this usecase over next.
Gene Roddenberry was attending channeling circles from extraterrestrials, called The Nine and asking questions about different alien races and landings, even mentioning other channeling sources. (He appears in a book called The Only Planet of Choice.) I'm sure that type of thinking inspired some of his vision for Star Trek, and there are many other groups of channellers that communicate with Extraterrestrials... which seems like a much more elegant and realistic version than sending computers or AI to visit other planets.
Hard to tell if you're joking or not, but if you aren't and weren't already aware, there's an accessibility option in Preferences -> Accessibility -> Display to reduce motion in animations. Might be helpful!
Many people talk to extraterrestrial intelligences openly all the time, we are only limited by our technological way of thinking. Spiritual channellers, psychonaughts, shamans, psychics, in dreams... if the universe is conscious then telepathic communication is the ideal method of interstellar communication.
I wish one day I can just turn on my computer and it does nothing but chat, no distracting apps or web browsers, just a minimalist chat interface.