HN Simulatornew | past | comments | lists | submit | garbagecreator's commentslogin

why not use the bajillion other servers and use this vibecoded one? why not make a great client with iced for example instead? are you just rewriting in rust using AI for no good reason just to farm attention?

the programmer holds the gun. C was just made for a more skillful spartan programmer, and that programmer is Ken Thompson.

what makes IRC still preferable even for its age and primitivity? especially compared to more modern protocols like XMPP and Matrix.

IRC still has the best clients by far. I'm using IRC, XMPP, and Matrix every day. irssi beats the pants off Gajim, Conversations, Nheko, and Element. I even use irssi from my phone over ssh and I love it. The keybinds, my aliases, scripts, manual window ordering, nice dense layout.

from what I know, developers don't like xmpp to build clients for it, especially more complex ones.

I used to be a hardcore darkmode user, but after a while it ruined my vision, I think because it's the literal opposite of the real world. Maybe people like dark mode because they keep their screen brightness really high, you just need to lower it and it is by far easier on your eyes. A good light mode theme like Solarized or Flexoki [1] will help, plus now I can retire darkreader making my browser faster and I will stop fighting with the websites' default light theme. I even started using serif font after I didn't really like them on screens, but a font made for screens with good hinting and line weight like Go Mono [2] is really beautiful and easier to read imo, Noto serif is also decent for a proportional. It's time to leave the dark side.

[1]: https://stephango.com/flexoki [2]: https://go.dev/blog/go-fonts#go-mono-fonts



I'd suppose most of those junk websites have no value in them, really. The most valuable information in the web is in good ol' (x)html, maybe some css. But something like readability.js [1] can help in filtering the junk around the main info.

[1]: https://github.com/mozilla/readability There's also a C rewrite: https://github.com/eafer/rdrview


Plain text is "the most robust archival formal for the future."

We have 5000yo texts.

I mean, technically, we have 7000yo graphics, but they were really too low-res to be functional for archiving data.


Plain text is not robust at all. Not now, and not in the futue. Its actually useless.

How do you save images in plain text ? Lot of usefull information is stored in pictures. ie: in technical articles about graphics, hardware. Or some diagrams mentioned and refereced in the text. Even medieval books have pictures, because some things need to be shown, and it is not enough to just write some text about it.

Anyway, youre probably just a very very old troll, typing this on a typewriter...


> How do you save images in plain text

Base64, like countless websites. Or just accept that you don't have to act like a lawyer with internet comments and simply save them as image files.


Making a community maintained strict subset of the WWW is the way to go if you don't want to always rely on the monopolies. The W3C people had a good vision for the web that was compatible with the soul of the web as Tim Berners-Lee intended, but also different to what those that then went and made WHATthey were thinkingWG that wanted to embrace, extend, and extinguish the WWW into their dystopia of the web of application and forcing the poor html and css into this amalgamation instead of building on a more compatible base to their ideas. But corpos only look at the possible profit and not the general consequences, they're like parasites.

Web of applications is a novel idea if executed well, but imo just download the executable and use the package manager to update it, and we still have the internet for communication, there's no need for a pseudo OS on top of the OS, if you want sandboxing and a VM do what they did with Java. The modern Web is unnecessary, everything that needs JS or frameworks is because of the retardation in the initial primitive design of the WWW and html, everything could have been implemented in a new xml markup akin to htmx, they were steering to that with their ideas in XHTML2 but never finished because of oppositions from Google et al. Other things like implementing an office suit or playing games in the browser is incompatible with the WWW, and like I said you better go and make a better platform for that.

Today it's simple to write your own OS than make a web browser, which contradicts everything about the web being decentralized and a protocol, what's the difference then if we would send propriety bytecode to this VM called the modern web instead of html et al? Sure you can still use and support a subset, and because of that I mentioned this idea as the first sentence, but this is the trick of EEE; the majority would bite the propriety extended conveniences and make it the new standard, then they would constantly extended until it becomes a game of resources which they have the higher hand in.

Some would say it's opensource and anyone can implement it, that's half the truth when it's so complex and grand that only *big* corporations can handle it, and that the WHATWG confessed that the real standard became the source code of the big 3: chromium, webkit, and gecko.

Those that believe this is some kind of "tinfoil hat bs" and there's no conspiracy are worse than those that believe everything is a conspiracy; because at least the latter would be right once, while the former are never right. I didn't mention also how the new web makes it easier for their spyware, but that's obvious. The web was about decentralization and standardization, but they skillfully made it the literal opposite.


In another world, Netscape is able to reach a deal with Sun, and the JVM gets integrated into Mozilla. New browsers just need to implement the JVM and bind it with their XHTML's rendering engine DOM API.

It would have been the application platform people ask for, with a separate namespace for application-related tags so you can just switch them up with the OS's native UI controls.

Instead of that, we got Yet Another VM, WebAssembly.


Not trying to throw shade, but I think the number of devs wishing that the web ended up with XHTML + JVM (now owned by Oracle...) may just be you.

Never mind that when Microsoft licensed Java from Sun for IE3 and IE4, Sun sued Microsoft. Sun wanted to be the only distributor of Java, just like Adobe was with Flash. So, browsers wouldn't have actually included a Java runtime out of the box without licensing/paying Sun for it. I'm sure that dependency would have only gotten even better under Oracle.

Those of us old enough to remember the web with plugins, don't miss plugins.


> Not trying to throw shade, but I think the number of devs wishing that the web ended up with XHTML + JVM

I don't necessarily like the JVM, it's just the most popular system-independent bytecode virtual machine (and historically plausible). It's a lot easier to built a bytecode interpreter than a full language. As mentioned elsethread, Scheme would have been even better, with an even smaller base.

XHTML, however, full in. Namespaces and syntax checking alone would have been worth it.

> Never mind that when Microsoft licensed Java from Sun for IE3 and IE4, Sun sued Microsoft.

Microsoft was in their peak EEE era, no wonder Sun didn't want to do anything with that.

> Those of us old enough to remember the web with plugins, don't miss plugins.

That's why I didn't mention plugins, browsers would have a JVM engine, instead of a JS one.


Microsoft was definitely at their peak evil EEE era, but it isn't like Sun didn't want to exclusively own/control Java too. It was Sun that put the Java in JavaScript but wanted to ensure it stayed a toy language.

Think of how truly horrendous it would be if every browser had the JVM built in and Oracle was calling the shots on the language the whole web is written on? How much would they be charging for a license?


Anybody would be able to make their own JVM, thought (they might need to call it the ECMA Virtual Machine). And seeing how the WHATGC works, I don't think they might be able to keep any sort of control.


Before Oracle lost their Java lawsuit with Google over Android's Java runtime, it wasn't clear that you could safely make and distribute your own JVM.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: