ulrischa

Just use php. SSR since 1999

I get sick when I think about migrating my htaccess and apache rules to this format

A really impressive feature list but a pretty heavy system level dependencies. On windows chocolatey is needed for them.

Almost anything ist noch longer true. PHP has a very strong backward compatibility. Migrating from one mayor release to another mostly is possible without touching your code. But you can also start new and work with very modern language features

PHP has namespaces: https://www.php.net/manual/en/language.namespaces.php But what is the difference writing abc\classname or abc_classname? Long classnames ist not a big problem

Somehow spooky for what github actions are used. On the one side it is cool to have hosted task runners with multiple options thanks to using vms in github actions, on the other side is the question: is this what github actions ate ment for?

My Pebble was not very good. The display glitched all the time, the connector to load the watch was fidgety and the display too dark. I hope the mechanical construction will be better for the new ones

The old automation in YAML is very cluncky as the author also mentioned. The new UI guided creation is not powerful and can become confusing for complex cases on the other side. I do all my automation with the node-red Integration. But the combination of the node-red flows with the Homeassistant dashboards is not very good. Do you plan to change the automation to something like node-red but better integrated? Or change the yaml to sonething less declarative and more code centric?

You can use any cheap webhosting

I read it and was happy. But then I dived deeper and it is the same as all the other frameworks. Why is this not using Webcomponents mixed with markdown? Why not JS template literals? Why do I need bun? And not to mention the strange naming convention: htm for Client html for Server- wtf?

What I want is Astro with just web standards like Webcomponents

A phd ist not a phd. A phd in medicine is like a Bachelor thesis. While a phd in engineering can become a 10 year nightmare

I’m a solo founder myself, and here’s what’s worked for me so far:

Start with the Basics: I spent some time wrapping my head around the fundamentals. Books like "Influence" by Cialdini, "Crossing the Chasm" by Geoffrey Moore, and "The 22 Immutable Laws of Marketing" by Ries & Trout helped me get a grip on core concepts like positioning, target audiences, and the psychology behind persuasion.

Focus on One Channel and Iterate: I learned the hard way that it’s tempting to try every platform, but that’s overwhelming—especially when you’re solo. So I picked one channel that made sense for my audience (initially, email outreach and LinkedIn). I ran small experiments with subject lines, tone, calls-to-action, and watched what worked.

Engage in Conversations, Not Sales Pitches: A big part of sales, I realized, is listening. I started hanging out in niche forums and Slack/Discord channels where my potential users might be, answering questions, and offering help. When people realize you’re there to support them, not just push a product, it builds trust.

Use Low-Cost Tools and Communities: Hacker News, indie hacker communities, and entrepreneur subreddits are goldmines for getting feedback on landing pages, pitch decks, or just your general marketing approach. I regularly post progress updates or ask for opinions—sometimes the feedback can sting, but it’s invaluable.

Document Everything: Whenever I tried a new marketing tactic—be it a cold outreach email or a small Twitter ad campaign—I noted my assumptions, what I did, and the results. Over time, I built up a playbook of what actually moves the needle for my audience.

Build Real Relationships: Early on, I put a lot of effort into meaningful relationships—both with early customers and other solo founders. A quick Zoom call or a coffee chat can lead to referrals, partnerships, or just great insight. Honestly, it’s usually more about genuine curiosity and a willingness to help than any formal pitch.

Adopt a Continuous Learning Mindset: Marketing and sales tactics change quickly—algorithms, consumer behavior, best practices, all of it. I keep reading, trying, and asking questions. And I keep telling myself that every “No” is actually a “Not yet”—it’s just data to improve my approach.

That’s how I’ve been tackling marketing and sales as a solo entrepreneur. Keep things simple, learn by doing, and stay genuinely curious about your customers. It’s an ongoing process, but one that becomes more intuitive with each experiment. Good luck!

See this to get clean Markdown for a webpage: https://devkram.de/markydown/index.php

Does not work on a smartphone

See Google Today: https://www.google.com/search?q=dinner+for+one

I have build a grafana weather dashboard with the data from an enviro+ some years ago. It monitors a lot of weather data from my home. You can see it here in German: https://umwelt-olching.de

In Germany: Nowhere because the Deutsche Bahn is late again: https://www.dw.com/en/germany-a-third-of-long-distance-train... https://www.theguardian.com/business/2023/oct/14/its-the-sam...

Good solution. But for what the Program.fs? The conversion from md to html could be done within the action with more common languages and state of the art libraries for this job.

I made spectral image analysis at university. And there weren't good software Tools available

Why does everybody thinks first this has something to do with your nationality? This is the Stammtisch. I'm from Germany and when I come with my little son to a restaurant we also can not sit there. Same right for all

I like these tools that are in one local html file. But this seems a bit unsupported. Last commit ist one year old. When you need some more but no jira then kanboard.org is what I can recommend

Have not used it in the past. Are the limitations for the free plan enough for a hobby coder?

I wonder how a powerpoint can be converted to markdown

It will not be available in the EU for now. I always feel disadvantaged when I read that sentence

The implementation on Chrome for Android is really ugly

I would take the new "Plasma 2350 w" from Pimoroni https://shop.pimoroni.com/products/plasma-2350-w and connect some APA102/Dotstar or WS2812/Neopixel either from BTF Lightning, Amazon or Pimoroni

I think the main problem with writing large programs as bash scripts is that shell scripting languages were never really designed for complexity. They excel at orchestrating small commands and gluing together existing tools in a quick, exploratory way. But when you start pushing beyond a few hundred lines of Bash, you run into a series of limitations that make long-term maintenance and scalability a headache.

First, there’s the issue of readability. Bash's syntax can become downright cryptic as it grows. Variable scoping rules are subtle, error handling is primitive, and string handling quickly becomes messy. These factors translate into code that’s harder to maintain and reason about. As a result, future maintainers are likely to waste time deciphering what’s going on, and they’ll also have a harder time confidently making changes.

Next, there’s the lack of robust tooling. With more mature languages, you get static analysis tools, linters, and debuggers that help you spot common mistakes early on. For bash, most of these are either missing or extremely limited. Without these guardrails, large bash programs are more prone to silent errors, regressions, and subtle bugs.

Then there’s testing. While you can test bash scripts, the process is often more cumbersome. Complex logic or data structures make it even trickier. Plus, handling edge cases—like whitespace in filenames or unexpected environment conditions—means you end up writing a ton of defensive code that’s painful to verify thoroughly.

Finally, the ecosystem just isn’t built for large-scale Bash development. You lose out on modularity, package management, standardized dependency handling, and all the other modern development patterns that languages like Python or Go provide. Over time, these deficits accumulate and slow you down.

I think using Bash for one-off tasks or simple automation is fine — it's what it’s good at. But when you start thinking of building something substantial, you’re usually better off reaching for a language designed for building and maintaining complex applications. It saves time in the long run, even if the initial learning curve or setup might be slightly higher.

Seems like I can not edit it. Sorry

That's what I mean

I’ve seen a lot of people do this when resurrecting old niche sites. The high-level approach usually involves grabbing all the snapshots from archive.org, stripping out their timestamped URLs, and consolidating everything into a local mirror. In practice, you want to:

1. Collect a list of archived URLs (via archive.org’s CDX endpoints). 2. Download each page and all related assets. 3. Rewrite all links that currently point to `web.archive.org` so they point to your domain or your local file paths.

The tricky part is the Wayback Machine’s directory structure—every file is wrapped in these time-stamped URLs. You’ll need to remove those prefixes, leaving just the original directory layout. There’s no perfect, purely automated solution, because sometimes assets are missing or broken. Be prepared for some manual cleanup.

Beyond that, the process is basically: gather everything, clean up links, restore the original hierarchy, and then host it on your server. Tools exist that partially automate this (for example, some people have written scripts to do the CDX fetching and rewriting), but if you’re comfortable with web scraping logic, you can handle it with a few careful passes. In the end, you’ll have a mostly faithful static snapshot of the old site running under your revived domain.