Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)F

FizzyOrange

@ FizzyOrange @programming.dev

Posts
2
Comments
1237
Joined
3 yr. ago

  • Do people use Cargo?

    Jump

  • Almost everyone uses Cargo. I think the only people that don't are Google and Facebook who will probably be using Bazel or Buck2. I think you're a bit confused about what Cargo is.

  • A real free alternative to Git Graph

    Jump

  • I've tried this. Unfortunately it isn't anywhere near as good as Git Graph, or at least it wasn't when I tried it a few months ago. I'll stick with Git Graph until it stops working I think.

  • The CUPS explout is here: GitHub - RickdeJager/cupshax

    Jump

  • Wow look at that CUPS code and tell me with a straight face there aren't 5 more similar vulnerabilities waiting to be found...

  • .dev Why is C hidden gold?

    Jump

  • I seriously wonder what kind of circumstances lead someone to be this irrationally devoted to such a flawed and outclassed language. Probably best if I just block you though...

  • Pragmatic Semiconductor bends RISC-V into new markets • The Register

    Jump

  • Unlikely to be of any use to anyone in practice because you can fit a 12k gate chip into a grain of sand and then it doesn't really matter if it's not flexible.

    Interesting tech though.

  • .dev It's time to return to the roots, to the C programming language.

    Jump

  • Go to bed, you're drunk.

  • Removed

    Programming in simple 4 steps

    Jump

  • I've never done it but apparently you can actually gradually transition to Typescript one file at a time by renaming them from .js to .ts. Might help a bit. Good luck anyway!

  • Google's Shift to Rust Programming Cuts Android Memory Vulnerabilities by 52%

    Jump

  • Actual blog post.

    Great accomplishment. I think we all knew it must happen like this but it's great to see real world results.

    I think this is probably actually the most useful part of the post:

    Increasing productivity: Safe Coding improves code correctness and developer productivity by shifting bug finding further left, before the code is even checked in. We see this shift showing up in important metrics such as rollback rates (emergency code revert due to an unanticipated bug). The Android team has observed that the rollback rate of Rust changes is less than half that of C++.

    I think anyone writing Rust knows this but it's quite hard to convince non-Rust developers that you will write fewer bugs in general (not just memory safety bugs) with Rust than with C++. It's great to have a solid number to point to.

  • Removed

    Programming in simple 4 steps

    Jump

  • Yeah IntelliJ does amazingly without type annotations but even it can't do everything. E.g. if you're using libraries without type annotations, or if you don't call functions with every possible type (is your testing that good? No.)

    Static types have other benefits anyway so you should use them even if everyone in your team uses IntelliJ.

  • Removed

    Programming in simple 4 steps

    Jump

  • In common usage a linter detects code that is legal but likely a mistake, or code that doesn't follow best practice.

    Although static type checkers do fit in that definition, that definition is overly broad and they would not be called a "linter".

    Here is how static type checkers describe themselves:

    Pyright is a full-featured, standards-based static type checker for Python.

    Mypy is a static type checker for Python.

    TypeScript is a strongly typed programming language that builds on JavaScript, giving you better tooling at any scale.

    Sorbet is a fast, powerful type checker designed for Ruby.

    Here is how linters describe themselves:

    Pylint is a static code analyser for Python 2 or 3. ... Pylint analyses your code without actually running it. It checks for errors, enforces a coding standard, looks for code smells, and can make suggestions about how the code could be refactored.

    (Ok I guess it's a bit redundant for Pylint to say it is a linter.)

    Eslint: The pluggable linting utility for JavaScript and JSX

    Clippy: A collection of lints to catch common mistakes and improve your Rust code.

    Ruff: An extremely fast Python linter and code formatter, written in Rust.

    You get the idea... Linters are heuristic and advisory. Quite different to static type checking.

  • Deleted

    Permanently Deleted

    Jump

  • Honestly I would take a look through a good standard library that provides a lot of algorithms (e.g. C++ or Rust). That has the basics, especially for data structures.

    Also have a go at some hacker rank tests. Especially if you want to learn dynamic programming (abysmal name), they absolutely love that.

  • Removed

    Programming in simple 4 steps

    Jump

  • Linters 100% won't. A static type checker is not a linter.

  • Removed

    Programming in simple 4 steps

    Jump

  • Yes because you used static type annotations. This thread was about code that doesn't use static types (or static type annotations/hints).

  • Removed

    Programming in simple 4 steps

    Jump

  • It's an example to demonstrate that linters cannot reliably detect variable name typos - you need static types. None of the stuff you mentioned is relevant.

    The typo in your example is also undetectable by linters. I think you're missing the point.

  • Removed

    Programming in simple 4 steps

    Jump

  • What's awful about this example? The only thing I do is access an object member. Does your code not do that??

  • Removed

    Programming in simple 4 steps

    Jump

  • Yes you can use static type hinting and the static type checker (Mypy or Pyright) will catch that. Linters (Pylint) won't.

  • Removed

    Programming in simple 4 steps

    Jump

  • If you use VSCode, open both files and then ctrl-shift-P "Compare active file with ..."

    You're welcome.

  • Removed

    Programming in simple 4 steps

    Jump 
  •  
        
def foo(x):
  return x.whatevr

    No linter is going to catch that.

  • Removed

    Programming in simple 4 steps

    Jump

  • ...for people who refuse to use static types.