Second, the "Digital Markets Act" has no "you must sell products directly to consumers" requirement. https://en.wikipedia.org/wiki/Digital_Markets_Act - look at the list of "Core Platforms Services" it covers. Search engines, communications, ad networks - Twitter's absolutely in several of those categories. It's about regulating gatekeepers to the market.
Traveling west, reaching land, leaving enough evidence to confirm the story five centuries later, making it back, and finally, convincing other people that it happened? No.
It really reminds me of Roam Research, which was also an overpriced, niche product that was unavoidable for quite some time in these circles. Now if you google it (or kagi it?) you just see a bunch of reddit posts asking if Roam is dead.
You'd think Kagi has millions of paying users, and not ~33k, seemingly half of which are on HN.
Hopefully this time around they don't actually start referring to their community as a cult like Roam did.
Flawless, it's really easy to wrap your head around (especially if you grok Go).
I would recommend spinning up the most basic site from scratch to give it a try, takes minutes tops and its got a built in dev server to see your site.
It pretty much all rapidly clicked into place from there. The idea of adding content as markdown is so easy and appealing, and the flow is so logical. The build times make me smile. Everything feels so rapid and under my control.
It's maybe an issue with me but I've been on blogotext where I would post stuff, then on Hugo but the tooling was taking most of my energy and the version upgrade path was a blocker for my themes, plugins, etc. I was clueless how to solve those pains without coding and opening issues. Then I tried zola but it was buggy, and I had to learn Rust to fix one basic issue which took days of rewriting code review after review.
And having yet to setup a pipeline and fight to make that work, just too much for me.
Then I went to WordPress and didn't had to mess with trying to make the blogging system adapt to my needs with code, it was just flexible enough with a nice WYSIWYG editor and admin panel and plugins. No mess with ci/cd build times, manual upgrades and reading language specs and opening issues to make things work. Those things were not needed to just blog.
Today I'm still on WordPress and none of the SSG feel simple enough to me.
Git, markdown, build pipelines... Code editor. It's all fun for work and collaboration with devs but just out of interest for blogging.
Also they mostly generate invalid HTML and lack features or have custom templates. And next upgrade could break everything.
I prefer something that is helping me focus on blogging for long term without upgrade maintenance cost and without fearing platform dies.
But yeah WordPress is not perfect and I'm considering maybe to glue a few tools together in the long run and make my edits in pure txt or HTML for which no existing SSG or WordPress are needed.
Considering that 99 years ago both Maldives and India were still colonised (and would remain so for decades), I'm gonna go out on a limb by saying that no, Chagos Islands weren't seen as particularly important back then.
This is like a backend developer asking someone using a spreadsheet why don't they just build their own database. Or a sysadmin telling you why don't you just run your own Kubernetes cluster. Unless there's like a 10 person team working on the same thing, you gotta take shortcuts somewhere.
Not here to argue that learning CSS properly isn't better, but I legit have no interest in doing so. I can copy-paste that code and be sure it'll look exactly the same on my website. I can't do the same with CSS.
To be clear, you have to 'learn CSS properly' to make sense of Tailwind. I don't see how someone can not know CSS, but know Tailwind. Tailwind is just atomic classes for the underlying CSS styles.
> I don't see how someone can not know CSS, but know Tailwind.
I've met a fair amount of devs (specially younger, <30yo fullstack devs) who have not written raw CSS at all and just use Tailwind. They are employed and get paid decently well.
Tailwind is a massive time saver, and I can see the appeal.
I can honestly say that tailwind made me way better at CSS. Going through the docs to find classes I needed to do particular things and reading what they did had made me so much better at understanding what it does at a low level. I would still prefer not to write tailwind classes rather than struggle with naming bespoke classes and writing all the CSS but it's definitely made me a better and faster frontend developer
The music industry has a long, long history of people paying to put songs in prominent places. If you built it yourself you would be 100% confident that nobody was paying the person compiling the playlist to put songs on it.
Well, at least at first. If your playlist derived from the ambient music of a particular streetcorner in Berlin becomes popular enough, someone would probably try hanging out there blasting their new song 24/7. Someone else might try approaching you about working out a deal to pay you to slip their new song into the mix. And of course you can never know who's paying to put songs on whatever stations or playlists the locals are listening to.
Some pretty interesting things would probably happen as the result of your goofy little fun project getting big enough to start having these problems though.
What more could one possibly need than "it'd be fun to build"? Does everything in the world have to be novel and important? Or can some things just be cool and for fun?
What I was going for (but poorly expressed) is that if your goal is to figure out what people listen to within a geographical area, streaming service data seems far more comprehensive than putting one mic on one random street.
The goal here seems more focused towards informing people about the existence and imprecision of shot spotters than actually trying to determine anything about regional music interests.
Not considered stable just yet, but it works well-enough for me.