Hacker News new | past | comments | ask | show | jobs | submit | l-p's comments login

> - some visual artifacts with the gtk menu

You need a compositor. picom works.

For a proper "native i3 experience" I recommend setting gtk-titlebar=false and unbinding tab/pane management keybinds. I already have a window manager, I don't need a second one.

I also had to disable adwaita because when it's enabled closing a shell with ^D closes all open windows, sometimes it leaves an empty window instead.

> - xterm still feel faster to me.

lxterminal also launches 6 times faster, I guess on a slow laptop without a dedicated GPU these terminals are not the most efficient option.


there's a black box after i click the burger menu button.


Looks composited to me, look at the odd wobble of the picture overlapping the Gonarch, that's not present in the original video.


I've been using Hammer since the Worldcraft 3 days, it took less than an hour of using TrenchBroom to know I'll never go back to Hammer or JACK.

It just works. The overall modelling workflow is much more efficient, it's well designed, linked groups is a killer feature, it doesn't crash for no reason and when it does crash you can submit an issue and get it fixed in a day (or fix it yourself, it's FOSS), CSG (e.g. the carve tool) produces sane geometry in a few milliseconds instead of crashing after a 20s freeze.

It also runs smooth and fast whereas hammer stutters all the time and feels like it renders its viewports and UI at 20 fps.

The apparent simplicity is a feature in itself, not a lack of functionality.


> it doesn't crash for no reason

From my doom level editing days, this was always the biggest issue; the level editors were so very touchy, and would crash all the time.


I started maintaining uBlock filters to avoid being spammed by intrusive ads a for a service I neither need nor want.

https://gist.github.com/L-P/cfee57bd0835c88262e29ff3a1f09b60

I'm slightly irritated by AWS making the same errors Azure did on their portal. Keep your ads out of my tools.


> caps lock should be eliminated everywhere

Caps Lock is a necessary feature.

I need my ÉÈÀÇ and I never could get a compose key working in all inputs, Caps Lock is the only reasonable alternative.


If you're in need of AZERTY-specific keys and you're on a QWERTY layout, take a look at https://github.com/qwerty-fr/qwerty-fr.

It's a strict superset of QWERTY, and it enables entering e.g. è and È with altgr+e and shift+altgr+e respectively.


US-intl can do that just fine, though some people can't stand dead keys.


Whether dead keys are acceptable or not depends heavily on how frequent they are in the language.

The Danish keyboard layout has ¨, ^, ´ and ` on dead keys — those are used in foreign names and a few loanwords — but Æ, Ø, Å are real keys.

Having Å, Ø and Æ as dead keys would make as much sense as having V, K and J as dead keys in English.


I use it to type in Danish and Italian, as it happens (plus Swedish and French every now and then).

Æ, Ø, Å aren't dead keys, they're available via AltGr + Z, L, and W respectively. However, Italian and French accented letters (as well as Swedish/German Ä/Ö) are available via either AltGr or dead keys - and I find myself almost always using dead keys, perhaps because they are more "logical" so I learned them faster.

And of course, typing any kind of quote is a dead key in every language (quote followed by spacebar).

By now, after so many years, dead keys are well in muscle memory so they feel barely any slower to type than regular two-key combos (like uppercase letters).


0.48 is not even released yet (still a RC) you'll have to wait a bit more for 0.49.

There's nothing preventing you from building it yourself though, the master branch is stable and you can complete the game without a single crash or game-breaking bug.


The README.md certainly is confusing then:

  Version: 0.49.0


> If Reddit replaces volunteer mods with paid mods we would get a more > consistent moderation and almost certainly a more professional experience.

I can guarantee you the opposite. You'll have a site-wide abusable Scunthorpe-incompatible report-based automated moderation with no proper appeal mechanism in place because half a dozen underpaid interns/offshored employees will be responsible for taking over the work of hundreds of moderators.

It's already happening in some cases. There's ways to make reports go directly to the so-called Anti-Evil Operations team who will irrevocably override any moderation decision and enforce abusive reports.

It's easy to get people banned, post some hateful content, wait for reports, and then report the reports for report abuse.

> But I can't think of any other social site that has such a bad rep for moderation.

There are some legitimate cases of poorly moderated subreddits and mod abuse (and the whole powermod issue), but beware, most of the time people complaining about power-tripping mods and "not being able to say anything anymore" have been banned for very good reasons (those reasons being straight-up hate speech most of the time).


Yes, but we even give murderers due process. You don't have any civil liberties with reddit, but if the punishment doesn't fit the crime or you know they just used the rules as a pretext to squash dissent, it's going to leave a bad taste.

They can do whatever they want with their platform, but I can also not like mods who make decisions I don't agree with.

I also don't think mods should be allowed to ban people just for being subscribed to other subs or having posted there. The whole idea that I co-sign everything the sub stands for just because I read it tells you all you need to know: they expect and often demand that you do in fact co-sign everything the sub stands for.

And that's the fundamental problem with reddit, really. It's not just the keyword squatting mods: it's that it's a giant social experiment that distills the worst of mob behavior and anonymity.

Fixing reddit requires some kind of check on the mods and the elimination or complete overhaul of the karma system.


They are.

We caught "community builders" making disingenuous posts trying to pass reposted/translated content as OC to generate engagement. After getting caught doing so with their admin accounts they tried again using normal users.

They also had the bright idea to spam users via DM using a poorly templated message (verbatim "insert u/USERNAME") to promote localized copies of low-quality subs (the kind of trash you see on r/all).


For anyone wanting further information about this: https://old.reddit.com/r/SubredditDrama/comments/13p889x/red...


This is how Reddit started. In the very beginning of the site the founders had a couple of accounts they would use to put content on the site. It's in Reddit's DNA so to speak.


I'm partial to the Moutarde de Charroux, made with Saint Pourçain (a local wine).

https://www.huiles-et-moutardes.com


> I'd be curious to know what's good or bad about it compared to GCP and AWS.

Documentation lies, support lies, metrics lie, bugs everywhere, and when something breaks the status page is always all green and support tries to convince you it's your fault anyway. They're only here to prevent you from enforcing the SLA. The distrust is pervasive. I stopped suspecting my code, if something breaks outside of a planned maintenance it is _always_ Azure.

My latest support ticket: Azure App Service internal DNS server broke and there is no way to bypass it short of hardcoding IPs in /etc/hosts. Support told me that if I wanted App Service to work reliably I had to implement their DNS server myself. To rephrase, my PaaS provider told me to spend time and money to implement the very platform I was paying them for, and it just so happened to be absolutely impossible because of an unannounced BC break a few months prior (which is another lengthy and frustrating story).

This morning I had a VM cut out of the network and 10% of my App Service traffic just disappeared. No explanation, no incident report, nothing.

These days I'm working with AWS, and it just works. If something isn't working you know it's your fault and that the answer is in the documentation. I'm not spending days on workarounds, I'm actually implementing as planned. I have no words to describe the relief I'm feeling.


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

Search: