Hacker Newsnew | past | comments | ask | show | jobs | submit | evanharwin's commentslogin

> a small fraction of kids branching off into fringe networks that are off the radar and will take them to very dark places very quickly.

‘Fringe networks’, and ‘off the radar’ feel like a very negative framing for a kind of smaller, more intimate, and often pleasantly communal feeling internet that I quite like!

Old fashioned online forums—maybe even Hackernews itself?—would likely fit into this ‘fringe’, ‘off the radar’ internet, and yet, it still feels much less toxic here than it does on twitter.

> The real problem is social media. Their machine learning algorithms are optimised to boost toxic content

…and you need a massive network to enable this, right? You can’t do it without the money, and the volume of content, that the giants in this space have.

If this just pushes kids onto the small web—sure, it’s not _all_ wholesome—but at least it’s not as carefully, as deliberately manipulative.


I wonder if social media could actually be a really positive push for the “small stakes big thinkers” type, in some cases.

There’s loads of great content on YouTube for example, with channels doing genuine and interesting science and experimentation in public. Channels like Breaking Taps, Journey to the Microcosmos, The Thought Emporium, all come to mind, for me. I’m sure you can think of others.

More hackernews-coded, perhaps, there’s also lots of cool small blogs positing some pretty neat ideas… although, sites like YouTube might arguably provide easier access to finance for sustaining these people!


This makes me think - is it actually bad for Amazon/Google/Microsoft, that they now have to pay a licensing fee to Redis?

I feel like there’s an argument that these kind of licensing terms are almost beneficial to ‘big cloud’ because the cost/effort of all of these arrangements might dissuade smaller companies from trying to compete in the hosting and managed-services business.


Microsoft announced on the same day as the Redis license change that Azure's managed Redis offering will continue to run against the latest releases: https://azure.microsoft.com/en-us/blog/redis-license-update-...

Meaning that Microsoft is "paying to play" with Redis Ltd... while I have not seen any announcements from AWS or GCP.


I do wonder if Microsoft kicked this all off by telling Redis Ltd that they were willing to pay beforehand.


Yes, this seems likely since there is almost no way that an announcement from Microsoft would happen so quickly. There were months of back and forth of licensing meetings prior to this with Redis Labs and Microsoft.

Microsoft would never just announce something like this on a whim.


they don't have to pay. they offer a Redis-compatible service. whatever it is, nobody knows, and almost nobody cares. (sure, in practice they just forked it. but it was not AGPL-like when the fork happened, so ... c'est la vie)


Appreciate both the clear feeling and nuanced take here!

It’s interesting, because it’s like the problem is partly that most of the CI offerings out there are at least a little bit gross, but also the vast number of mediocre CI offerings is a factor too.

It feels like it’d be easy to convince yourself that what you’ve built is better than everything that exists already, and hey, maybe it is! But personally I wonder if we really need is a step-change here, not an incremental improvement—something that really does make build and deploy easier, and changes how we all think about it too.


My life experience has been that answering the question is almost always a matter of "easier ... for whom ... to do what?" I think CI/CD systems often run up against the same problem that programming language adoption runs into: trying to be all things to all people for all problem domains is incredibly hard

Even what I mentioned about static typing I'm sure caused a blood-pressure spike in some readers, since some folks value the type safety and others consider it "line noise". Some people enjoy the double-quote free experience of yaml, others pound on their desk about the 7 ways to encode scalars and "but muh norway!!11"

But, taking our ragingly dumbass buildspec friend <https://docs.aws.amazon.com/codebuild/latest/userguide/build...> as a concrete example, how in the holy hell did they invent some build language without conditionals?! I'm sure the answer is "well, for our Amazon-centric use case, you're holding it wrong" but for someone coming from GitLab CI and GitHub Actions which both have "skip this job if today is Tuesday" it's a pretty glaring oversight


Agreed. Seems like web search implementation (both from Kagi and all its competitors!) could be almost endlessly improved upon, and any non-search feature is at odds with that.

Maybe there’s an argument that people who might use this, might also be people with sites that’d be valuable to index, and thus it’d both be nice for them and improve search for all users? :)


Wow I like it, simple like Flask, but with the HTML in the same file (as opposed to the jinja templates) which is a pattern I really like!

Makes me wonder if you could integrate this ambition to do the web-stuff in your Python file with the FastAPI/Pydantic BaseModel situation. Like a HTML templating library made out of Python data classes (or Pydantic BaseModels).

Either way, I respect the ambition! :) Always cool to see web stuff with Python.


Flask's routes return strings, there's nothing stopping you from doing this. The render_template function is just a convenience.


Technically the string return type is just a shorthand, IIRC render_template returns a Response object that sets Content-Type and other things appropriately. But yeah it’s pretty trivial to create an HTML formatting library and use it with Flask. (I think there’s already libraries for the tag syntax, you just need to hook it into Flask, or literally any Python web framework really.)


A lot of the scenarios described here aren’t “firing” someone, as I understand it, but making someone redundant.

The difference being that being fired suggests the employee did something to deserve it, but being made redundant could happen to the best of employees.


We don't really use that term (making someone redundant) in the U.S. I've heard it on British shows so I assume that's where you are. It means laying someone off, right? Meaning a workforce reduction?


Yeah, exactly - with this context the article makes a bit more sense to me! :)


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: