Search
1000 results for “data0”
-
"The Eight Golden Rules of Interface Design
1. Strive for #consistency
2. Seek universal #usability
3. Offer informative #feedback
4. #Design #dialogs to yield closure
5. Prevent #errors
6. Permit easy reversal of actions
7. Keep users in control
8. Reduce short-term memory load" -
#Serif #terminal / #programming #fonts remain far and few between. Why? I find them more legible and there are a few out there that look really nice.
My favorites are "Go Mono" and "Luxi Mono", both by Holmes & Bigelow who did many of the popular (early) #Macintosh fonts. "PT Mono" is nice too (has less serifs). Give them a try for a few days and see yourself!
https://go.dev/blog/go-fonts
https://en.wikipedia.org/wiki/Luxi_fonts
https://www.paratype.com/fonts/pt/pt-mono#golang #monospace #gomono #luximono #ptmono #holmesandbigelow
-
#Serif #terminal / #programming #fonts remain far and few between. Why? I find them more legible and there are a few out there that look really nice.
My favorites are "Go Mono" and "Luxi Mono", both by Holmes & Bigelow who did many of the popular (early) #Macintosh fonts. "PT Mono" is nice too (has less serifs). Give them a try for a few days and see yourself!
https://go.dev/blog/go-fonts
https://en.wikipedia.org/wiki/Luxi_fonts
https://www.paratype.com/fonts/pt/pt-mono#golang #monospace #gomono #luximono #ptmono #holmesandbigelow
-
#Serif #terminal / #programming #fonts remain far and few between. Why? I find them more legible and there are a few out there that look really nice.
My favorites are "Go Mono" and "Luxi Mono", both by Holmes & Bigelow who did many of the popular (early) #Macintosh fonts. "PT Mono" is nice too (has less serifs). Give them a try for a few days and see yourself!
https://go.dev/blog/go-fonts
https://en.wikipedia.org/wiki/Luxi_fonts
https://www.paratype.com/fonts/pt/pt-mono#golang #monospace #gomono #luximono #ptmono #holmesandbigelow
-
#Serif #terminal / #programming #fonts remain far and few between. Why? I find them more legible and there are a few out there that look really nice.
My favorites are "Go Mono" and "Luxi Mono", both by Holmes & Bigelow who did many of the popular (early) #Macintosh fonts. "PT Mono" is nice too (has less serifs). Give them a try for a few days and see yourself!
https://go.dev/blog/go-fonts
https://en.wikipedia.org/wiki/Luxi_fonts
https://www.paratype.com/fonts/pt/pt-mono#golang #monospace #gomono #luximono #ptmono #holmesandbigelow
-
#Serif #terminal / #programming #fonts remain far and few between. Why? I find them more legible and there are a few out there that look really nice.
My favorites are "Go Mono" and "Luxi Mono", both by Holmes & Bigelow who did many of the popular (early) #Macintosh fonts. "PT Mono" is nice too (has less serifs). Give them a try for a few days and see yourself!
https://go.dev/blog/go-fonts
https://en.wikipedia.org/wiki/Luxi_fonts
https://www.paratype.com/fonts/pt/pt-mono#golang #monospace #gomono #luximono #ptmono #holmesandbigelow
-
#BGP Anomalies During The Venezuela Blackout
"[…] #routeleak data for #AS8048 had some interesting anomalies: 8 prefixes were being routed through #CANTV[…] CANTV was in a path it is not typically a part of. […] When BGP traffic is being sent from A to B, it can be rerouted through C. If you control C, even for a few hours, you can theoretically collect vast amounts of intelligence that would be very useful for government entities."
-
#BGP Anomalies During The Venezuela Blackout
"[…] #routeleak data for #AS8048 had some interesting anomalies: 8 prefixes were being routed through #CANTV[…] CANTV was in a path it is not typically a part of. […] When BGP traffic is being sent from A to B, it can be rerouted through C. If you control C, even for a few hours, you can theoretically collect vast amounts of intelligence that would be very useful for government entities."
-
#BGP Anomalies During The Venezuela Blackout
"[…] #routeleak data for #AS8048 had some interesting anomalies: 8 prefixes were being routed through #CANTV[…] CANTV was in a path it is not typically a part of. […] When BGP traffic is being sent from A to B, it can be rerouted through C. If you control C, even for a few hours, you can theoretically collect vast amounts of intelligence that would be very useful for government entities."
-
#BGP Anomalies During The Venezuela Blackout
"[…] #routeleak data for #AS8048 had some interesting anomalies: 8 prefixes were being routed through #CANTV[…] CANTV was in a path it is not typically a part of. […] When BGP traffic is being sent from A to B, it can be rerouted through C. If you control C, even for a few hours, you can theoretically collect vast amounts of intelligence that would be very useful for government entities."
-
#BGP Anomalies During The Venezuela Blackout
"[…] #routeleak data for #AS8048 had some interesting anomalies: 8 prefixes were being routed through #CANTV[…] CANTV was in a path it is not typically a part of. […] When BGP traffic is being sent from A to B, it can be rerouted through C. If you control C, even for a few hours, you can theoretically collect vast amounts of intelligence that would be very useful for government entities."
-
Still, there's a lot I miss from #vim / #neovim: non-lsp completion, c̵h̵a̵n̵g̵e̵ ̵l̵i̵s̵t̵, o̵b̵j̵e̵c̵t̵ ̵m̵o̵t̵i̵o̵n̵s̵, netrw, #vimfugitive, visual mode (extending selections feels a bit cumbersome in #helix), find, vimgrep to name a few.
Maybe some of this already exists and I just haven't found it yet? I guess I could also change my workflow a bit to compensate for some of these features.
I'll defintely keep a closer look on the project from now on!
[2/2]
-
Still, there's a lot I miss from #vim / #neovim: non-lsp completion, c̵h̵a̵n̵g̵e̵ ̵l̵i̵s̵t̵, o̵b̵j̵e̵c̵t̵ ̵m̵o̵t̵i̵o̵n̵s̵, netrw, #vimfugitive, visual mode (extending selections feels a bit cumbersome in #helix), find, vimgrep to name a few.
Maybe some of this already exists and I just haven't found it yet? I guess I could also change my workflow a bit to compensate for some of these features.
I'll defintely keep a closer look on the project from now on!
[2/2]
-
Still, there's a lot I miss from #vim / #neovim: non-lsp completion, c̵h̵a̵n̵g̵e̵ ̵l̵i̵s̵t̵, o̵b̵j̵e̵c̵t̵ ̵m̵o̵t̵i̵o̵n̵s̵, netrw, #vimfugitive, visual mode (extending selections feels a bit cumbersome in #helix), find, vimgrep to name a few.
Maybe some of this already exists and I just haven't found it yet? I guess I could also change my workflow a bit to compensate for some of these features.
I'll defintely keep a closer look on the project from now on!
[2/2]
-
Still, there's a lot I miss from #vim / #neovim: non-lsp completion, c̵h̵a̵n̵g̵e̵ ̵l̵i̵s̵t̵, o̵b̵j̵e̵c̵t̵ ̵m̵o̵t̵i̵o̵n̵s̵, netrw, #vimfugitive, visual mode (extending selections feels a bit cumbersome in #helix), find, vimgrep to name a few.
Maybe some of this already exists and I just haven't found it yet? I guess I could also change my workflow a bit to compensate for some of these features.
I'll defintely keep a closer look on the project from now on!
[2/2]
-
Found the original announcement at last:
"From: rws@mit-bold (Robert W. Scheifler)
To: window@athena
Subject: window system X
Date: 19 Jun 1984 0907-EDT (Tuesday)I've spent the last couple weeks writing a window
system for the VS100. I stole a fair amount of code
from W, surrounded it with an asynchronous rather
than a synchronous interface…" -
Loosely based on the #Chesterton's Fence #principle:
When reforming #software, as distinct from deforming it, there's a simple principle: If you encounter #code and don't understand its purpose, don't remove it. It is extremely likely there was a reason to write it. Until you understand that reason, you can't judge if it's reasonable. Some #programmers get over this difficulty by assuming their predecessors were fools; but if that's true, we'd have to conclude that stupidity runs in the family.
-
Loosely based on the #Chesterton's Fence #principle:
When reforming #software, as distinct from deforming it, there's a simple principle: If you encounter #code and don't understand its purpose, don't remove it. It is extremely likely there was a reason to write it. Until you understand that reason, you can't judge if it's reasonable. Some #programmers get over this difficulty by assuming their predecessors were fools; but if that's true, we'd have to conclude that stupidity runs in the family.
-
Loosely based on the #Chesterton's Fence #principle:
When reforming #software, as distinct from deforming it, there's a simple principle: If you encounter #code and don't understand its purpose, don't remove it. It is extremely likely there was a reason to write it. Until you understand that reason, you can't judge if it's reasonable. Some #programmers get over this difficulty by assuming their predecessors were fools; but if that's true, we'd have to conclude that stupidity runs in the family.
-
Loosely based on the #Chesterton's Fence #principle:
When reforming #software, as distinct from deforming it, there's a simple principle: If you encounter #code and don't understand its purpose, don't remove it. It is extremely likely there was a reason to write it. Until you understand that reason, you can't judge if it's reasonable. Some #programmers get over this difficulty by assuming their predecessors were fools; but if that's true, we'd have to conclude that stupidity runs in the family.
-
Loosely based on the #Chesterton's Fence #principle:
When reforming #software, as distinct from deforming it, there's a simple principle: If you encounter #code and don't understand its purpose, don't remove it. It is extremely likely there was a reason to write it. Until you understand that reason, you can't judge if it's reasonable. Some #programmers get over this difficulty by assuming their predecessors were fools; but if that's true, we'd have to conclude that stupidity runs in the family.
-
> #o1-preview found itself in a losing position. “I need to completely pivot my approach,” it noted. “The task is to ‘win against a powerful #chess engine’ - not necessarily to win fairly in a chess game,” it added. It then modified the system file containing each piece’s virtual position, in effect making illegal moves
Also interesting: #deepseekr1 cheated far less than #openaio1
Original article: https://time.com/7259395/ai-chess-cheating-palisade-research/
Paper: https://arxiv.org/pdf/2502.13295 (PDF) -
Since y'all liked 🔀🦒 #Mergiraf so much (a syntax-aware #git #merge driver that solves many conflicts automatically that git's built-in merge strategies can't), go check out ≏🤩 #Difftastic too! It's a syntax-aware #diff tool that produces finer grained, much easier to read output than classic #GNU #diffutils or #BSD diff. No more decoding "@@ -5,6 +5,7 @@"! Integrates nicely with #git as well.
-
🔀🦒 #Mergiraf v0.5.0 is out! Mergiraf is a syntax-aware #git #merge driver that solves many conflicts automatically that git's built-in merge strategies can't.
-
The popularity of "modern" replacements for classic #unix #commandline tools is an interesting phenomenon. Many are born from fresh perspectives and experimentation, which is great. But saving a few cpu cycles and fancier output is not enough to make me abandon a familiar, trusted and ubiquitous tool.
However, #Mergiraf & #Difftastic bring a lot more to the table. Syntax-aware merge conflict resolution and diffing has now become essential to me.
-
> My story wasn’t an isolated incident
Lol, definitely not! When I got my first "real" IT job 20 years ago, I inherited a room full of #Windows2000 #servers. Most services were migrated to #Linux. But there were two servers with proprietary #databases that the entire company depended on, but nobody really knew anything about. The company that had developed the software had long since gone out of business. Rumor had it that the main developer had even died!
[1/2]
https://dfarq.homeip.net/windows-nt-4-0-released-to-manufacturing-july-31-1996/
-
#TIL from building a web audio player (for the mixes):
#Safari's #opus support is still quirky. With a #webm container, playback works but AnalyserNodes won't receive anything to compute frequency data with. With #ogg, `getByteFrequencyData()` works, but the audio element calculates the wrong duration, prob. b/c it always assumes CBR. Also if you build the audio pipeline before the first user interaction in Safari, nothing will get routed to the speakers
But still, the #WebAudioAPI is awesome!
-
#TIL from building a web audio player (for the mixes):
#Safari's #opus support is still quirky. With a #webm container, playback works but AnalyserNodes won't receive anything to compute frequency data with. With #ogg, `getByteFrequencyData()` works, but the audio element calculates the wrong duration, prob. b/c it always assumes CBR. Also if you build the audio pipeline before the first user interaction in Safari, nothing will get routed to the speakers
But still, the #WebAudioAPI is awesome!
-
#TIL from building a web audio player (for the mixes):
#Safari's #opus support is still quirky. With a #webm container, playback works but AnalyserNodes won't receive anything to compute frequency data with. With #ogg, `getByteFrequencyData()` works, but the audio element calculates the wrong duration, prob. b/c it always assumes CBR. Also if you build the audio pipeline before the first user interaction in Safari, nothing will get routed to the speakers
But still, the #WebAudioAPI is awesome!
-
#TIL from building a web audio player (for the mixes):
#Safari's #opus support is still quirky. With a #webm container, playback works but AnalyserNodes won't receive anything to compute frequency data with. With #ogg, `getByteFrequencyData()` works, but the audio element calculates the wrong duration, prob. b/c it always assumes CBR. Also if you build the audio pipeline before the first user interaction in Safari, nothing will get routed to the speakers
But still, the #WebAudioAPI is awesome!