Skip Navigation

Posts
11
Comments
949
Joined
3 yr. ago

  • The waste of power is often associated to the proof of work consensus, but that's not a requirement of blockchain. There are other ways to create consensus.

    The bandwidth requirements really depend on what's being stored, but it's usually very manageable for a server. And clients not running validation don't need to store or transfer that much data.

  • git itself is really not far from a blockhain. Blockchain is fine, it only has a bad rep because of ponzi schemes that use it to create crypto, but the technology and trustless consensus mechanisms are interesting.

  • you'll need to record it

    a man saying ‘ALRIGHT ALRIGHT ALRIGHT’, wherein the first syllable of the first two words is at a lower pitch than the second syllable, and the first syllable of the last word is at a higher pitch than the second syllable.

    If you say it in front of the mirror at exactly 3am, a court official will spawn at your location to serve you the papers.

  • but seriously, we need project management features that are decentralized: issue tracking, kanban, code reviews w/ comments, and ways to extend functionality without relying on a git forge.

  • it's fine to prefer less colors, but man, that (2025) blog post is all over the place...

    Sometimes it gets so bad one can’t see the base text color: everything is highlighted. What’s the base text color here?

    why does the base color matter at all? What is "base" anyway when every word has a syntactic meaning?

    Here’s a quick test. Try to find the function definition here:

    It's funny to see how this test backfired depending on the person in hacker news, lobster, and lemmy threads. Clearly a personal preference phrased as absolute truth.

    But the crux of why the post doesn't make sense is assuming this would matter at all:

    Here’s another test. Close your eyes (not yet! Finish this sentence first) and try to remember what color your color theme uses for class names?

    Can you?

    If the answer for both questions is “no”, then your color theme is not functional.

    No, it doesn't. And it boggles my mind why someone would think that failing to recall colors-to-syntax pairs would mean the theme has failed you. Visualizing colors, more often than not, is not even a conscious effort. Colors are a subtle aid to guide your attention to the parts that matter.

    Can you see it? I misspelled return for retunr and its color switched from red to purple.

    This would/should be better caught by a static checker anyway.

    But the best part is that the post contradicts itself: the suggested minimal theme doesn't even address that typo use case mentioned above, because it doesn't feature a distinct color for special keywords. So if one were to follow the post's advice, return and retunr would look exactly the same, making it worse than the colorful theme it criticizes.

  • it's larger than one, also likely larger than nvidia Jetson and some firewalls out there. The record is for the smallest PC capable of running a 100B model LLM locally.

    The specs are impressive tbh, but the record is a bit... specific

  • my bad, I thought this was a wendy's

  • I'm not complaining, I'm stating an observation. You seem the one bothered

  • any language that allows ternary conditionals

  • "Just pour money and we'll solve these little problems, trust me bro, just a few trillion more, we're almost there" vibes

  • people really overthinking the joke in the comments huh

  • It makes sense for it to be there

  • That's not what it means. You need a party actively trying to censor or hide information to be a Streisand effect, this is just accidental marketing.

  • No, this is about adding guidelines for tool-generated submissions to the kernel. The tailwind conversation was on making their documentations more accessible to AI tools.

    Linus doesn't want to add guidelines to not fuel any side of the whole discussion, and says that adding guidelines won't solve the problem because a lot of times it's not trivial to detect whether or not a contribution was written with AI tools, after all, "documentation is for good actors", hinting that anyone contributing AI slop is not expected to respect it anyway.

  • because it does make prototyping/MVP faster, and unfortunately it's difficult for some to see that having no human who can actually understand the codebase is a terrible idea in the medium and long term

  • I don't think Bahrain cares how many buttplugs they sell in other countries, so I wouldn't call it a Streisand effect

  • soulless and dull

    it seems you have read my documentation