Conversation

Notices

1. Embed this notice
   internetarchive (internetarchive@mastodon.archive.org)'s status on Friday, 11-Oct-2024 01:44:35 JST internetarchive

   • Brewster Kahle

   Updates from @brewsterkahle about the DDOS attacks on Internet Archive:

   • Haelwenn /элвэн/ :triskell: likes this.
   • Sick Sun repeated this.
   • Embed this notice
     morph (morph@morphnet.de)'s status on Friday, 11-Oct-2024 01:46:07 JST morph

     in reply to

     • Brewster Kahle

     @internetarchive @brewsterkahle ☹️

   • Embed this notice
     Sam (They/Them) (addressforbots@social.apcn.nz)'s status on Sunday, 13-Oct-2024 05:08:31 JST Sam (They/Them)

     in reply to

     • Brewster Kahle

     @internetarchive @brewsterkahle
     Another update (screenshoted from the site formerly known as Twitter)

   • Embed this notice
     Hideki Motosuwa (wildebest@mastodon.online)'s status on Sunday, 13-Oct-2024 20:42:26 JST Hideki Motosuwa

     in reply to

     • Brewster Kahle

     @internetarchive
     I hope it gets well soon. And my advice. Please don't use JavaScript. Internet archive should 100% work without JS since I am a "libre JS" user and JS bloats everything. Internet archive should be able to be accessed by any browsers without JS. JS made my computer works hard. It's heavy on memory. And JS library needs constant update that makes it even more bloated.
     @brewsterkahle

     翠星石 likes this.
   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Sunday, 13-Oct-2024 20:44:24 JST 翠星石

     in reply to

     • Aroop Roelofs :verified:
     @finlaydag33k JavaScript is a pile of garbage and it makes any computer work hard, no matter how fast it is.
     
     If your computer has in excess of 1 billion bytes of RAM and is clocked in excess of 1 billion Hz and software is still struggling to run, that's the fault of the software, not your computer.
   • Embed this notice
     Aroop Roelofs :verified: (finlaydag33k@social.linux.pizza)'s status on Sunday, 13-Oct-2024 20:44:25 JST Aroop Roelofs :verified:

     in reply to

     • Brewster Kahle
     • Hideki Motosuwa

     @wildebest If JS is making your computer work hard or is that heavy on memory... Your PC is the problem, not JS...
     @internetarchive @brewsterkahle

   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Sunday, 13-Oct-2024 23:58:52 JST 翠星石

     in reply to

     • Aroop Roelofs :verified:
     @finlaydag33k There's many sites on the internet that don't agree with you, too bad linking to them or even mentioning them would be recommending the execution of proprietary malware.
     
     You're clearly browsing only sites that are light with JavaScript if the Raspberry Pi 1A isn't getting overwhelmed, but I reckon those sites would operate just as well and perform better without JavaScript.
   • Embed this notice
     Aroop Roelofs :verified: (finlaydag33k@social.linux.pizza)'s status on Sunday, 13-Oct-2024 23:58:54 JST Aroop Roelofs :verified:

     in reply to

     • 翠星石

     @Suiseiseki wdym "makes any computer work hard"?
     It barely puts any stress on a Raspberry Pi 1A...
     If suddenly your "billion bytes of RAM and billion Hz CPU" starts struggling with it, something else is horribly wrong and it's not JS itself...

     Sure, it's not the most resource efficient language there is but it's certainly not the "heavy pile of garbage" you make it out to be.

   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Monday, 14-Oct-2024 00:05:58 JST 翠星石

     in reply to

     • Aroop Roelofs :verified:
     @finlaydag33k Well, there is it.
     
     Yes, if you run small JavaScript programs the incredible power of modern hardware can take it without slowing down too much.
     
     Most of JavaScript is "stupid oversized piece of shit framework" that runs in web browsers - but really if you want to write something outside of a browser, you're better off writing perl or another decent scripting language or a compiled language.
   • Embed this notice
     Aroop Roelofs :verified: (finlaydag33k@social.linux.pizza)'s status on Monday, 14-Oct-2024 00:05:59 JST Aroop Roelofs :verified:

     in reply to

     • 翠星石

     @Suiseiseki No, I run JS (or more accurately TS but the difference is practically non-existence) on the Pi itself using Deno...
     Not even browsing websites...

     You're mistaking "stupid oversized piece of shit framework bloated with 1337666 things you don't need ran in a bloated webbrowser that does 1337666 extra things" with "JS"...

     JS, in itself, isn't that taxing...

   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Monday, 14-Oct-2024 00:26:00 JST 翠星石

     in reply to

     • Aroop Roelofs :verified:
     @finlaydag33k JavaScript totally fails ease of use if you actually compile the supporting software to compile rather than someone doing it all for you and passing around mystery meat binaries.
     
     Deno relies on the "V8 engine" and rust, which means to use it requires the compilation of "V8", LLVM and rustc and the massive dependency chains, which takes many CPU cycles and a huge amount of RAM to compile and chances are it'll fail to compile multiple times too.
     
     I wouldn't describe such setup as anywhere near "lean", but it is mean to at least one person and their computer.
     
     
     Meanwhile, I can just emerge perl from the source code and in a few short minutes get a working perl runtime.
     
     Or I can just emerge gcc from the source code (oh wait, already installed) and in an acceptable amount of time have the best C compiler.
   • Embed this notice
     Aroop Roelofs :verified: (finlaydag33k@social.linux.pizza)'s status on Monday, 14-Oct-2024 00:26:01 JST Aroop Roelofs :verified:

     in reply to

     • 翠星石

     @Suiseiseki I mean, the JS program isn't even that small and the Pi is effectively equivalent to a PC from around the early 2000's.
     Even at peaks, it barely gets above 5% usage on its CPU (memory usage sits around 70MB including the entire OS).

     And yes, most JS you find on *websites* is overly bloated.
     But that's not the fault of JS.
     I personally think it's unfair to label JS (the language) as "a big evil" because devs tend to make scuffed choices.
     JS itself can be quite lean and mean (altho it's indeed nowhere near as fast as a compiled language).

     I mostly use Deno because JS is my go-to language.
     I could learn Perl (altho I already can write some Nim) but I'd need to re-learn a lot for what is effectively very little gains where it matters for me.
     It's a balancing act between raw efficiency and "ease of use".

   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Monday, 14-Oct-2024 20:35:45 JST 翠星石

     in reply to

     • Aroop Roelofs :verified:
     @finlaydag33k >Linux kernel bad because it takes many CPU cycles and huge amounts of RAM to compile with chances it'll fail to compile multiple times too?
     Linux is only a kernel, so please don't imply it's more than a kernel.
     
     Linux is bad because it contains proprietary software disguised as arrays of numbers - I use the free version - GNU Linux-libre
     
     With a cut down .config, Linux-libre is quite pleasant to compile and compiles every time.
     
     >most distros bad, must build entire distro yourself so you have 100% control over everything!...
     Most distros are bad, but there's no reason to write yet another distro when you can install Gentoo-libre or GNU Guix.
     
     When it comes to large software, I've found gcc to be a program that compiles the most reliably.
   • Embed this notice
     Aroop Roelofs :verified: (finlaydag33k@social.linux.pizza)'s status on Monday, 14-Oct-2024 20:35:46 JST Aroop Roelofs :verified:

     in reply to

     • 翠星石

     @Suiseiseki At this point, you just keep moving the goalpost to make JS look worse than it really is...
     We went from "running JS" to "compiling the runtime"...

     What's next? Linux kernel bad because it takes many CPU cycles and huge amounts of RAM to compile with chances it'll fail to compile multiple times too? :stallman_thaenkin:
     I wouldn't describe such setup anywhere near "lean" but it's at least mean to one person and their computer. :yay:
     GCC also takes a huge amount of CPU cycles to compile and install with chances it'll fail multiple times too... GCC bad!
     And well... GCC doesn't even come out of the box with most common distros...
     Oh wait... Most distro's are just passing around "mystery meat binaries", so most distros bad, must build entire distro yourself so you have 100% control over everything!...
     Oh wait, that takes many CPU cycles and can fail multiple times too...
     So best is just not running any software, no CPU cycles wasted anywhere in the pipeline! 🤤

   • Embed this notice
     trillytrill (trillytrill@mstdn.social)'s status on Wednesday, 16-Oct-2024 20:29:45 JST trillytrill

     in reply to

     • Brewster Kahle

     @internetarchive @brewsterkahle
     Man, this is just low. Like attacking a library low. Who tf does shit like this?

     clacke likes this.