strkek

> Without the in-game ability to start over after making a mistake, you're forced to deal with whatever the game throws at you. No excuses, no rationalizations.

I found "Alien: Isolation" to be amazing in this aspect as well. You can only save at very specific points in the map (no quicksave), and in many situations where you might expect the game to be paused, like when saving progress, it's really not.

Makes you think twice before doing anything.

It's like the devs of Clang and GCC suddenly joined to define what "C20" means but bypassing ANSI and ISO processes.

I can perfectly see this implemented without breaking backwards compatibility, similar to how we have usermodes for "connected via SSL" and channel modes for "requires SSL".

It doesn't require breaking backwards compatibility because, as far as outdated clients are concerned, they just "can't enter a channel because they lack a required usermode" or "can't send a message to some user because they lack a required usermode".

We only need the spec to define "some way" to do it so clients can announce their support and servers know what to do with the supporting clients.

Then it's up to IRC daemons to provide some modes for it.

And federated too, if I may add.

Aren't they basically the ones controlling the protocol specs through the BitTorrent Enhancement Proposals (BEP)?

(Honest question.)

If you begin this, please leave a GitHub link so I can follow it :)

EDIT: Or a link to the repository, in case it's not hosted on GitHub.

Last time I checked you could create a directory with a name "like:this" from Linux or something, and Windows would display it but not allow you to access it in any way.

Have they fixed this? (Just pure curiosity)

As long as humans continue to be like we have been so far, i.e. with the mentality of destroying our own planet and not caring about it, or committing crimes like kidnapping, etc... as long as there are individuals like that, every time we humans learn something new, things will inevitably turn way more scarier.

Whether it's colonizing other planets or making a full-dive VR; just thinking about the time when we can do any of these things gives me a headache.

I wonder if this app has a drawer.

swipes to the right

> Message archived.

No wtf.

undo

Guess it doesn't.

Worse of all is that this abbreviation must have come from someone who had no idea what cryptocurrencies are; someone who thought it was "magical WoW money but better".

Because I just can't wrap my head around the fact that anyone who knows what a cryptocurrency is, is somehow unaware of all the massive prior art indicating that crypto=cryptography.

It's like calling light bulbs "glowing pears" (jk, I love the German language <3).

Chill.

It's both a user and UX problem. It's like when some part of a website's functionality is only available through Flash.

You know some (nowadays "most") people will have it disabled, and you're indirectly saying that you don't care about those users at all, which is not a bad thing.

It's the users' fault for not enabling Flash, sure, because they're not your target audience. But whether you provide a good UX for your non-target audience or not, it's your fault. And again, you're not obligated to accommodate those users, but that doesn't change the fact the you could give them a better UX but chose not to.

So, from this you can know that the users GitLab cares about are only a subset of the users GitHub cares about.

The article doesn't say which version, though.

Eh, I think they were talking about the UX for people that have JavaScript disabled, not about the JavaScript language.

To me it sounded more like "I can browse GitHub without JavaScript just fine, but GitLab doesn't even display the README, even though I'm using the exact same settings".

Obligatory link to the "YAML sucks" repo:

https://github.com/cblp/yaml-sucks

If you ignore the flame-inducing title, it's just a table showing how different implementations parse YAML input in very different ways.

> btw, did you notice how there are hardly any books, conferences or discussions about C despite being a fairly popular language?

Oh, yes. When I wanted to fiddle with OpenGL (and later SDL), I was baffled to find that absolutely everything documentation-wise was for C++.

EDIT: Sorry, "documentation" was probably the wrong word to use here. I meant "learning resources".

Most projects use buzzwords like that though.

- Safe! - Blazing fast! - Powerful! - Elegant! - Shiny! - Modern!

You know, marketing stuff that tells you absolutely nothing about the software itself but is required to fill space on a website.

The thing is, a boring "Benchmarks" heading in the README doesn't get you as many GitHub stars as a "Blazingly fast!" heading+icon. And you know how addictive Internet Points can be.

I think it's a situation sort of like with SSL and TLS, where the former term implies the latter. I mean, it's not rare to find people using the term "SSL Certificates" even on TLS-only setups. Also:

https://wiki.openssl.org/index.php/Libssl_API

> libssl is the portion of OpenSSL which supports TLS

It's for TLS support yet they call it "libssl".

So yeah, you can just mentally replace "RSS" with "RSS/Atom" and most of the time it'll be fine.

You'd still be able to use `C-[` though.

(And I actually use it in Termux)

> If you're frustrated, simple insert mode (`i`) is all you need to get back to your comfort zone.

Also, something I wish I knew back when I was learning is `:set nonumber` to turn off the gutter and be able to copy things with the mouse (`:set number` turns it back on).

If I had known this, my experience wouldn't have been as bad as it was until I learned to use the registers.

There's definitely something about forums that can't be found in social networks. I don't know what that is, but I know it's very unlikely that I'll have as much fun as in those days.

Not sure if it's because I was a teenager back then and perceived the internet differently, but nowadays everything looks way too "serious".

> In the end ~/go doesn't look a lot different than the @INC path that points to something in your home directory, or /usr/include, /usr/lib, and /usr/bin in a pure C system.

Well, yes and no, and that's the only thing I don't like about GOPATH: that your source code is not in GOPATH, but in `$GOPATH/src`.

I'm not against GOPATH per-se because I'm already used to other PATHs; I'm just against it not behaving like those other common PATH variables, like PATH, LD_LIBRARY_PATH, PYTHONPATH[1], etc. GOPATH introduces intermediary directories (src, pkg, bin), instead of going straight to the point and being only for source code.

I mean, there's `GOPATH` and also `GOBIN` which is just `$GOPATH/bin`. IMO it would make much more sense for GOPATH to be only source code, GOBIN to be only executables, and something like GOPKG for the current `$GOPATH/pkg`.

[1]: Yes I know venv is a thing, I'm just mentioning PYTHONPATH to illustrate my point.

I made[1] a zsh hook some time ago that allowed you to have per-project GOPATH.

At the root of the project I just have to do `echo 'github.com/username/package' > .gopkg` and after that, for everything I do under that directory tree, GOPATH will be automatically set to something like `export GOPATH="$(dirname .gopkg)/.gopath"`.

I don't use zsh anymore though.

[1]: https://gist.github.com/strkek/294c2f5e6fe94b8303b5121266b27...

Same here, but in my case when I need that I usually go with Mithril.js[1]. I found it by chance and instantly liked it. It's a shame that nobody seems to know it.

[1]: https://mithril.js.org/

Imagine my confusion back then.

I could push fine to BitBucket if I used Python 2 version locally, and same for my VPS if I used the Python 2 version both locally and remotely.

But as soon as I touched the Python 3 version of Mercurial the pull/push problems began. I don't recall the exact error and maybe it's fixed now (this happened like 6 months ago), but I don't think I'll give it another try for some time.

IIRC CPython devs reject performance-related patches if they cause the code to become "less readable".

>> I believe Mercurial is, finally, slowly porting to Python 3.

I just gave up on Mercurial since it didn't let me push to BitBucket nor to an Ubuntu VPS via SSH.

For better or worse, Git just works.

> Also, if you five away what a strong password consists of (case, length, characters, symbols) then doesn't that make it weaker because you give bots/attackers a pattern to follow?

I don't think it changes anything at all. Attackers won't ignore "dolphins" just because a meter says it's weak.

Unless it's an actual limitation of the site where you're signing up, in which case the culprit for the reduced search space would be the website for such password limitations, not because the password strength meter.

I'm very curious what will they do when Python 2 reaches EOL. Will they keep depending on deprecated software?

As weird as this might sound, I see WebAsssembly more like a portable shared library format than a JavaScript replacement.

Well, one thing that Cargo got wrong is forcing you to clone a full git repository when only the latest commit is relevant.

IMHO it should allow me to either use a shallow clone or use crates.io's API directly.