In other news today...
-
Other swatting incidents have had even more devastating consequences. In 2017, a Kansas man was shot to death by police responding to a swatting call. The man who made that call was sentenced to 20 years in prison last year.
And I'm sure the police had no fault in that.
-
@Dragoon said in In other news today...:
I hope his arrest involved a large group of armed people invading his home and throwing him on the ground.
-
I've been using Fira Code since @pie_flavor convinced me of the awesomeness of code ligatures. With JetBrains shipping their font as default in their IDEs, this might see more widespread adoption.
-
@topspin said in In other news today...:
I've been using Fira Code since @pie_flavor convinced me of the awesomeness of code ligatures.
And what's awesome about them?
-
@MrL said in In other news today...:
@topspin said in In other news today...:
I've been using Fira Code since @pie_flavor convinced me of the awesomeness of code ligatures.
And what's awesome about them?
As the JetBrains page mentions it's good for two things:
Better spacing balance, e.g. C++ scoping operator::
looks nicer than two sequential colons, and nice symbols, e.g.->
,<=
, etc. get merged to what they actually mean.if (i <= j && k != 0) foo->bar();
It takes a bit to get used to at first.
-
We had them back when I was doing APL.
-
@topspin said in In other news today...:
@MrL said in In other news today...:
@topspin said in In other news today...:
I've been using Fira Code since @pie_flavor convinced me of the awesomeness of code ligatures.
And what's awesome about them?
As the JetBrains page mentions it's good for two things:
Better spacing balance, e.g. C++ scoping operator::
looks nicer than two sequential colons, and nice symbols, e.g.->
,<=
, etc. get merged to what they actually mean.if (i <= j && k != 0) foo->bar();
It takes a bit to get used to at first.
Not a fan of merging the symbols. Tried it for a bit (definitely not long enough to get used to it). Back to Mono.
-
@topspin I took a quick try, but almost immediately switched back to ubuntu mono. It's too wiry for my taste, and it seems the ligature and relative positioning magic doesn't work in gnome-terminal.
-
-
@topspin said in In other news today...:
@MrL said in In other news today...:
@topspin said in In other news today...:
I've been using Fira Code since @pie_flavor convinced me of the awesomeness of code ligatures.
And what's awesome about them?
As the JetBrains page mentions it's good for two things:
Better spacing balance, e.g. C++ scoping operator::
looks nicer than two sequential colons, and nice symbols, e.g.->
,<=
, etc. get merged to what they actually mean.if (i <= j && k != 0) foo->bar();
It takes a bit to get used to at first.
I have numerous problems with this
- Code looks completely different on your screen and elsewhere. So you have to be comfortable with two modes of parsing code, instead of one.
- Inconsistent movement of caret while typing would drive me crazy.
- All ligature fonts I've seen are ugly.
- What's written is not what's displayed... it feels WRONG.
-
@MrL Not gonna lie, it feels a bit weird when the glyphs subtantially change after an edit, but there's little to no inconsistent caret movement.
-
I'd heard of it before but never tried. So let's give it a go, we'll see.
@topspin said in In other news today...:
Better spacing balance, e.g. C++ scoping operator
::
looks nicer than two sequential colons,Right from the start,
::
looks to me much uglier with the ligature, because while the two colons are indeed closer and maybe nicer than in monospace, the overall spacing between the two words is not changed, so there is more whitespace around the::
.I.e. instead of
f o o : : b a r
it now looks likef o o :: b a r
whereas I would probably have preferredf o o :: b a r
(small things, I know, but that's what those ligatures are all about anyway!).and nice symbols, e.g.
->
Not working (VS 2017). Dunno why,
=>
works (but in C++ I don't need that).It takes a bit to get used to at first.
Yeah, currently I'm not convinced, but I'll give it a few days.
-
@topspin said in In other news today...:
And I'm sure the police had no fault in that.
Of course not.
They investigated themselves and found they did nothing wrong
-
@MrL said in In other news today...:
@topspin said in In other news today...:
@MrL said in In other news today...:
@topspin said in In other news today...:
I've been using Fira Code since @pie_flavor convinced me of the awesomeness of code ligatures.
And what's awesome about them?
As the JetBrains page mentions it's good for two things:
Better spacing balance, e.g. C++ scoping operator::
looks nicer than two sequential colons, and nice symbols, e.g.->
,<=
, etc. get merged to what they actually mean.if (i <= j && k != 0) foo->bar();
It takes a bit to get used to at first.
I have numerous problems with this
You should've stated that your question was rhetorical, I needn't have bothered to reply.
- Code looks completely different on your screen and elsewhere. So you have to be comfortable with two modes of parsing code, instead of one.
That's why I said it will hopefully see more adoption. I haven't had any problems with this, though, it's quite minor. It's rather like having a color TV while everyone else still has monochrome, you take the improvement where you get it instead of being bothered by not having it everywhere.
- Inconsistent movement of caret while typing would drive me crazy.
- All ligature fonts I've seen are ugly.
Doesn't sound like an arguments against ligatures, unless you're saying the ligatures are ugly and not just the non-ligatures compared to a different font.
- What's written is not what's displayed... it feels WRONG.
That's kind of backwards, as what's displayed it what should be written in the first place. I don't have a key for â on my keyboard, though, so typing
!=
as it's always been is a reasonable input method.
-
@Zecc said in In other news today...:
@JBert It's a platform game where you don't actually jump. Instead you can only invert gravity.
"VVVVVV" is, I assume, a reference to the spikes usually present in such games (including this one).
I thought "VVVVVV" ("the letter V six times") refers to the names of the player's character and his five spaceshipmates.
-
-
-
@topspin said in In other news today...:
As the JetBrains page mentions it's good for two things:
Better spacing balance, e.g. C++ scoping operator::
looks nicer than two sequential colonsNothing::makes colon::cancer look::good.
-
@topspin said in In other news today...:
@MrL said in In other news today...:
- Code looks completely different on your screen and elsewhere. So you have to be comfortable with two modes of parsing code, instead of one.
That's why I said it will hopefully see more adoption. I haven't had any problems with this, though, it's quite minor. It's rather like having a color TV while everyone else still has monochrome, you take the improvement where you get it instead of being bothered by not having it everywhere.
It requires the user to know two things instead of just one. With normal fonts, I see the code that I type with the characters that I put there. With ligature fonts, I would additionally have to have a mental mapping that coordinates the text I see on the screen or elsewhere with the characters that produce the ligature symbols. It violates WYTIWYS.
- Inconsistent movement of caret while typing would drive me crazy.
Sometimes your cursor moves over a whole symbol, but sometimes it moves halfway or a third of the way across a displayed symbol. With normal fonts, the cursor always moves over a whole symbol.
- All ligature fonts I've seen are ugly.
Doesn't sound like an arguments against ligatures, unless you're saying the ligatures are ugly and not just the non-ligatures compared to a different font.
It's hard to have symbols that fit a single-character width look consistent with symbols that stretch across two or three character widths.
- What's written is not what's displayed... it feels WRONG.
That's kind of backwards, as what's displayed it what should be written in the first place. I don't have a key for â on my keyboard, though, so typing
!=
as it's always been is a reasonable input method.But that requires extra knowledge that those keys will produce that character. Also, does it show
â
when you type != and <>? How is the coder supposed to know which keys to type to get the right inequality operator for their current language?
-
@djls45 said in In other news today...:
Also, does it show
â
when you type != and <>? How is the coder supposed to know which keys to type to get the right inequality operator for their current language?This is particularly relevant given that there are at least one language where
!=
and<>
are both semantically valid (and mean completely different things).
-
@Mason_Wheeler said in In other news today...:
@topspin said in In other news today...:
As the JetBrains page mentions it's good for two things:
Better spacing balance, e.g. C++ scoping operator::
looks nicer than two sequential colonsNothing::makes colon::cancer look::good.
Or is it that you just dislike C++ in general? It makes more sense than just using a dot for everything, especially in the C++ space where it's important to know whether a member access operation is static (x::y), direct (x.y), or indirect (x->y).
-
@Mason_Wheeler said in In other news today...:
@djls45 said in In other news today...:
Also, does it show
â
when you type != and <>? How is the coder supposed to know which keys to type to get the right inequality operator for their current language?This is particularly relevant given that there are at least one language where
!=
and<>
are both semantically valid (and mean completely different things).Oh, good point. I hadn't thought of that! But it further supports the point that a font should not need to know anything about the semantics of the text it is being used to display.
-
@djls45 said in In other news today...:
Also, does it show â when you type != and <>?
No, it's shows a diamond for <>. Pause the video in my post at around 0:51.
-
@Zecc Code ligatures are good for reading code, not for writing.
So it's usefulness is influenced by which you do the most.
-
@Zecc said in In other news today...:
@Zecc Code ligatures are good for reading code, not for writing.
So it's usefulness is influenced by which you do the most.So it's good for code reviewers, but not code writers. But then when you consider the fact that most (all?) code reviewers are also code writers...
-
Maybe I'm misunderstanding what they mean but to me that looks like it invalidates everything they said in the paragraph.
-
@djls45 said in In other news today...:
Also, does it show
â
when you type != and <>?Fira Code doesn't, it shows a "diamond" for
<>
. It's obviously up to the font designer what to do, but to make it useful it should not be unintuitive, which mapping to different sequences to the same symbol would be.How is the coder supposed to know which keys to type to get the right inequality operator for their current language?
The same way he's doing that right now. He already knows that.
-
@hungrier said in In other news today...:
Maybe I'm misunderstanding what they mean but to me that looks like it invalidates everything they said in the paragraph.
Agreed, I didn't get that either.
-
-
@djls45 said in In other news today...:
How is the coder supposed to know which keys to type to get the right inequality operator for their current language?
The same way they know how to type the right keys for anything in their current language. What you type doesn't change
-
@Zecc said in In other news today...:
@Zecc Code ligatures are good for reading code, not for writing.
So it's usefulness is influenced by which you do the most.Besides the obvious point that code is read more often than it's written... You
writetype exactly the same thing as before, you just see more readable output.
-
@Zecc said in In other news today...:
@MrL Not gonna lie, it feels a bit weird when the glyphs subtantially change after an edit, but there's little to no inconsistent caret movement.
That's horrible.
@topspin said in In other news today...:
You should've stated that your question was rhetorical, I needn't have bothered to reply.
It wasn't.
That's why I said it will hopefully see more adoption. I haven't had any problems with this, though, it's quite minor. It's rather like having a color TV while everyone else still has monochrome, you take the improvement where you get it instead of being bothered by not having it everywhere.
The most important rule of code readability is Similar things should look similar, different things should look different. Parsing code is a lot faster and easier when it's the case.
I know it sounds like not much, but it's a real overhead to translate between different representations.
- Inconsistent movement of caret while typing would drive me crazy.
You push a button, sometimes new character appears on the screen, sometimes not. Weird.
- All ligature fonts I've seen are ugly.
Doesn't sound like an arguments against ligatures, unless you're saying the ligatures are ugly and not just the non-ligatures compared to a different font.
"It's ugly" is a great argument against using a font, ligature or not.
- What's written is not what's displayed... it feels WRONG.
That's kind of backwards, as what's displayed it what should be written in the first place.
But it's not what is written.
-
@Zecc said in In other news today...:
@djls45 said in In other news today...:
Also, does it show â when you type != and <>?
No, it's shows a diamond for <>. Pause the video in my post at around 0:51.
@topspin said in In other news today...:
@djls45 said in In other news today...:
Also, does it show
â
when you type != and <>?Fira Code doesn't, it shows a "diamond" for
<>
. It's obviously up to the font designer what to do, but to make it useful it should not be unintuitive, which mapping to different sequences to the same symbol would be.So these ligature fonts either do nothing or are actively antagonistic towards SQL? And recall that lots of code uses SQL or SQL-derivatives for database interactions, so it's not a light thing that can simply be ignored.
-
@djls45 they're created for a certain purpose, obviously. They may fit your use case, in which it makes sense to use them, or they don't in which case it doesn't. YMMV and all that.
-
Anyway, I may try out Jetbrains Mono and see if I like it better than Iosevka. My main reason for picking Iosevka over Fira Code is the nicer italics, which it looks like Jetbrains also has.
-
@topspin said in In other news today...:
IoT
The same shit as before, but with remote exploits.
StarTrek - in reality, this is how the Borg conquers us.
-
@Dragoon said in In other news today...:
The software giant patched 300+ bugs in its quarterly update.
But how many did they add?
-
@dcon said in In other news today...:
@topspin said in In other news today...:
IoT
The same shit as before, but with remote exploits.
StarTrek - in reality, this is how the Borg conquers us.
So, Battlestar Galactica?
-
@djls45 said in In other news today...:
Or is it that you just dislike C++ in general? It makes more sense than just using a dot for everything, especially in the C++ space where it's important to know whether a member access operation is static (x::y), direct (x.y), or indirect (x->y).
x::y isn't necessarily static, it could be direct.
-
-
article lists other funny names
includes a link to a tracking map that shows the names
they didn't include Sir Grits-a-lot in their list
-
@hungrier Sadly, there's too many to pick from.
For Your Ice Only is a brillant one, though an old one which also gets a chuckle is Brad Gritt.
EDIT: I almost forgot about David Plowie.
-
On the hardware side, it's got some neat stuff:
- removable battery
- 3.5mm slot
- notchless display
- microSD support
- USB-C
But the other stuff is very "Linux Hardware" ish:
- 1.2 GHz cpu
- 2 GB RAM
- 16 GB storage
- 2750 mAh battery
- 5 MP main camera, 2 MP self camera
-
-
@JBert Icegrittingtruck McIcegrittingtruckface
-
-
@hungrier So it's an old Android phone with none of the benefits of Android?
-
@anonymous234 said in In other news today...:
@JBert Icegrittingtruck McIcegrittingtruckface
Is that a real one? Because this one is supposed to drive around somewhere (at least if it survived since 2018):
-
@JBert once the Brits make a meme, they do go all in on it for years to follow, donât they?
-
@topspin said in In other news today...:
@JBert once the Brits make a meme, they do go all in on it for years to follow, donât they?
See also: Brexit ď