Search
1000 results for “data0”
-
The liquidation of the #LivingComputerMuseum might ruin the last chance to save more #CompuServe data for historical research.
The last 9 #SC40 servers (#PDP10 derivatives) were saved from the dumpster 10y ago¹. One was sent to the #LCM and has been in storage since afaik. Of the other 8, all but one have disappeared.
What will happen to the LCM one now? Christie's probably not interested in it? Will it finally be scrapped?
-
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.
-
Oh my <overlord of choice>…
"There is also an unfortunate #bug that is not fixed to this day that result in an excessive creation of .DS_Store file. Those files should only be created if the user actually makes adjustments to the […] folder. That’s unfortunately not what happens and visiting a folder pretty much guarantees that a .DS_Store file will get created"
On the origins of #DS_store
https://www.arno.org/on-the-origins-of-ds-store -
Oh my <overlord of choice>…
"There is also an unfortunate #bug that is not fixed to this day that result in an excessive creation of .DS_Store file. Those files should only be created if the user actually makes adjustments to the […] folder. That’s unfortunately not what happens and visiting a folder pretty much guarantees that a .DS_Store file will get created"
On the origins of #DS_store
https://www.arno.org/on-the-origins-of-ds-store -
Oh my <overlord of choice>…
"There is also an unfortunate #bug that is not fixed to this day that result in an excessive creation of .DS_Store file. Those files should only be created if the user actually makes adjustments to the […] folder. That’s unfortunately not what happens and visiting a folder pretty much guarantees that a .DS_Store file will get created"
On the origins of #DS_store
https://www.arno.org/on-the-origins-of-ds-store -
Oh my <overlord of choice>…
"There is also an unfortunate #bug that is not fixed to this day that result in an excessive creation of .DS_Store file. Those files should only be created if the user actually makes adjustments to the […] folder. That’s unfortunately not what happens and visiting a folder pretty much guarantees that a .DS_Store file will get created"
On the origins of #DS_store
https://www.arno.org/on-the-origins-of-ds-store -
Oh my <overlord of choice>…
"There is also an unfortunate #bug that is not fixed to this day that result in an excessive creation of .DS_Store file. Those files should only be created if the user actually makes adjustments to the […] folder. That’s unfortunately not what happens and visiting a folder pretty much guarantees that a .DS_Store file will get created"
On the origins of #DS_store
https://www.arno.org/on-the-origins-of-ds-store -
If you're still using polyfill.io you probably want to replace/remove it IMMEDIATELY. The domain has been sold and the new owners are injecting #malware (1).
If you absolutely have to use externally hosted #JavaScript and #CSS, it's a good idea to secure it with #SubresourceIntegrity (2). It's supported by most old browsers you're probably polyfilling for.
(1) https://polykill.io/
(2) https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity -
If you're still using polyfill.io you probably want to replace/remove it IMMEDIATELY. The domain has been sold and the new owners are injecting #malware (1).
If you absolutely have to use externally hosted #JavaScript and #CSS, it's a good idea to secure it with #SubresourceIntegrity (2). It's supported by most old browsers you're probably polyfilling for.
(1) https://polykill.io/
(2) https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity -
If you're still using polyfill.io you probably want to replace/remove it IMMEDIATELY. The domain has been sold and the new owners are injecting #malware (1).
If you absolutely have to use externally hosted #JavaScript and #CSS, it's a good idea to secure it with #SubresourceIntegrity (2). It's supported by most old browsers you're probably polyfilling for.
(1) https://polykill.io/
(2) https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity -
If you're still using polyfill.io you probably want to replace/remove it IMMEDIATELY. The domain has been sold and the new owners are injecting #malware (1).
If you absolutely have to use externally hosted #JavaScript and #CSS, it's a good idea to secure it with #SubresourceIntegrity (2). It's supported by most old browsers you're probably polyfilling for.
(1) https://polykill.io/
(2) https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity -
If you're still using polyfill.io you probably want to replace/remove it IMMEDIATELY. The domain has been sold and the new owners are injecting #malware (1).
If you absolutely have to use externally hosted #JavaScript and #CSS, it's a good idea to secure it with #SubresourceIntegrity (2). It's supported by most old browsers you're probably polyfilling for.
(1) https://polykill.io/
(2) https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity -
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…" -
Thoughtfully designed, aesthetically pleasing CSS library with many modern features:
"matcha.css – Drop-in semantic styling library in pure css"
Think default #browser #stylesheet: no build steps, no dependencies, no #JavaScript, no configuration needed. Just link it into your new or old #HTML and off you go.
-
Captivating #debugging horror story: Coding Machines (how the machines are secretly taking over). This is from 2009. Another attack vector that's possible today is inserting into #LLMs and getting triggered by #adversarial #prompting.
https://www.teamten.com/lawrence/writings/coding-machines/
via #CoRecursive #CoRecursivePodcast:
https://corecursive.com/coding-machines-with-don-and-krystal/ -
Captivating #debugging horror story: Coding Machines (how the machines are secretly taking over). This is from 2009. Another attack vector that's possible today is inserting into #LLMs and getting triggered by #adversarial #prompting.
https://www.teamten.com/lawrence/writings/coding-machines/
via #CoRecursive #CoRecursivePodcast:
https://corecursive.com/coding-machines-with-don-and-krystal/ -
Captivating #debugging horror story: Coding Machines (how the machines are secretly taking over). This is from 2009. Another attack vector that's possible today is inserting into #LLMs and getting triggered by #adversarial #prompting.
https://www.teamten.com/lawrence/writings/coding-machines/
via #CoRecursive #CoRecursivePodcast:
https://corecursive.com/coding-machines-with-don-and-krystal/ -
Captivating #debugging horror story: Coding Machines (how the machines are secretly taking over). This is from 2009. Another attack vector that's possible today is inserting into #LLMs and getting triggered by #adversarial #prompting.
https://www.teamten.com/lawrence/writings/coding-machines/
via #CoRecursive #CoRecursivePodcast:
https://corecursive.com/coding-machines-with-don-and-krystal/ -
#TIL #Caddy is not only a great general-purpose #http server with automatic #https handling (via #letsencrypt and #zerossl). It also has a layer 4 module that can make it terminate #tls for arbitrary #tcp services and still handle certificates automatically. I just used it to tls-terminate a #redis db and it works like a charm!
-
Forced to accept a huge pile of indigestible #legalese terms and conditions of some service? Paste it into #AI and have it summarize the disadvantages you're facing as a customer. It's pretty good at it afaict.
Here's #Bandcamp's latest terms and conditions as an example:
https://hf.co/chat/r/SznQuq8 -
`Promise.withResolvers()` will be part of #es2024! It's another tool to write cleaner #async code with in #JavaScript. Here's a neat explainer:
https://pawelgrzybek.com/deferred-javascript-promises-using-promise-withresolvers
-
@whynothugo Here's a more hands-on one from the #sourcehut folks: https://git-send-email.io/
After hosting my own #GitHub-style forge for many years (used #forgejo last), most of my private projects are now just plain ssh-hosted repos. Managing the ever growing complexity just stopped being worth it for me. #GitBug and #cgit (simple read-only web frontend) is all I need. Accepting patches/issues via mail only is not ideal, but not dealing with low-effort PRs and lazily filed issues is nice too.
-
I'm not saying we should all go back to #mailinglists lists and scatter our stuff all over the place. #GitHub and centralized repos in general have a lot of advantages. But there's a trade-off to be made and you should be aware of it before you click "add repo" just because they say it's free.
-
The #CuckoosEgg is one of my favorite #books ever. It's the real story of how an astronomer turned #sysadmin starts investigating a 75¢ billing discrepancy and ends up uncovering a KGB #hacker in the late 80's.
I knew there was a docu-style movie starring the real admin #CliffordStoll. But I had never watched it. Until today! And it's every bit as fun and nostalgic to watch as I'd hoped!
-
I actually already did this in 2018 when #vim 8.1 came out. I was using #MacVim back then, simply because it was rendering text much faster than all the terminal apps available at the time. The new built-in terminal in 8.1 was a huge feature. It allowed me to stop switching between MacVim and the terminal all the time and still enjoy a fast vim experience. Eventually faster terminals like #alacritty, #kitty and #wezterm and also #neovim made me switch back to the terminal again.
-
[4/5]
jose-elias-alvarez/typescript.nvim - easy #typescript-language-server integration (I've just seen this is now archived, but it still works well.)
fatih/vim-go - #golang language support
mhartington/formatter.nvim - format runner. I use it to run #biome and #gopls to auto-format code.
*GIT*
tpope/vim-fugitive - THE BEST. This is how I mostly interact with #git.
lewis6991/gitsigns.nvim - git decorations for the gutter
rhysd/conflict-marker.vim – makes resolving merge conflicts easier