Personal web server running dual stack since early 2010s currently sees 18-20% v6 traffic. When split by type, counting only mobile users it reaches 30% at peak.

Bot/crawler traffic is ironically 100% v4.

Meanwhile: enabled h3 in september last year for the fun of it, instantly at >40% traffic by request count, passing 50% since the beginning of the year, h2 accounting almost all the remaining traffic and plain ssl/http requests <1% being just bots.

An even bigger one is hardcoding black and white instead of using foreground/background and use reverse when needed.

Comments URL: https://news.ycombinator.com/item?id=46845642

Points: 139

# Comments: 60

Yes, indeed. But I still stand by the gatekeeping though.

Sadly, it's a tragedy due to how popular github (and similar services) have become.

These sites were supposed to be by developers for developers.

Moving off github into a more niche platform was the best choice I have ever made to curb such zero-effort issue and feature requests. It raises the barrier just enough.

On the other hand, I'm a dev, and I hate the "start a discussion first" gatekeeping. I participated in projects where the approach is to start a discussion on a forum first, and I get the same feeling you have as a tech guy calling ISP support on the phone.

Every single web or mobile app does his own custom thing nowadays. As a user I couldn't care less how it's implemented, what I want consistency in behavior and style across the board.

It feels like this has been completely lost, even on platforms like mac where consistency used to be important.

I'd take MFC everything over random behavior if I could.

I've been using emacs with the "lucid" build since forever, as it's the leanest build that still gets a graphical window working on X11 and see none of the actual "toolkit".

I guess the pgtk build is required nowdays for native wayland support.

I was hit by this scenario in the 2000s with an old desktop pc I had, also in the 10ys range, I was using just for boring stuff and random browsing, which was old, but perfectly adequate for the purpose. With time programs got rebuilt with some version of SSE it didn't support. When even firefox switched to the new instruction set, I had to essentially trash a perfectly working desktop pc as it became useless for the purpose.

See the old apple gun vs squirt gun. The same is true also when using stuff like whatsapp on android, where the os keyboard shows you one image from the system theme, but the one which you see inserted in the text is not what you selected, but at least is partially better than sending something without knowing how it will be rendered, which is what most chat messages have realized after trying to simply using the system font.

So at that point, you have to switch to a different custom font just for the emoji block, and you're still limited to what unicode allows instead of just bundling whatever image you want (which is a great excuse to sell new phones with "new emojis" I guess).

On top of that, there are only very few emojis that can be read properly at the same size of the current line height. It works for a few simplified faces and symbols, but that's it.

The fact that emoji fonts override the font color rendering is an aggravating factor. I don't want text to change color behind my choice (it SUCKS with customized color themes).

They feel like a punch in the face to me when I'm reading documentation or even worse when reading code.

Sadly, it's really hard to avoid them nowdays. I'm using a few lisp scripts with emacs to translate the common ones back to ascii for rendering.

I can point out that "Noto Emoji" is a b/w version of Noto Color Emoji, which contains a MUCH more suitable version of emojis that can be used in running text. As noted before, it's only a partial solution as I find most emojis are still not readable when scaled at the same size as the text and when simplified sometimes they also lose the original meaning (just use the damn word dammit!). But at least they don't override the color. On linux, you can force a font substitution with fontconfig to force the b/w version whenever color-emoji is used and can't be customized.

Under most cases, you won't get the same inter-layer adhesion with ABS, so while you get better impact resistance, under most circumstances PETG will yield more durable parts that won't delaminate under the same stress conditions. For outside use under the sun, you should use it's cousin ASA.

To respond to the OP.. 3D printed parts can be incredibly durable when printed correctly. The parts need to be designed for 3d-printing in mind, like most other manufacturing methods. A 1cm-thick 15% filled PLA slab that has been printed vertically might be easy to snap in half with two hands, but it becomes almost impossible to break with bare hands when printed horizontal, and requires a saw to be cut when filled to 50%+. And this using consumer-grade printers.

I'm using 3d-printed parts for work and at home, some in use for almost 7 years at this point, and the only telltale sign is the layered look.

The rods in the design are not 3d-printed, which makes sense (most plastics would be too flexible, and 3d-printing a rod is always more expensive).

I haven't keep up lately, but as a linux-only dev, is there any hw combo which would give me full native hardware support and the ability to develop for the platform?

(I don't count linux-on-[android|win] as a solution)

As a student I used a ton of warez software in the 90ies. As such, I didn't have any real prejudice back then, and photoshop was the worst of the bunch from my perspective. I held that view for a long time, akin to how I consider autocad from autodesk one of the worst cads you could use despite being outrageously popular.

I have no longer an opinion on it as I didn't use it for such a long time. I'm cycling between krita and GIMP, and GIMP's UI is just fine to me, in the same way I suppose a ton of designers-with-big-opinions are more familiar with photoshop due to all the training they did on it (and probably, _mostly_ on it).