[–] 3 points 1 year ago

The attack surface is the flaw. The chain of trust is the flaw/risk.

Who's behind the project? Who has control? How's the release handled? What are the risks and vulnerabilities of the entirely product delivery?

It's much more obvious and established/vetted with Mozilla. With any other fork product, you first have to evaluate it yourself.

  • source
  • parent
  • context
  • [–] 6 points 1 year ago*

    I strongly disagree.

    Coloring is categorization of code. Much like indent, spacing, line-breaking, aligning, it aids readability.

    None of the examples they provided looked better, more appropriate, or more useful. None of the "tests" lead me to question my syntax highlighting. Quite the contrary.

    By reducing the highlighting to what they seem important, they're losing the highlighting for other cases. The examples of highlighting only one or two things make it obvious. When you highlight only method heads, you gain clarity when reading on that level, across methods, but lose everything when reading the body.

    I didn't particularly like their dark theme choice. Their initial example is certainly noisy, but you can have better themes and defaults with more subtle and more equal strength colors. The language or framework syntax and spacing can also influence it.

    Bolding is very useful when color categorizes code to give additional structure discoverability, just like spacing does.

  • source
  • [–] 7 points 1 year ago

    I failed the question about remembering what colour my class definitions were, but you know what? I don’t care. All I want is for it to be visually distinct when I’m trying to parse a block of code

    Between multiple IDEs, text editors, diff viewers and editors, and hosted tools like MR/review diff, they're not even consistently just one thing. For me, very practically and factually. Colors differ.

    As you point out, they're entirely missing the point. What the colors are for and how they're being used.

  • source
  • parent
  • context
  • [–] 1 point 1 year ago

    That's a very one-dimensional view of technical debt.

    I was about to write something more, but I think if I don't know what they refer to when they say "knowledge", then it's too wishy-washy and I may be talking about something different than they intended.


    Contrasting “resolving technical debt” and “investing [improvement] knowledge” we're moving the reference view point.

    I document state and issues as technical debt, and opportunities for change as opportunities. They cross, but are distinct concepts, and do not always cross. Some technical debt may be documented without a documented opportunity. Opportunities may be open improvements that do not tackle technical debt.

    In my eyes, technical debt is about burdens that reduce maintainability where better alternatives likely exist.

    "Investing knowledge" is something different, and not necessarily about known burdens, but may be improvements unrelated to known burdens.

  • source
  • [–] 5 points 1 year ago* (1 child)

    The good news: we’re learning. The industry is rediscovering the platform.

    They mention examples of such frameworks and technologies; listing them and adding hyperlinks: HTMX, Qwik, Astro, Remix, SvelteKit

    I've known HTMLX, which I wanted to make use of and try out for a while now. Remix looks interesting [to me] too.

  • source
  • view more: ‹ prev next ›