I like to write SVG by hand with a text editor and Firefox, but that's probably not for most people.
I mainly like it, because you're entering all the coordinates as numbers, which makes ratios more apparent and also easy to work with...
Yep, that one's the Holocene.
I think, it works kind of well in games where you're able to enslave/recruit the random encouters (Pokémon, Shin Megami Tensei and such), as it's then a surprise what you'll find, somewhat like a slot machine.
But the way the more recent entries work in these series, that you find out what creatures roam the world by exploring, that kind of works, too.
More generally, I don't particularly like the problem that random encounters solve. Which is that you've got sections of gameplay where nothing happens, so you throw enemy encounters into there. That also goes for non-random encounters.
RPGs do this and I used to enjoy RPGs as a form of escapism. But now that I'm doing more stuff in real-life, I want it condensed down in roguelike form, or I'll just play other genres...
Are you sure about that?
Man, sometimes I wish courts were a lot sassier.
the customer and his wife had made threats to publicise the claimant's email in the press, social media and/or Trustpilot.
Bam! Perfect evidence that the customer is a twat.
Oh yeah, I wasn't trying to say no forks existed beforehand. There just weren't as many active ones.
I'm glad that forks are becoming a thing, again. The community (including myself) have slacked off for far too long, just taking it for granted that a browser was provided to them.
And people got seriously offended by any choice Mozilla made, even though the source code is right there. I get that not everyone has the skill to modify the source code, but enough people do that we should be able to cover various different preferences.
Would be even cooler, if the grassroots community started pushing the browser forward more, rather than just doing things different from Mozilla, but it's a good first step.
And Pocket isn't very intrusive either, is the point you were trying to make, right?
To my knowledge, it's the recommendations on about:home, which can easily be disabled, and then just a glorified bookmark to access Pocket. If you want it gone from the UI, set extensions.pocket.enabled
to false in about:config.
There's two things at play here.
MP3 (or WAV, OGG, FLAC etc.) provide a way to encode polyphony and stereo and such into a sequence of bytes.
And then separately, there's Unicode (or ASCII) for encoding letters into bytes. These are just big tables which say e.g.:
01000001
= uppercase 'A'01000010
= uppercase 'B'01100001
= lowercase 'A'
So, what your text editor does, is that it looks at the sequence of bytes that MP3 encoded and then it just looks into its table and somewhat erronously interprets it as individual letters.
Well, uh, mine is Kate. Not sure, if you need much selling on that, then.
I use it with an LSP server to provide highlighting and refactorings for Rust. Other languages are available.
The project-wide search & replace feature is really useful. It's available from the bottom bar.
In the settings, you can activate the "Filesystem Browser" plugin, which I sometimes prefer compared to the Projects view or the Documents view.
You can search for features with Ctrl+Alt+i.
In general, though, it's lightweight and easy to use. It's not going to win an award for a riveting new usage concept, which is why I like it.
I mean, to some degree definitely yes. You do need some upfront knowledge and some editing steps can be quite tedious.
I zone out while shoving shapes around the place, so I actually enjoy doing it in my freetime.
Having said that, we are talking about icons. You usually don't want those to be particularly complex anyways.
But the SVG format is also more powerful than one might expect.
You've got a collection of basic shapes. Particularly, paths allow you to draw essentially anything, including some really useful curves. And you can also do some cool gradients and even animations.
And you can use fonts in the text element, but only like in HTML, i.e. you specify "bold" or "Times New Roman" and hope wherever it's displayed has that font available. Would definitely not recommend that for an icon.
Inkscape allows converting text to a
path
, so that it doesn't depend on the host system. So, if I ever want a font in an icon, I'd do that in Inkscape and then copy thepath
element that it created into my text editor.