I was excited about it when it first came out, but haven't heard anything about it since.

This kind of makes the Digg team look like a joke. Rebuilding was always going to be hard, but I think this kills any chance of building it up a third time since no one can take it seriously.

Digg v3 was in 2006, this is at least v5 :)

I think there was a v4 that attempted to bridge the gap between v3 and v4.

Then v5 was when it wasn't curated at all and just a generic news aggregator.

So this is v6 I guess.

With time, I've been revoking the ability of more and more apps to deliver notifications. The vast majority of the notifications these days are just pointless ads anyway.

We use self-hosted GitLab at work. It’s really a pleasure to use, everything works the way it feels like it should. The main downside is the system resource requirements are absurd considering at any given time there’s only 1-2 people using the GitLab interface.

The prose style and the fact that it was super repetitive. Every bullet re-described the copy-pasting. Definitely LLM slop.

> Side note: anyone else have moments where you can’t press delete once predictive text has shown up?

Chiming in just to say: yes

> the engineers aren't complaining, in fact it is the opposite, they are actually more productive.

More productive isn't the opposite of complaining.

I don't hear any either way.

If an engineer complains in the woods and nobody is around to hear them, did they even complain at all?

How is no syntax highlighting better, specifically?

(To address sibling comment: If I were colorblind, I would lead with that in any conversation about syntax highlighting; I am not colorblind.)

To answer the question: it's a feeling, like lots of things in software development. I tried "no syntax highlighting", found that I liked it, and I no longer use syntax highlighting. To say "specifically" how it's "better"... I'm not even saying it's better. "I like no-syntax-highlighting" is the statement I'm making (which, when it comes to syntax highlighting, is a statement a lot of people have issues with). So, from my personal experience, I take issue with the statement that no-syntax-highlighting is making things "difficult for the sake of it".

Try this out for analogy: I ate Red Baron pizzas every Friday night for 15 years, then I heard about homemade pizza 10 years ago. I tried making homemade pizza. It was good! ("I tried it and liked it") Now I only eat homemade pizza on Fridays. How is homemade pizza specifically better? It's better because I like it more. That's all there is to it. It's a preference.

(For the analogy to work, you have to like or at some point have liked Red Baron frozen pizzas. I happen to like them... the analogy is flawed though, I admit!)

(Let me preempt criticism that I'm comparing Red Baron frozen pizzas to syntax highlighting. I am not. It's only about the preference, not the object of the preference.)

Not op, but in my case a lifetime of colourblindness has desensitised me to colour as an indicator.

I have my editor configured with zero highlighting for keywords and syntactic elements. Admittedly, I have compilation/lint/syntax/type check errors set to invert the erroneous block, black background white text.

Syntax and keyword highlighting is just noise given I’ve been trained by decades of colourblind unfriendly interfaces

Syntax highlighting doesn't necessarily mean color, though. Using boldface to highlight keywords is another option that is traditional in some circles (e.g. Delphi has been doing that for 30 years now).

that's a very good reason to not use syntax highlighting. If that is what the other guys are dealing with, I withdraw my critique but I don't get the impression that is the case

I agree and don’t use any of that stuff—-except syntax highlighting. Why wouldn’t you? Color is a whole extra dimension it adds to the code that lets the eye notice errors more quickly and jump around faster.

Unpopular opinion apparently: I love it. I’ve been using it since beta 1 and it’s grown on me enormously. iOS 18 on my work iPhone felt incredibly dated and I was relieved when we could finally upgrade enterprise devices.