Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.infosystems.gemini > #174
| From | rtr <rtr@haraya.invalid> |
|---|---|
| Newsgroups | comp.infosystems.gemini |
| Subject | Re: In the news |
| Date | 2022-02-01 10:10 +0800 |
| Organization | A noiseless patient Spider |
| Message-ID | <87k0efcp6t.fsf@haraya.local.net> (permalink) |
| References | <st3vop$1c0o$1@gioia.aioe.org> <875yq2cbtf.fsf@haraya.local.net> <st5no8$l7l$1@gioia.aioe.org> <875yq0rdrr.fsf@haraya.local.net> <slrnsvfdop.2qi.dan@djph.net> |
Dan Purgert <dan@djph.net> writes:
> rtr wrote:
>> [...]
>> Funnily enough, I was reading a lot about IPFS a few days ago because I
>> thought it's a neat protocol with all the fancy modern web crap that
>> they've pulled in their website. But then I came across this guy's blog:
>>
>> https://fiatjaf.com/d5031e5b.html
>>
>> Which promptly killed all of my enthusiasm with IPFS. It seems like a
>> half-baked protocol that sounds neat in theory but is quite bad in
>> practice. I don't want my files having anything to do with something
>> like that.
>
> Heh, I get that feeling from a fair number of "modern" things. It's
> almost as if all the new frameworks and such that make programming
> easier also make it easier to just make a horrible mess.
They've created their own complex way of making things simple. Is what I
gathered from most ``modern'' tech. It's just crap over crap over crap
and crap. I'm sure there are good technical reasons as to why they were
developed but at some you have to ask yourself: ``Maybe it's time to
just create a new thing for this instead of bolting in it into the
existing framework.''
--
Ang kalayaan ay dili gihatag, ini'y giabot.
--
{gemini,gopher}://kalayaan.xyz
Back to comp.infosystems.gemini | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
In the news David <david@arch.invalid> - 2022-01-29 19:07 +0100
Re: In the news rtr <rtr@haraya.invalid> - 2022-01-30 08:22 +0800
Re: In the news David <david@arch.invalid> - 2022-01-30 11:02 +0100
Re: In the news news@zzo38computer.org.invalid - 2022-01-30 18:51 -0800
Re: In the news rtr <rtr@haraya.invalid> - 2022-01-31 07:43 +0800
Re: In the news Dan Purgert <dan@djph.net> - 2022-01-31 10:16 +0000
Re: In the news Jeremy Brubaker <jbrubake.362@orionarts.invalid> - 2022-01-31 14:01 +0000
Re: In the news Dan Purgert <dan@djph.net> - 2022-01-31 15:56 +0000
Re: In the news rtr <rtr@haraya.invalid> - 2022-02-01 10:12 +0800
Re: In the news rtr <rtr@haraya.invalid> - 2022-02-01 10:10 +0800
Re: In the news Dan Purgert <dan@djph.net> - 2022-02-01 09:42 +0000
Re: In the news oldernow <oldernow@dev.null> - 2023-12-18 19:55 +0000
Re: In the news Kestral Gaian <kes@kesgai.com> - 2023-12-22 00:23 +0000
Re: In the news Denez Van Dyck <denez@vandyck.invalid> - 2023-12-22 08:28 +0000
Re: In the news oldernow <oldernow@dev.null> - 2023-12-26 20:28 +0000
Re: In the news John <john@building-m.simplistic-anti-spam-measure.net> - 2024-01-09 16:27 +0000
Re: In the news SugarBug <3883@sugar.bug> - 2024-01-09 12:18 -0600
Re: In the news oldernow <oldernow@dev.null> - 2024-01-26 14:01 +0000
Re: In the news John <john@building-m.simplistic-anti-spam-measure.net> - 2024-01-26 18:09 +0000
Re: In the news oldernow <oldernow@dev.null> - 2024-01-27 19:31 +0000
Re: In the news news@zzo38computer.org.invalid - 2024-01-28 10:53 -0800
Re: In the news news@zzo38computer.org.invalid - 2024-01-09 14:23 -0800
Re: In the news Ben <benk@tilde.team> - 2022-01-30 14:43 +0330
Re: In the news bunburya <bunburya@tilde.club> - 2022-01-30 12:53 +0000
Re: In the news rtr <rtr@haraya.invalid> - 2022-01-31 07:43 +0800
Re: In the news bunburya <bunburya@tilde.club> - 2022-01-31 11:13 +0000
Re: In the news Jason McBrayer <jmcbray@carcosa.net> - 2022-01-31 09:42 -0500
Re: In the news !nv4l1d <invalid@invalid.com> - 2022-02-01 03:06 +0000
Re: In the news rtr <rtr@haraya.invalid> - 2022-02-04 15:26 +0800
Re: In the news Christian Seibold <krixano@mailbox.org> - 2022-01-31 16:06 -0600
csiph-web